Application Types Detailed Guide

ICANN's 2026 application round supports several types of gTLD applications:

• Standard/General Applications: Open to any eligible entity for any available string
• Brand TLD Applications: For corporations applying for their trademarked brand names
• Geographic Name Applications: For cities, regions, and other geographic identifiers
• Community Applications: For TLDs serving a specific community with demonstrated support
• IDN Applications: Internationalized Domain Names in non-Latin scripts
• Exclusive Use TLDs: For applicants who want exclusive use of their TLD
• Restricted Applications: TLDs with specific registration restrictions

A standard gTLD application is the default application type. Any eligible entity can apply for any available string that doesn't match protected categories (geographic names without government support, restricted strings, etc.).

Standard applications have the same evaluation fee and process but may face contention if multiple applicants apply for the same string.

Open gTLDs: Anyone can register a domain name under an open gTLD. Examples include .com, .org, and .net. Most commercial gTLDs are open.

Restricted gTLDs: Only eligible individuals or organizations meeting specific criteria can register domains. Examples include .bank (verified banks only), .health (verified healthcare providers), and brand TLDs (typically for internal use only).

No. Each gTLD requires a separate application and a separate $227,000 application fee. If you want to apply for multiple TLDs (e.g., .brand, .brandproducts, .brandstore), you must submit separate applications for each.

However, you can submit multiple applications simultaneously during the application window.

This is called contention. When multiple applicants apply for the same string, ICANN initiates a contention resolution process:

• Community Priority Evaluation: If one application has community designation, it may have priority
• Auction: The most common resolution method—applicants bid in an ICANN-managed auction
• Private Resolution: Applicants can agree to resolve contention privately (joint venture, one buys out the other)

The winner of the auction or resolution process proceeds to delegation.

A community gTLD application is for TLDs that serve a clearly defined community (e.g., .cat for Catalan speakers, .gal for Galicia). Community applications undergo additional evaluation to verify:

• The community is clearly delineated
• There's substantial support from the community
• The applicant has the endorsement of the community
• The TLD will be operated in the community's interest

Community designation can provide priority in contention resolution but requires additional documentation.

Geographic names include:

• Country and territory names (e.g., .paris, .tokyo)
• City names (e.g., .nyc, .london)
• Regional names (e.g., .bavaria, .quebec)
• UN country codes and ISO 3166-1 codes
• Names listed in the ISO 3166-1 standard

ICANN maintains a list of geographic names that require government or public authority support.

For geographic name applications, you must obtain government or public authority support or at least non-objection:

• Support Letter: From the relevant government or public authority explicitly supporting the application
• Documentation: Proof of the authority's jurisdiction over the geographic name
• Timing: Must be obtained before application submission

Without this support, the application will not be evaluated.

Yes, but you must have explicit government or public authority support. Many city TLDs are operated by private organizations under agreement with the city government.

Examples include .nyc (operated by a city entity), .tokyo (operated by Tokyo Metropolitan Government), and .paris (operated with city support).

Country Code TLDs (ccTLDs): Two-letter codes designated by ISO 3166-1 (e.g., .us, .uk, .de). These are not part of the new gTLD program.

Geographic gTLDs: Can be any length and represent cities, regions, or other geographic entities (e.g., .nyc, .london, .bavaria). These are part of the gTLD program.

A brand TLD application is for corporations applying for their trademarked brand names (e.g., .google, .bmw, .sony). Brand TLDs typically:

• Match the corporation's registered trademark
• Are used primarily for internal purposes (corporate websites, product authentication)
• Are not open for public registration

Brand TLD applicants must provide trademark registration evidence and demonstrate brand recognition.

Brand TLD requirements include:

• Valid Trademark: Registered trademark in at least one jurisdiction
• Brand Recognition: Evidence of substantial use and recognition
• Corporate Structure: Demonstrated organizational capacity to operate a registry
• Intent: Clear statement of intended use (typically for internal corporate purposes)

For complete details, see our Brand TLD Guide.

Technically yes, but most brand TLDs are operated as exclusive-use or restricted TLDs for internal corporate purposes. Opening a brand TLD to public registrations is possible but rare, as it:

• Dilutes the brand protection value
• Requires additional operational infrastructure
• Creates potential trademark conflicts
• Increases compliance requirements

An IDN (Internationalized Domain Name) gTLD is a TLD in a non-Latin script such as Arabic, Chinese, Cyrillic, or other supported scripts. Examples include .中文网, .السعودية, and .在线.

IDN gTLDs enable multilingual representation on the internet, serving non-English speaking communities in their native scripts.

ICANN supports 26 scripts for IDN gTLD applications, including:

• Arabic, Armenian, Bangla, Chinese (Simplified & Traditional)
• Cyrillic, Greek, Gujarati, Hebrew, Hindi
• Japanese, Korean, Lao, Myanmar, Persian
• Tamil, Telugu, Thai, Tibetan, Turkish
• Ukrainian, Urdu, Vietnamese, and more

For complete details, see our IDN Guide.

Variant strings are different representations of the same string in a script. For example, in Chinese, simplified characters (简体) and traditional characters (繁體) are variants of the same words.

When applying for an IDN TLD, you may need to address variant strings to prevent confusion and ensure users reach the intended destination regardless of which variant they type.

The base application fee is the same ($227,000). However, additional costs may include:

• Variant String Analysis: $10,000 - $30,000 for expert analysis
• RZ-LGR Integration: If script is not yet integrated into Root Zone LGR
• Community Panel Formation: For new script applications
• Translation Services: For application materials

An exclusive use TLD is a gTLD where the registry operator registers all domain names exclusively for their own use. These are typically brand TLDs (e.g., .google, .apple) where:

• The registry does not sell domains to third parties
• All domains are used internally for corporate purposes
• Registration policies restrict who can register

Benefits of exclusive use TLDs:

• Brand Control: Complete control over which domains exist
• Security: Reduced phishing risk (no third-party registrations)
• Simplified Operations: No need for public registration systems
• Cost Predictability: Lower operational costs without registrar relationships
• Trust: Users can trust any domain under the TLD is legitimate

The application process is the same as other gTLD applications, but you must:

• Clearly state your intention to operate as an exclusive use TLD
• Document your registration policies restricting access
• Explain how the exclusive use benefits your organization
• Demonstrate you have no intention to sell domains to third parties

Reserved names are strings that ICANN does not allow to be applied for, including:

• Two-letter country codes: All ISO 3166-1 two-letter codes (e.g., .us, .uk)
• ICANN internal names: .iana, .example, .test
• Redacted strings: Strings withheld for protection
• Government/international organization names: Without support

Non-permitted strings are those that:

• Conflict with existing TLDs: Including ccTLDs and existing gTLDs
• Are confusingly similar: To existing TLDs or reserved names
• Violate public policy: Strings that are offensive or contrary to public order
• Technical constraints: Strings that cannot be technically implemented

Some restricted strings are available, but they require:

• Verification of registrant eligibility (e.g., verified bank for .bank)
• Enhanced registration policies
• Ongoing compliance verification
• Additional security measures

Note that some restricted strings may already be delegated to other registries.