Summary

  • ICANN’s 2026 Round geographic-name process begins with a review of every applied-for string and allocatable variant, not only applications self-designated as geographic. Geographic Names Identification determines whether the string may fall within the rules; Geographic Names Review later examines required application responses and support or non-objection documentation.
  • Applicants should preserve an evidence chain that connects the exact string, issuing authority, signatory competence, intent, scope, original document and verification route. They should distinguish remediable documentation questions from rules that prohibit delegation of country or territory names. Above all, they should report each stage accurately: identification is not rejection, a letter is not a completed review, and a completed geographic-name review is not a delegation decision.

An applicant does not avoid geographic-name scrutiny by leaving a box unchecked. In the 2026 Round, ICANN says every applied-for gTLD string—and every allocatable variant string—will be reviewed against the Applicant Guidebook’s geographic-name requirements. The first question is about the string. Only then does the process turn to the applicant’s supporting evidence.

That distinction matters. Geographic Names Identification is a string-level check during String Evaluation. Geographic Names Review is a later verification and substantive evaluation during Application Evaluation. Where government or public-authority support or non-objection is required, the record must establish more than the existence of a signed letter. ICANN’s panel can examine whether the issuer is competent, whether the communication is authentic, whether it contains the required information and whether its scope actually covers the application.

The governance lesson is narrow but consequential: identification is not rejection, a support letter is not delegation, and political visibility is not a substitute for an auditable evidentiary chain.

The screen applies before an applicant’s characterization does

ICANN’s published process begins with a universal check. All applied-for strings and allocatable variants are reviewed to determine whether they may be geographic names under the 2026 Round rules. That means an applicant’s own designation is informative, but it does not control whether the Geographic Names Panel examines the string.

This first stage should change how applicants prepare. A team should not ask only, “Do we intend to apply for a geographic name?” It should also ask whether the proposed string could match a defined geographic category when reviewed independently. ICANN’s public materials identify categories that include capital-city names, certain city names used for city-associated purposes, exact matches of sub-national place names listed in ISO 3166-2, and specified UNESCO or United Nations geographic regions.

The useful work therefore starts before a letter is requested. Applicants need a documented string analysis: the relevant language forms, the intended use, the geographic lists checked and any allocatable variants. This is not evidence that the panel will reach a particular result. It is a way to preserve what the applicant knew, checked and relied upon when the application was assembled.

Identification and review answer different questions

The process has two distinct functions. Geographic Names Identification asks whether the string falls within the applicable geographic-name rules. Geographic Names Review then examines the application response and, where necessary, the support or non-objection documentation.

Collapsing those functions creates two opposite errors. One is to treat identification as an adverse final decision. The other is to treat possession of a letter as proof that the application has cleared evaluation. Neither follows from ICANN’s published sequence.

The distinction is especially important for governance reporting. A risk register, board paper or investment memo should name the stage actually reached. “Potentially geographic,” “identified for review,” “documentation under verification” and “passed Geographic Names Review” are not interchangeable statements. They describe different facts, different uncertainties and different remaining dependencies.

The evidence must connect authority, intent and scope

ICANN explains that the review may test whether required documentation is legitimate, authoritative and complete. The Applicant Guidebook also allows the panel to confirm a communication’s authenticity through relevant diplomatic authorities or members of ICANN’s Governmental Advisory Committee, and to contact the signing entity about its intent and understanding.

For an applicant, that makes provenance part of the substance. A defensible evidence file should identify the governmental or public authority, the legal or administrative basis for its competence, the signatory’s office, the date, the precise string, the applicant and the nature of the support or non-objection. It should also preserve the transmitted document, its original format, delivery trail, translations where used and a reliable contact path for verification.

A prestigious signature does not cure an ambiguous scope. A letter that discusses a civic initiative, a local digital strategy or a broad partnership may not necessarily communicate support or non-objection for the exact gTLD application. Conversely, a concise communication can be strong evidence if its authority, subject and intent are explicit and verifiable.

Applicants should therefore treat the letter as one component of a record rather than a standalone ceremonial object. The operational question is whether an evaluator can connect issuer, authority, intent, string and application without filling gaps by inference.

Some outcomes are not remediable in the same way

The Applicant Guidebook separates missing or defective documentation from a determination that the string is a country or territory name. ICANN’s published FAQ says a country or territory name cannot be delegated and that this determination is final without additional review or challenge. Documentation problems, by contrast, may qualify for Extended Evaluation under the Guidebook’s stated conditions.

That difference should govern escalation. If the issue is documentary, the immediate task is to understand the deficiency, preserve communications and use the available process accurately. If the underlying string falls into a prohibited category, a stronger letter does not change the rule described by ICANN.

This is why the early string analysis and the later evidence file should remain separate but linked. One tests eligibility under the geographic-name definitions. The other proves the quality and applicability of support where support is required.

L3 — Build the file an evaluator can authenticate

The first control is an evidence register for every communication relied upon. Record the original filename, immutable hash, date received, sender domain, delivery channel, signatory, issuing authority, relevant jurisdiction, exact applied-for string and any variant covered. Link each assertion in the application to the document and passage that supports it.

Keep original and translated versions together, but do not let a translation silently replace the source. Record who prepared it and when. Where the authority’s competence is not self-evident, preserve the legal or administrative reference that explains it. Confirm that a verification contact remains reachable and knows the communication may be authenticated.

These controls do not guarantee a successful review. They reduce avoidable uncertainty when the panel tests legitimacy, authority, content and intent.

Sources