Skip to main content
Resources

Frequently Asked Questions: ICANN Fellowship Program

ICANN Fellowship Program

Application | Selection | Travel

Application

Can I send information separately to ICANN if I cannot provide it in time for the application?

The online application system is the only method that you can use to apply for an ICANN Fellowship. Where applicable, an applicant may submit additional documentation as proof of their engagement in ICANN. Additional documentation should be sent to fellowship-application@icann.org. No information will be accepted after the application closes.

Can I submit my application in any language?

The online application form must be written in English. If English is not your first language, you are encouraged to translate your responses into English for the application. The Selection Committee members come from different countries around the world, and English is their common language. If an application is completed in any language other than English, we cannot guarantee that the content will be read and/or understood for its original meaning.

Supporting documentation (such as attendance records, links to blogs, certificates, etc.) may be in other languages.

Which ICANN Learn Courses are required?

If you are a first-time fellow, you must complete 102 Introduction to ICANN. This course is available in English (102.1), Spanish (102.2), French (102.3), Arabic (102.4), Russian (102.5), Chinese (102.6), and Portuguese (102.7).

If you are applying for a second or third fellowship, you must complete 501.1 Digital Trade and Global Internet Governance.

Your course completion certificate is a required element of the application system and must be uploaded within the application.

How do I take an ICANN Learn course?

First, create an account at ICANN Learn at https://learn.icann.org.

On the ICANN Learn dashboard, click the catalog icon. First-time fellows will find their required course under the Newcomers tab; alumni will find their course under the Internet Governance tab.

You do not have to complete the entire course in one sitting; ICANN Learn will save your progress. Once you have completed the required course, you can download your certificate in the left-hand corner of the specific course launch page. Alternatively, you can access your certificate by clicking on the transcript icon on the ICANN Learn dashboard. Certificates can be downloaded in pdf format and uploaded into your application directly.

For more information, please review these instructions [PDF, 11.7 MB].

How many times can I receive Fellowship Program support?

An individual can receive a fellowship up to three times. Second and third-time fellows must prove their ICANN involvement and engagement in one of the ICANN communities.

I'm an active participant in the ICANN community. Do I need to provide proof of engagement?

Yes, applicants are responsible for providing evidence of their ICANN involvement and engagement. You will have the opportunity to describe your engagement on the Fellowship Program online application and supporting documentation should be submitted to fellowship-application@icann.org according to the instructions in the online application.

What type of supporting documentation should I submit as proof of  my ICANN involvement and engagement?

Below are some examples:

  • attendance records or relevant documentation demonstrating your participation in ICANN global and/or regional events or webinars
  • a screenshot of your name in a membership list for an ICANN Supporting Organization (SO), Advisory Committee (AC), Stakeholder Group (SG), or Constituency
  • an email from the group's chair confirming your membership
  • links to substantive discussions and deliberations on mailing lists for working groups
  • examples of contributions to reporting on working group activity to the stakeholder group/community
  • links to public comment contributions
  • links to work on review teams
  • blogs about ICANN-related topics and events

Can I submit my application form or supporting documentation after the application round closes?

No. Please take careful note of the application closing date listed at https://www.icann.org/fellowshipprogram/#dates-deadlines. Active but incomplete applications will not be considered once the system is closed. Supporting documentation submitted after the system is closed will not be considered.

Selection

Who reviews the applications and how are the fellowships chosen?

The Selection Committee is composed of representatives appointed by their Supporting Organization (SO) or Advisory Committee (AC). The Selection Committee reviews all eligible applications and scores them according to the Applicant Selection Criteria. The Selection Committee will take into account comments from ICANN's Global Stakeholder Engagement team on individual applications and on the overall needs of each region and community group in ICANN's multistakeholder model.

The Fellowship Program will support 45 participants per ICANN Public Meeting, including newcomers, returning alumni, and mentors.

For the ICANN Policy Forum, ICANN only accepts applications from Fellowship Program alumni.

How will I know if I received a fellowship?

All successful candidates are announced on the ICANN website, approximately four months before the meeting. Successful candidates also receive a follow-up email and should accept the fellowship within a week. If a candidate does not accept the fellowship, a pre-established list of alternates will be used to fill the vacated position.

Do I need to re-apply for each fellowship?

Yes, you must re-apply for each fellowship round.

Travel

How will my travel be covered?

All travel including airfare and accommodations will be booked and paid for by ICANN directly. Any additional charges related to travel are the responsibility of the fellow. Please visit the Community Travel Support Guidelines [PDF, 312 KB] for more information.

How will the stipend work?

A stipend not to exceed US $500.00 will be provided to offset reasonable individual expenses (such as meals, transport to/from the airport, and incidentals). One half of the allotted stipend will be provided to each participating fellow prior to the meeting; the second half of the stipend will be provided via wire transfer by ICANN upon successful completion of the ICANN Fellowship Program and submission of the post-meeting survey two weeks after the ICANN Meeting.

Do I need insurance?

Acquiring and paying for any and all insurance, including but not limited to travel insurance, is the responsibility of the fellow. Carrying proof of insurance is suggested. ICANN will reimburse travel insurance expenses only if it is required to apply for a visa; to be reimbursed, the supported traveler must provide proof that the insurance is required.

I would like to add personal or other business segments to my travel. What do I do?

Please refer to the Community Travel Support Guidelines [PDF, 312 KB] and the Community Travel Support website for more information.

What travel documents are needed?

  • A valid passport **
  • Travel documents as required by your country of origin
  • A visa may be required by the country hosting the ICANN Public Meeting; it is very important that you check with your local consulate agency
  • Transit visas may be required to connect in certain cities or countries; please check with your local consulate agency

**All travel documents must be consistent with the name on your valid passport.

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."