String Evaluation, which consists of five separate assessments, focuses solely on the evaluation of the applied-for strings and their allocatable variant strings. It is designed to safeguard DNS stability while addressing stakeholder concerns. String Evaluation starts after String Confirmation Day, and partially overlaps with the Community Input, Objections and Appeals window. It is expected to take 180 days at a minimum.
During String Evaluation, applied-for strings and their allocatable variants are evaluated for uniqueness, clarity, and potential confusion with existing strings or trademarks.
String Evaluation can result in application termination, new or expanded contention sets, or additional requirements to address or mitigate risks.
Important Notes
- String Evaluation focuses on evaluating the applied-for string, not the applicant or application.
- String Evaluation begins after String Confirmation Day and is expected to last at least 180 days.
- String Evaluation overlaps with the Community Input, Objections and Appeals period.
- Clarifying questions are not issued for String Evaluations.
- String Evaluation does not follow the order of the Prioritization Draw; String Evaluation results are published at the same time for all applications.
- Each of the five assessments that comprise String Evaluation occur concurrently.
String Evaluations
String Evaluation consists of the five assessments described below, each of which is conducted concurrently. Unlike Application and Applicant Evaluation, String Evaluation does not follow the priority order established by the Prioritization Draw. Click each assessment, below, for more details and relevant resources.
ICANN will publish the outcomes of the String Evaluations on the Application Publication and Statistics (APS) Application Details page.
String Similarity Evaluation
The objective of the String Similarity Evaluation is to prevent user confusion and loss of confidence in the DNS resulting from the delegation of visually similar strings.
"Visually similar" means visually confusing strings, specifically strings so visually similar that they create a probability of user confusion if more than one of the strings is delegated.
Name Collision Initial Assessment
The Name Collision Initial Assessment aims to identify strings with a high risk of name collision.
Name collision occurs when a name intended to be used in one naming system, such as an internal corporate network, accidentally resolves in the global Domain Name System (DNS). This can cause unexpected behavior, including misdirected communication or service failures.
Once the evaluation is completed, ICANN publishes an Initial Assessment report describing the assessment, its methodology, and findings. Once the assessment report is published, the community can provide feedback on the methodology and findings via a Public Comment period.
Safeguard Assessment
The Safeguard Assessment determines if an applied-for string (including any applied-for allocatable variant strings) requires specific safeguards as contractual requirements (Safeguard Public Interest Commitments (PICs)) in the applicable Registry Agreement as it relates to consumer protection, sensitive strings, and regulated markets.
Geographic Names Identification
All applied-for strings, including any applied-for allocatable variant strings, are reviewed to identify strings that may be considered Geographic Names according to the criteria described in Section 7.5 Geographic Names. Strings identified as eligible Geographic Names must undergo Geographic Names Review as part of the Application Evaluation stage.
Singular/Plural Notifications Evaluation
Singular/Plural Notifications received during the 30 days immediately following String Confirmation Day are evaluated to determine if the relevant applied-for string represents the singular or plural form of the same word in the same language as another applied-for gTLD, an existing gTLD, a string being processed from a previous new gTLD round, or a Blocked Name.
More Information
Learn more about String Evaluation:
- Module 7 String and Application Evaluation Procedures of the Applicant Guidebook
- String Evaluation FAQs