Application Types: Frequently Asked Questions

1. What types of gTLD applications can be submitted in the New gTLD Program?

An applicant can choose to designate its application as a general application or a specialized application, both of which are subject to ICANN's evaluation to confirm the designation.

A general application is any application that does not fall into a specialized type. It is subject to the standard set of requirements set out in the Applicant Guidebook and does not have any conditional requirements or designations.

A specialized application has conditional requirement(s) and designation(s), depending on 1) the type of the applied-for string; 2) the type of applicant; and/or 3) the intended use of the applied-for string. See the various designations for a specialized application in the list below:

• Geographic Name application
• Reserved Name application
• Community Application
• Brand TLD application
• Internationalized Domain Name (IDN) application
• Variant string application
• Application from governments or inter-governmental organizations (IGOs)
• Application from an applicant that qualifies for assistance through the Applicant Support Program

2. Why are there different types of gTLDs?

The variety of gTLDs that have been and will be introduced through ICANN's New gTLD Program reflects the various identities and needs of Internet users worldwide, as well as the intended use for top-level domains. They enhance the Domain Name System (DNS) by promoting diversity, competition, and innovation. Applications for different gTLD types have varying requirements and are subject to conditional evaluations to confirm their respective designations and may be subject to conditional fees. Learn more by reading the use cases that tell the stories of prior applicants for various gTLD types, including the considerations of registry operators before they applied for the strings, as well as their business impact since delegation.

3. What is a Geographic Name application?

If the applied-for string matches any of the following criteria, it will be considered a Geographic Name application:

• It is the name (in any language) of a capital city of any country or territory listed in the ISO3166-1 standard;
• It is a city name, where the applicant declares that it intends to use the gTLD for purposes associated with the geographic name;
• It is an exact match of a sub-national place name such as a county, province, or state listed in the ISO3166-2 standard; or
• It is a name listed as a UNESCO region or appearing on the UN Geographic Regions section M49.

Applicants may choose to identify their applied-for string as a Geographic Name during the application process. However, regardless of whether or not an applicant designates its applied-for string as a Geographic Name, ICANN will evaluate whether an applied-for string meets the criteria for a Geographic Name, because this type of application must satisfy additional requirements in order to be approved. Learn more

4. What is a Reserved Name application?

If an eligible entity applies for a string that has been set aside on the Reserved Names list, it will be considered an application for a Reserved Name. Learn more

5. What is a Community Application?

If an applicant intends to operate an applied-for string for the benefit of a clearly delineated community, the applicant can designate its application as a Community Application. Learn more

6. What is a Brand TLD application?

If a brand or trademark owner applies for a string that matches its registered trademark, the applicant can designate its application as a Brand TLD application. Learn more

7. What is an Internationalized Domain Name (IDN) application?

If an applicant applies for a string that contains one or more non-ASCII characters, it will be considered an IDN application. Learn more

8. What is a variant string application?

If an applicant applies for a string that has other forms in different scripts-such as Arabic or Chinese-and those forms are identified as variant strings under the Root Zone Label Generation Rules (RZ-LGR), the application is considered a variant string application. Learn more

9. Why are applications from governments and intergovernmental organizations (IGOs) considered specialized?

Specialized applications may have different requirements based on the application or applicant type. Applications from governments or IGOs are considered specialized because they often involve Geographic Names or Reserved Names, which come with specific eligibility and procedural requirements. Furthermore, if an application by a government or IGO proceeds to contracting, the "Special Provision Relating to Intergovernmental Organizations or Governmental Entities" will be included in the applicant's Registry Agreement.

10. Why are applications from Supported Applicants considered specialized?

A new gTLD application from an applicant that qualifies for the Applicant Support Program (i.e., a Supported Applicant) is different from a general application because of the reduced application fee, the receipt of bid credits in any auctions to resolve contention, and restrictions during contracting. Learn more

11. What is an "Exclusive Use" TLD?

An Exclusive Use TLD is a TLD wherein all domain name registrations will be registered to, and maintained by, its registry operator for the Exclusive Use of the registry operator or its Affiliates. The registry operator will not be permitted to sell, distribute, or transfer control or use of any registrations in the gTLD to any third party that is not an Affiliate of Registry Agreement. Learn more

12. What is a "Sponsored TLD"?

ICANN will not use the term "sponsored" as it relates to application types in the next round of the New gTLD Program. However, there are some gTLDs from previous rounds of the program that are considered sponsored. These are gTLDs that are specialized and have a sponsor representing the particular community that is most affected by the gTLD. The sponsor carries out delegated policy-formulation responsibilities over many matters concerning the gTLD. The closest equivalent to this gTLD type in the Next Round would be a Community gTLD.

13. Can a TLD that is a generic term be used in a specialized way?

Yes, this is possible depending on how the applicant intends to use the TLD and whether the applied-for TLD qualifies for Brand TLD designation or a Code of Conduct exemption. There may be cases where a generic term is being used in a specialized way, in which case a Community gTLD may qualify as a Brand TLD or for a Code of Conduct exemption. For example, a family with the last name "GenericTerm" may apply for the .GENERICTERM string and designate the applied-for TLD as a Community gTLD, restrict registration eligibility to its family members (the defined community), and qualify for Code of Conduct Exemption (Exclusive Use designation).

14. Can an application type be changed?

A request to change an application type may or may not be permitted. For example, if an applicant designates their application as a Community Application (which can only be done during the initial application process), the applicant is not permitted to request to change the application type to a non-Community Application at a later stage. The designation of a Geographic Name cannot be changed either.

15. Can an applied-for string have more than one application type?

Yes, a specialized application may qualify for more than one designation. Learn more

16. Which types of strings are not permitted to be applied for?

• Already delegated TLDs
• gTLD strings that were applied for in previous gTLD rounds and whose applications are still being processed
• Existing Country Code Top-Level Domains (ccTLDs)
• Strings currently requested as IDN ccTLDs
• All other one- or two-letter ASCII strings
• Strings on the Blocked Names list
• Strings on the Reserved Names list (unless the applicant is qualified to use the exception process to apply for a limited international IGO-INGO name)
• Closed Generics

Learn more

2. Geographic Name Applications

1. Which types of strings are considered Geographic Names?

Applicants are permitted to apply for the following types of strings, including their allocatable variant string(s), which are considered Geographic Name gTLDs:

• Name of capital city of any country or territory (in any language) listed in the ISO3166-1 standard;
• City names, where the applicant declares that it intends to use the gTLD for purposes associated with the city name;
• An exact match of a sub-national place name, such as a county, province, or state, listed in the ISO 3166-2 standard;
• Strings listed as a UNESCO region or appearing on the Geographic Regions section of the "Standard country or area codes for statistical use (M49)".

The 5 regions recognized by UNESCO include: Africa, Arab States, Asia and the Pacific, Europe and North America, Latin America and the Caribbean (as of May 2025).

Applicants may choose to identify their applied-for string as a Geographic Name during the application process. However, regardless of whether or not an applicant designates its applied-for string as a Geographic Name, ICANN will evaluate whether an applied-for string meets the criteria for a Geographic Name, because these types of applications must satisfy additional requirements to be approved.

2. What is the process for evaluating Geographic Names?

All applied-for gTLD strings and their allocatable variant strings will be reviewed according to the requirements in the Geographic Names section of the Applicant Guidebook regardless of whether the application indicates it is for a Geographic Name. The processing of Geographic Names comprises:

• Geographic Names Identification, which is a string-level check, conducted during the string evaluation phase of the New gTLD Program: Next Round, and
• Geographic Names Review, which is the verification and substantive evaluation of application responses for strings determined to be geographical. This review takes place during the application evaluation phase of the next round.

3. What are the requirements to apply for a Geographic Name?

Applicants for a Geographic Name must identify and consult with relevant governments or public authorities and determine what level of government support is required. Applicants will need to supply documentation of support or non-objection, including a signed letter from the relevant government or public authority.

4. Are applicants permitted to apply for a country or territory name as a Geographic Name?

No. Applicants are not permitted to apply for country or territory names as documented in the ISO 3166-1 standard (ISO Online Browsing Platform). A string will be considered to be a country or territory name if:

1. It is an alpha-3 code listed in the ISO 3166-1 standard.
2. It is a long-form name listed in the ISO 3166-1 standard, or a translation of the long-form name in any language.
3. It is a short-form name listed in the ISO 3166-1 standard, or a translation of the short-form name in any language.
4. It is the short- or long-form name associated with a code that has been designated as "exceptionally reserved" by the ISO 3166 Maintenance Agency.

5. It is a separable component of a country name designated on the "Separable Country Names List," or is a translation of a name appearing on the list, in any language. Permutations and transpositions of the following strings are reserved and unavailable for delegation:

   1. Long-form name listed in the ISO 3166-1 standard.
   2. Short-form name listed in the ISO 3166-1 standard.
   3. Short- or long-form name association with a code that has been designated as "exceptionally reserved" by the ISO 3166 Maintenance Agency.
   4. Separable component of a country name designated on the "Separable Country Names List, or is a translation of a name appearing on the list, in any language.

   Strings resulting from permutations and transpositions of alpha-3 codes listed in the ISO 3166-1 standard are available for delegation, unless the strings resulting from permutations and transpositions are themselves on that list. Permutations include removal of spaces, insertion of punctuation, and addition or removal of grammatical articles like "the." A transposition is considered a change in the sequence of the long or short–form name, for example, "RepublicCzech" or "IslandsCayman."

6. It is a name by which a country is commonly known, as demonstrated by evidence that the country is recognized by that name by an intergovernmental or treaty organization.

5. Are applicants permitted to apply for a city name as a Geographic Name?

Applicants are permitted to apply for a city name where the applicant declares that it intends to use the gTLD for purposes associated with the city name. An application for a city name will be subject to the same requirements as Geographic Names (i.e., they will require documentation of support or non-objection from the relevant governments or public authorities) if:

• It is clear from statements within the application that the applicant will use the gTLD primarily for purposes associated with the city name; and
• The applied-for string is a city name as listed on official city documents.

City names present challenges because they may also be generic terms or brand names, and in many cases are not unique. Thus, city names are not universally protected.

6. What recourse does a city government have if an applicant applies for a string that matches the city name but the applicant does not intend to use the string in a manner related to the city?

City governments with concerns about strings that are duplicates, nicknames, or close renderings of a city name should not rely on the evaluation process as the primary means of protecting their interests in a string. Rather, relevant concerned parties may elect to file a formal objection to an application that is opposed by the relevant community, or may submit its own application for the string.

3. Reserved Name Applications

1. What are Reserved Names?

A Reserved Name is a string designated for a specific entity, and cannot be registered by any other applicant. Strings on the Reserved Names list may be applied for, but only through an exception process by the relevant entity, which must provide appropriate documentation for verification. The entities that can apply for their relevant Reserved Names are:

• Red Cross Red Crescent (RCRC)
• International Olympic Committee (IOC)
• International Governmental Organization (IGO)
• International Non-Governmental Organizations (INGO)

See more information in Section 6.2.2.2 of the Applicant Guidebook.

2. What kind of documentation is required to apply for a Reserved Name?

• Certification of Incorporation and, if applicable, letter from parent organization;
• Documentation of support or non-objection including a signed letter from the relevant public authority (if applicable).

If there is reason for doubt of the authenticity of the documentation provided, ICANN may consult with the relevant authorities for further verification.

4. Community Applications

1. What is a Community gTLD?

While there is no ICANN policy that defines "community," as it relates to a Community gTLD, this type of top-level domain generally is operated to benefit a specific group of people who share an identity, interest, purpose, or other common denominator (e.g., cultural or linguistic group, regional community, professional organization, etc.).

An applicant that designates its applied-for string as a Community gTLD is required to have a Specification 12 in the applicable Registry Agreement with ICANN.

2. What types of entities can apply for a Community gTLD?

Any applicant can designate its applied-for gTLD string as Community gTLD. However, applications for Community gTLDs must undergo a conditional evaluation (i.e., Registry Commitments Evaluation (RCE)), which requires payment of an additional fee, and will pay for and undergo the Community Priority Evaluation (CPE) if the applicant elects to use the CPE to resolve contention, if contention with the applied-for Community gTLD string occurs. Specifically, all Community Applications must pass the RCE in order to proceed in the program. Therefore, applicants are cautioned to carefully consider whether they believe their applications meet the relevant evaluation criteria before designating their applied-for TLD as a Community gTLD.

3. When can an applicant designate its application as a Community Application?

An applicant's designation of its application as "community" may only occur during the initial application submission stage and cannot be changed. The community designation is inflexible because a Community Application obtains priority over other applications if the applied-for TLD is in contention and passes the Community Priority Evaluation (CPE).

4. Does Community Priority Evaluation (CPE) determine community designation?

No. CPE is a contention resolution mechanism used to evaluate whether a Community gTLD should receive priority over other applications for the same string (i.e., in contention). Any applicant can designate its applied-for gTLD string as Community gTLD.

5. How can an applicant apply for a Community gTLD?

An applicant can only designate its applied-for string as a Community gTLD during application submission. After the application is submitted, applicants cannot request to designate the application type as a Community gTLD (or request to change from a Community gTLD to a non-Community gTLD) as an Application Change Request (ACR). Applicants that designate their applied-for strings as Community gTLDs will be required to answer a series of additional application questions. These applicants will be prompted to submit the required documentation and must pay an additional fee for the Registry Commitments Evaluation.

6. What is a Community Applicant required to submit as part of its application?

An applicant for a Community gTLD (i.e., Community Applicant_ must:

• Answer specific application questions with respect to the Community Application, including those about the community it represents.
• Provide proposed Community Registration Policies which, at a minimum, must include details about registrant eligibility and naming selection;
• Submit written endorsement by one or more established institutions representing the community it names.

Proposed Community Registration Policies will be evaluated as part of the Registry Commitment Evaluation process. The information related to the community that the applicant claims to represent, as well as any endorsements, will be evaluated if an applicant elects to participate in Community Priority Evaluation.

7. What should applicants know about ICANN's Community Registration Policies?

A Community Applicant must propose and obtain ICANN's approval of Community Registration Policies for inclusion in Specification 12 of the applicable Registry Agreement. At a minimum, the proposed policies must include details about who would be allowed to register domain names under the applied-for string (i.e., registrant eligibility) and what kinds of second-level domains will be permitted to be registered (i.e., naming selection). If the applicant does not have any approved Community Registration Policies, the application would not be able to proceed and would be ineligible to participate in the Community Priority Evaluation.

ICANN will conduct the Registry Commitments Evaluation to evaluate the proposed Community Registration Policies against specific criteria to ensure such policies proposed by applicants for inclusion in the applicable RA are enforceable as a practicable matter and are compatible with the ICANN Bylaws.

8. What written endorsement is permitted?

A Community Applicant must provide a written endorsement for the application by one or more established institutions that represent the community. The written endorsement must:

• Come from one or more organizations associated with the community that is named in the application.
• Clearly express support for the application.
• Be authentic; the identity of the organization must be verifiable;
• Include a rationale or explanation for expression of support (or opposition).
• Detail the process used by the organization to decide on support (or opposition).

The written endorsement should come from a well-established, directly relevant organization – even if that organization is small – rather than a large but loosely associated entity.

9. What is the advantage of submitting a Community Application?

Community Applications are eligible to participate in Community Priority Evaluation (CPE). CPE is a conditional evaluation used to determine whether a Community Application should receive priority over other applications for the same string. This provides an additional opportunity for Community Applications to resolve contention beyond the Replacement String Process or ICANN auction, which are mechanisms available to all applicants.

Note: If the applied-for Community gTLD string also qualifies as a Brand TLD, the option for a Brand String Change would also be available for such applicants.

5. Brand TLD Applications

1. What is a Brand TLD?

A Brand TLD allows a company, organization, or individual brand owner to use its own brand name as its top-level domain instead of something like ".com", ".org", or ".net".

The relevant Registry Agreement of a Brand TLD will include Specification 13, which includes an exemption to the Code of Conduct (Specification 9 of Registry Agreement).

2. What entities can apply for a Brand TLD?

Any applicant that is a brand owner and wants its applied-for gTLD string to be used exclusively for its brand can request a Brand TLD designation. However, for the applied-for string to qualify as a Brand TLD, the application must meet specific eligibility requirements and pass the Brand TLD Eligibility Evaluation.

3. How can an applicant apply for a Brand TLD?

An applicant can either request Brand TLD designation as part of its initial application by answering a series of application questions and submitting the required documentation, or submit an Application Change Request after the initial application. There is an additional fee for the Brand TLD Eligibility Evaluation.

4. What does a Brand TLD applicant need to submit?

A Brand TLD applicant (e.g., organization) must:

• Answer specific application questions with respect to its dot brand status; and
• Submit one or more Signed Mark Data (SMD) files from the Trademark Clearinghouse (TMCH) to prove that its brand name is a registered trademark.

Find out more about SMD files and TMCH requirements here.

5. What preparatory steps should a Brand TLD applicant take with the Trademark Clearinghouse (TMCH) before applying?

Prior to submitting an application, a Brand TLD applicant must have valid SMD file(s) covering the exact brand name the applicant wants to use as a TLD. If the applicant wants to apply for any variant string(s) in addition to the primary Brand TLD string, such applied-for variant string(s) must have a valid SMD file as well. The applicant should confirm that the descriptions of the goods and services in the SMD file are complete and correct, and that they include any word the applicant may want to use in the Brand String Change request. The vetting process in the TMCH for SMD file creation can take several months to complete – start early!

6. Can an applied-for Brand TLD string be a generic term?

Yes, some applied-for Brand TLD strings may be generic terms in the sense that the string can be found in the dictionary. However, via the Brand TLD Eligibility Evaluation, similar to the review of a trademark, the brand should be differentiated from that generic good or service. Pursuant to the Registry Agreement, a Brand TLD application cannot be a general application type.

6. Internationalized Domain Name (IDN) and Variant String Applications

1. What is an Internationalized Domain Name (IDN)?

IDNs (Internationalized Domain Names) are domain names that include characters (known as "code points") other than the letters "a" to "z", "A" to "Z", numbers 0-9, and hyphen "-" in Basic Latin (ASCII). IDNs enable domain names to be expressed in other languages and scripts such as Arabic, Chinese, Thai, and others. IDNs allow people to access online resources using their native scripts, promoting greater global inclusion and choice.

An IDN generic top-level domain can be represented in two ways:

• U-label: The actual Unicode characters in Normalization Form C (NFC) of the Unicode (e.g., .شبكة)
• A-label: The equivalent ASCII version created by using the Punycode algorithm (RFC3492) prefixed with "xn--" (e.g., xn--ngbc5azd)

2. What is a variant string? What is the difference between a primary string and a variant string?

A primary string is the main gTLD string being applied for or an existing gTLD. A variant string is generated by applying the Root Zone Label Generation Rules (RZ-LGR) to the primary string. Variant strings are considered the "same" by the script community as defined in the RZ-LGR. They are categorized as allocatable variant strings (can be applied for as gTLDs) and blocked variant strings (cannot be applied for as gTLDs). Together, the primary string and its respective variant strings make up a variant string set.

3. What rules must IDN gTLDs follow?

IDN gTLDs must meet the technical standards defined by the IDNA2008 (see RFCs 5890, 5891, 5892, 5893 and their successors) and the applicable version of Root Zone Label Generation Rules (RZ-LGR).

4. What are the Root Zone Label Generation Rules (RZ-LGR)?

RZ-LGR are a set of technical rules used to determine a valid generic top-level domain (gTLD) string and its variant string, along with the disposition of the variant strings, i.e. 'allocatable' (can be applied for as gTLDs) and 'blocked' (cannot be applied for as gTLDs).

5. In which scripts can IDN gTLDs be applied for?

An applicant can apply for an IDN gTLD in any script that is currently supported in the latest version of the Root Zone Label Generation Rules (RZ-LGR). The New gTLD Program: Next Round will use RZ-LGR version 6, which includes rules for 27 scripts or writing systems, namely: Arabic, Armenian, Bangla, Chinese (Han), Cyrillic, Devanagari, Ethiopic, Georgian, Greek, Gujarati, Gurmukhi, Hebrew, Japanese (Hiragana, Katakana, and Kanji [Han]), Kannada, Khmer, Korean (Hangul and Hanja [Han]), Lao, Latin, Malayalam, Myanmar, Oriya, Sinhala, Tamil, Telugu, Thaana, and Thai.

If a potential applicant wants to apply for a gTLD in a script that is not included in the RZ-LGR version 6, the applicant must work with the relevant script community to get it integrated into the RZ-LGR.

Need help getting started? Contact ICANN at globalsupport@icann.org. Learn more about the community process in developing the LGR procedure here. The applicant may be able to apply in the future, if the relevant script has been integrated and is available in the applicable version of RZ-LGR.

6. Can variant strings be applied for along with the primary string?

Yes, but only its allocatable variant strings can be applied for along with the primary string. An applicant must include all desired allocatable variant strings together with the primary string in its application during the initial submission. No variant strings can be added later within the same round.

All applied-for variant strings must be calculated by the RZ-LGR as allocatable variant strings and the applicant must ensure that, if the application proceeds to delegation, the primary and variant strings must be managed by the same registry operator and use the same backend registry service provider, along with other requirements as defined.

7. Can applied-for variant strings be withdrawn after initial submission of the application?

An applicant can withdraw applied-for variant string(s) after applying without impacting other primary or variant strings in the application. However, if the primary string is withdrawn, all of the applied-for variant strings will also be withdrawn.

8. Can a variant string of an existing gTLD be applied for?

A variant string of an existing gTLD can only be applied for if the applicant is the registry operator for the existing gTLD delegated in the 2012 round of the New gTLD Program. As a one-time exception, these applications will be prioritized ahead of all other new gTLD applications.

9. Can an applicant choose which string will be the primary string?

Yes, and this should be done conscientiously because choosing a different primary string can change which variant strings are allocatable or blocked. The LGR Tool can be used with the RZ-LGR to help applicants find out if there are any variant strings, and if so, which variant strings are allocatable or blocked, and explore options before applying.

For registry operators applying for variant strings of their existing gTLDs, their existing gTLDs are automatically designated as the primary strings and cannot be changed.

10. How is RZ-LGR used during the application process?

For an applied-for primary string, the RZ-LGR will check if the string is valid as a gTLD and identify any allocatable variant strings (and blocked strings). For a variant string, the RZ-LGR will confirm if it is a valid gTLD, check if it is a variant string of an existing gTLD or an applied-for primary string, and determine whether it is allocatable. The TLD Application Management System (TAMS) will automatically check whether the applicant's chosen string(s) comply with the RZ-LGR when the applicant enters the string(s) into the application system.

The RZ-LGR check is part of the Domain Name System or DNS Stability Review, which is automatically performed by TAMS to ensure that an applied-for string would not adversely affect the security or stability of the DNS if the applied-for string proceeds to delegation. The DNS Stability Review verifies whether an applied-for string conforms with various technical requirements, including the IDNA2008 for IDN strings. For example, strings that mix characters from different scripts will be rejected.

11. What happens if an applied-for string is flagged as invalid or as a blocked variant string?

An applied-for gTLD string can be found invalid for many reasons. These include not being within the specified length, not conforming to IDNA2008, not complying with RZ-LGR, etc. If the applicant believes the TLD Application Management System (TAMS) made a mistake in flagging the applied-for string in the DNS Stability Review, the result can be challenged. An applicant must submit the challenge no later than 14 days before the close of the application submission period. ICANN will then review whether there was a system error. This challenge mechanism only applies to strings using scripts supported by the applicable version of the RZ-LGR.

When TAMS applies RZ-LGR on the primary string, it can flag a variant string as 'blocked.' Similarly, if the applicant believes that the tool has made a mistake, it can submit the challenge no later than 14 days before the close of the application submission period. ICANN will then review whether there was a system error.

12. How much does it cost to apply for variant strings?

The gTLD evaluation fee covers one applied-for primary string and up to four allocatable variant strings in the New gTLD Program: Next Round. If an applicant wants to apply for more than four variant strings, the applicant must pay the full evaluation fee for each additional variant string.

If the applicant is a registry operator of a gTLD delegated in the 2012 round of the New gTLD Program, the applicant can apply for up to four variant strings without paying the evaluation fee in the next round of the program.

Standard conditional fees apply for any conditional evaluations.

13. What factors should applicants consider when applying for variant strings?

In submitting applications for variant strings, applicants must explain why each applied-for variant string is necessary, and the answers will be subject to the Variant String Evaluation. A panel will review the applicant's justification based on four key criteria:

1. The meaning or intended meaning of each of the applied-for variant strings is consistent with the applied-for primary string.
2. Each variant string is recognized as equivalent to the primary string by the target user community.
3. There are real benefits and users who will gain from the delegation of the variant string.
4. Applicants have a plan to manage the technical and operational impact of using the variant string.

Each applied-for variant string must reasonably meet all of these criteria to be approved.

14. What documents do applicants need when applying for variant strings?

Applicants will need to meet the same documentation requirements for both the primary string and each of the applied-for variant strings. For the specialized application types below, documentation requirements include the following:

• Community Applications: Applicants must provide community endorsements for the primary string and each applied-for variant string.
• Geographic Name applications: Applicants need letters of support or non-objection from the relevant governments or public authorities for the primary string and each applied-for variant string.
• Brand TLD applications: Applicants must show that the primary string and each applied-for variant string matches registered trademarks that the applicant owns and uses.

All applied-for variant strings are evaluated as part of the set with the primary string. Complete documentation is essential for each applied-for string to be approved.

15. What happens if the applied-for primary string or one of the applied-for variant strings is disqualified?

If the applied-for primary string is disqualified for any reason, the entire application – including all the applied-for variant strings – will also be disqualified and cannot move forward. However, if one of the applied-for variant strings is disqualified, the applicant can submit an Application Change Request (ACR) to remove that specific variant string. If the ACR is approved, the rest of the gTLD strings in the application, consisting of the primary string and any remaining applied-for gTLD variant strings, can proceed.

7. Exclusive Use TLDs

1. How is "Affiliate" defined in the context "Exclusive Use TLD"?

As defined in Section 2.9(c) of the Base Registry Agreement: (i) "Affiliate" means a person or entity that, directly or indirectly, through one or more intermediaries, or in combination with one or more other persons or entities, controls, is controlled by, or is under common control with, the person or entity specified, and (ii) "control" (including the terms "controlled by" and "under common control with") means the possession, directly or indirectly, of the power to direct or cause the direction of the management or policies of a person or entity, whether through the ownership of securities, as trustee or executor, by serving as an employee or a member of a board of directors or equivalent governing body, by contract, by credit arrangement or otherwise.

2. How does an application obtain the designation of "Exclusive Use TLD"?

An applicant that seeks to designate its applied-for string as Exclusive Use must undergo the Code of Conduct Exemption Evaluation. Note that Specification 13 of Registry Agreement includes an exemption to the Code of Conduct (Specification 9 of Registry Agreement). However, in some cases an applicant may not qualify for Specification 13 but subsequently be eligible for Code of Conduct Exemption.

3. Are all Brand TLDs considered to be for Exclusive Use?

Yes. An applicant that has qualified for a Brand TLD designation must include Specification 13 in its Registry Agreement for that TLD, which includes a note of exemption for Specification 9 (Code of Conduct). However, a Brand TLD may also register domains to trademark licensees.

4. Can a Community gTLD also be Exclusive Use TLD?

Yes, a Community gTLD can be for Exclusive Use (e.g., like a Brand TLD). Please note that, in some cases, a Community Applicant may not qualify or choose to apply for designation as a Brand TLD but the applied-for gTLD could still qualify for a Code of Conduct Exemption, thus allowing the registry operator to limit registrations to the registry operator and its affiliates.

5. Can a Geographic Name also be Exclusive Use TLD?

Yes, .HELSINKI and .STOCKHOLM are examples of existing Geographic Name TLDs delegated as a result of the 2012 Round of the New gTLD Program.

6. Do Exclusive Use TLDs have to be Brand TLD, Community gTLD, or Geographic Name?

No. Any TLD type, as long as it meets the Code of Conduct Exemption criteria, can be designated for Exclusive Use.

7. Is a "restricted TLD" the same as an "Exclusive Use TLD"?

ICANN does not formally use the term "restricted" as it relates to TLD types. However, in general, a TLD that has restrictions on eligibility will differ from a "Closed or Exclusive Use TLD" in that registration of domain names within the TLD is not limited to only the registry operator and Affiliates; instead, registration is limited to a particular group defined by the registry operator (e.g., a community or registrants within a specific geographic area).

8. Overlap Between Application Types

1. Can a Community gTLD be a Brand TLD?

Yes. It is possible for an applicant to designate its application for a TLD as a community and also complete Brand TLD eligibility evaluation and qualify as a Brand TLD. In this situation, the registry operator would have both a Specification 12 and Specification 13 in its Registry Agreement.

2. Can a Geographic Name be a Brand TLD?

No. It is unlikely that a geographic name could be trademarked and operated as a Brand TLD for that particular geographic area (e.g., "City" has a trademark for "City" and undergoes Brand TLD Eligibility evaluation). However, there may be cases where a brand name is the same as a name of a geographic area. In these cases, the applicant for the Brand TLD may have to show, or come to an agreement with the relevant government authority, that the TLD will be operated as a brand, unrelated to the geographic area. For example, please see here for more information on the history related to the application for .AMAZON in the 2012 round of the New gTLD Program and the outcome of discussions between the applicant and the relevant governmental authorities of the Amazon region.

3. Can a Geographic Name be a Community gTLD?

Yes. In this case, the application would have to undergo Geographic Names Review and, in addition, the relevant Registry Agreement would include a Specification 12 if the application proceeds to delegation.

9. Non-Permitted Strings

1. What are Blocked Names?

Blocked Names are gTLD strings that are not eligible to be applied for. The following types of gTLD strings and their allocatable variant string(s) are on the Blocked Names list:

• Special-Use Domain Names. (See list: IANA's Special-Use Domain Names Registry)
• Names associated with technical standards bodies.
• Country or territory names in relation to Geographic Names.
• Three-letter ASCII country codes.
• ICANN-related names and other entities in the DNS ecosystem

2. What are "Closed Generics"?

In 2013, the ICANN Board's New gTLD Program committee defined a "Closed Generic" as a "TLD string that is a generic term and is proposed to be operated by a participant exclusively for its own benefit."

The term "closed" refers to a gTLD wherein registration is limited exclusively to the registry operator and its affiliates (See Specification 11, Section 3(d) of the gTLD Registry Agreement).

A definition of a "generic" string can be found in ICANN's gTLD Registry Agreement: "A string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others." (See Specification 11, Section 3 (d)).

In January 2024, the ICANN Board determined that applications for Closed Generic applications "will not be permitted until such time as there is an approved methodology and criteria to evaluate whether or not a proposed closed domain is in the public interest."

Currently, ICANN is accepting self-assertion as part of the application process that the applicant does not intend to operate a gTLD as a "Closed Generic". If ICANN receives comments regarding a string (e.g., via Application Comment Forum) and concerns regarding "genericness," ICANN would review the comments and string at that time.

3. Can Closed Generics be applied for during future rounds of the New gTLD Program?

Unless and until the Generic Names Support Organization (GNSO) develops and the ICANN Board adopts a policy that permits the use of Closed Generics, including a "methodology and criteria to evaluate whether or not a proposed closed domain is in the public interest", per the 2024 GAC Advice – Hamburg Communiqué: Board Action, Closed Generics cannot be applied for.