String contention occurs when there is more than one application for an identical or similar string. A contention set is a group of applications that were determined to be identical or similar visually, aurally, or in meaning to other applied-for generic top-level domain (gTLD) strings.
Contention sets composed of identical applied-for primary strings and/or their variant strings will be identified and published by ICANN on Reveal Day. Contention sets may be further identified or modified depending on the outcome of applicable processes and evaluations, as described below.
Contention is between or among applications for the same TLD string and requires formal resolution to ensure that only one application per contention set proceeds to delegation. The contention resolution process is a critical safeguard for avoiding user confusion while maintaining Domain Name System (DNS) stability and integrity.
For a full explanation of string contention and contention resolution procedures, see Module 5 Contention Set Resolution of the Applicant Guidebook.
String Contention
String contention occurs when multiple applicants apply for identical or confusingly similar gTLD strings, including their allocatable variants.
String contention can manifest in two forms: Direct contention and indirect contention.
Direct contention refers to strings that directly conflict with each other, such as two applications for the exact same string or variants thereof.
Indirect contention involves applications that do not directly conflict with each other, but become linked through a chain of contention.
For example:
- Application A is in contention with Application B.
- Application B is in contention with Application C.
- Applications A and C are in indirect contention.
This type of contention may occur as a result of, for example, a String Confusion Objection. In the situation in which Application C files a successful String Confusion Objection against Application B and they are subsequently placed in contention, where previously there was no contention between Applications B and C. As a result, Applications B and C are in direct contention, and Applications A and C are in indirect contention.
Learn more in the String Contention and Its Resolution Topic Overview and 5.2 String Contention and Contention Resolution Procedures of the Applicant Guidebook.
How Contention Sets Are Formed
Contention sets may be identified at several checkpoints throughout the application process.
- Reveal Day: Applications are published publicly and applications for identical strings are placed in contention with each other.
- String Confirmation Day: Finalized applied-for strings are published and identical strings remain in contention, though no new contention sets can be created at this stage due to the replacement string mechanism (though some may be resolved via this mechanism).
- Singular/Plural Notifications: These may create new or updated contention sets if ICANN receives and subsequently confirms notification that two applied-for strings are singular and plural forms of the same word in the same language. If ICANN confirms that an applied-for string is the singular or plural version of an already delegated string, the application for the new applied-for string cannot proceed.
- If an applicant files a String Confusion Objection against another application and the panel finds in favor of the objector by determining that user confusion is probable, both applications are placed in direct contention and referred to the resolution procedure. These objections can be based on visual similarity, aural similarity, or similarity in terms of the strings' meanings.
- String Similarity Evaluation: A panel assesses visual similarity across all applications and places strings that are evaluated to be visually confusingly similar into contention sets.
Learn more in the String Contention and Its Resolution Topic Overview and 5.2 String Contention and Contention Resolution Procedures of the Applicant Guidebook.
How Contention Sets Are Resolved
Once contention sets have been established, the applicant may voluntarily withdraw or seek resolution through one of several mechanisms.
String Replacement
After Reveal Day, applicants that designated a replacement string when submitting their application may choose to switch from their applied-for string to their replacement string via the TLD Application Management System (TAMS). This can be done only during the 14-day replacement period to avoid contention.
If an applicant chooses to switch to their replacement string, that string permanently and irreversibly replaces their original applied-for string. Applicants cannot switch back to the originally applied-for string after the replacement period ends.
Although choosing a replacement string may help to avoid contention, it does not guarantee that the replacement string will not be subject to a contention set after String Confirmation Day as a result of Singular Plural Notification, String Similarity Evaluation, or String Confusion Objection.
For more information, refer to Replacement Strings Topic Overview and 5.1 Replacement Strings of the Applicant Guidebook.
Brand String Change
.Brand TLD applicants can choose to resolve contention by appending a term from their trademark registration to their applied-for string, provided that the term appears in the description of goods and services of the applicant's Trademark Registration or equivalent document. The revised string must not create contention or expand an existing contention set.
For more information, refer to the String Contention and Resolution Frequently Asked Questions and 5.3 .Brand String Change Requests of the Applicant Guidebook.
Community Priority Evaluation
An applicant that designates their application a Community TLD can choose to participate in Community Priority Evaluation (CPE) for an additional fee. This evaluation is conducted by a third-party that assesses the application against specific criteria designed to determine the applicant's relationship with the identified community.
If the applied-for Community TLD successfully passes CPE, the application is awarded priority status and can proceed to the next steps in the New gTLD Program, while other applications in the contention set will not be allowed to continue. If multiple applicants for the same applied-for string elect to go through CPE and prevail, they would proceed to an ICANN Auction. If an application for a Community TLD is not successful in CPE, it will proceed to an ICANN Auction.
For more information about CPE, refer to the Community Priority Evaluation (CPE) Topic Overview, Community Priority Evaluation (CPE) Vendor Evaluation Guide, and 5.4 Community Priority Evaluation of the Applicant Guidebook.
ICANN Auction
An ICANN Auction serves as the contention resolution mechanism when other resolution methods are not available or were unsuccessful (e.g., CPE). Once the auction has concluded, only one of the participating applications in direct contention for an applied-for gTLD will be eligible to proceed toward delegation, pending the outcome of the Applicant and Application Evaluation and the successful execution of a contract for the applied-for gTLD. In the case of indirect contention, it is possible for more than one application to prevail in an auction and proceed towards delegation.
Learn more about the ICANN Auction process in 5.6 ICANN New gTLD Auction of the Applicant Guidebook.
Private Resolution Prohibition
Applicants are prohibited from attempting to resolve a contention set privately. This includes private auctions, settlement agreements, joint ventures, or compensation offered in exchange for withdrawing or modifying an application.
From Reveal Day until contention resolution is finalized, applicants are prohibited from discussing or negotiating settlement agreements or post-auction transfer arrangements in any manner with another applicant in contention for the same string regarding any contending strings. This prohibition extends to both direct communication and indirect communication through intermediaries, agents, or third parties.
For more information, see 5.2.3 Prohibition of the Private Resolution of String Contention by Applicants of the Applicant Guidebook.
Additional Resources
Learn more about the New gTLD Program: 2026 Round.