Summary

  • ICANN says every applied-for 2026 Round string, including variant strings, is subject to an initial name-collision risk assessment.
  • A high-risk result is a conditional process gate: after any relevant contention is resolved, the applicant may need a mitigation plan that is successfully evaluated before the application can proceed.

An assessment is a classification, not a root-zone result

ICANN describes name collision as a situation in which a resource name intended for one naming system is inadvertently resolved in another. In June, ICANN sought a provider for the 2026 Round Name Collision Initial Assessment and said that each applied-for string, including variants, would undergo initial risk assessment under its Name Collision Risk Management Framework.

That is a broad screening obligation, but it should not be read as a delegation decision. The RFP describes a structured, expert-driven process using quantitative analysis and, where necessary, qualitative analysis to identify strings that could create severe negative consequences if delegated. It does not identify a particular 2026 application as high risk, approve a string, or allocate a future place in the root zone.

The difference matters because a risk finding changes the decision path rather than supplying the final decision. ICANN’s applicant guidance says that, when Initial Assessment is complete, it will publish a report on methodology and findings and hold a Public Comment period. Strings not identified as high risk enter the Temporary Delegation queue. A high-risk string does not simply disappear from the program: after any contention is resolved, the applicant may propose a Name Collision High-Risk Mitigation Plan for evaluation as part of Application Evaluation in order to proceed.

The plan has a narrower job than the application

The mitigation plan is not a new pitch for the string. ICANN defines it as a plan explaining how the applicant will reduce or eliminate name-collision risks before or after delegation. The resulting question is specific: does the proposed mitigation adequately address the identified concern for the application to continue in the program?

This is different from the mechanism covered in ICANN‑044. Safeguard Assessment examines whether a string may require particular safeguards as Registry Agreement requirements. Name Collision High-Risk Mitigation Plan Evaluation concerns the risk of an applied-for string resolving unexpectedly across naming systems and the measures proposed to address that risk. Both can be conditional evaluations, but their triggers, evidence and decision surfaces are not interchangeable.

The distinction also disciplines the evidence record. A reader should separate the Initial Assessment report, a public comment, the applicant’s plan, the panel’s evaluation, any contention outcome, and any later contracting or delegation event. A score, a risk label, or a mitigation proposal is not proof that the later events have occurred.

Primary strings and variants do not have the same exit

ICANN’s variant-string FAQ gives the sharpest boundary. If any primary string is identified as high risk, the application cannot proceed until the Mitigation Plan Evaluation has completed successfully. For an allocatable variant string, the applicant may amend the application to remove the high-risk variant and allow the remainder of the application to proceed.

That produces two different governance choices. A primary-string finding can make the plan-evaluation result a condition of progression. A high-risk variant can instead force a bounded scope decision: retain it and pursue mitigation, or remove it and preserve the rest of the application. Neither choice tells the public whether the primary string will ultimately be delegated.

What the public record can establish now

The current first-party material establishes procedures and stages. It establishes that all applied-for strings are assessed, that high-risk strings can require a mitigation plan, and that a successful mitigation evaluation is needed before a primary high-risk string can proceed. It does not establish a published risk result for a named 2026 applicant, the content of an applicant’s future plan, or a future delegation decision.

For applicants, registry service providers and public-interest participants, that boundary is more useful than an early prediction. The durable record should preserve the assessment methodology, risk classification, any comment, the mitigation proposal, evaluation result, and the later decision that actually changes the application’s program status.

Sources