Summary

  • ICANN's 2026 safeguard assessment assigns applied-for gTLD strings to four risk groups. If a string qualifies, the corresponding Safeguard Public Interest Commitments must enter its Registry Agreement without modification.
  • The assessment does not halt an application. At ICANN87, the Governmental Advisory Committee asked how the resulting contract duties would be monitored and enforced, and which laws' jurisdiction would apply.

A proposed top-level domain can sound like an authority before anyone has registered a name beneath it. Medicine, finance, education and public services are the examples the Governmental Advisory Committee raised at ICANN87 in Bali. The committee's October communiqué then named an awkward division of labour: the Safeguard Assessment cannot prevent an application from proceeding, but it can place enforceable Public Interest Commitments in the eventual Registry Agreement. The warning label is attached to the contract, not to a stop button.

The 2026 Applicant Guidebook shows the machinery. Every applicant answers Question Set 10 on safeguards, mission and purpose; the answers become public with the application. Once the comment period closes, ICANN decides whether the proposed string falls into a safeguard group. The assessment takes account of the application and comments rather than treating the applicant's own description as a verdict. The determination feeds contracting and, because it does not affect progression, cannot be challenged through the guidebook's Extended Evaluation and Evaluation Challenges process.

There are four groups: regulated sectors with open entry, highly regulated sectors with closed entry, strings with cyber bullying or harassment potential, and inherently governmental functions. The guidebook ties each to prescribed safeguards. If ICANN assigns a string to one or more groups, the applicable Safeguard PICs must be inserted into Specification 11 of its Registry Agreement without modification. Mandatory PICs already belong in every registry contract; the safeguard set is the extra layer for particular strings. Applicant-proposed Registry Voluntary Commitments are a separate instrument.

That makes the classification consequential even without veto power. A registry serving a sensitive label may have to pass requirements through registrar and registrant agreements, check credentials, or handle security obligations depending on the group. Those duties are contract terms, and ICANN says it enforces Specification 11. Yet a contractual promise is valuable only when someone can identify a breach, establish which obligation applies, and act on it. The GAC's questions about monitoring, enforcement and applicable-law jurisdiction go directly to that operating cost.

A buyer, public agency or would-be objector should therefore ask for a chain of records: the public Question Set 10 response, the comment record, ICANN's group determination, the exact Specification 11 terms and the compliance history once a registry operates. The assessment decides which contract clauses follow a string; other procedures decide other objections and outcomes. Calling the assessment a safety approval would give it a power the guidebook explicitly withholds.

The cited documents do not identify a 2026 application whose safeguard terms have been signed and tested. That contract, followed by a public enforcement record, would show whether classification has practical force. Until then, the political wager is plain: ICANN is asking the future contract to do work that the assessment itself cannot do at the application gate.

Sources