Cross-jurisdiction governance and policy interface.
Governance / ICANN
ICANN
ICANN governance intelligence tracks institutions, policy processes, standards activity, registry operations, accountability disputes, and implementation signals that affect internet infrastructure. BTW.

Institutional structure, policy process, and accountability trust.
Multi-stakeholder legitimacy and process clarity.
Structural policy changes usually materialize in 120d+ cycles.
Latest Coverage
Latest from ICANN
279 articles

ICANN
ICANN’s Proposed UA Dashboard Must Keep Self-Reports Separate From Tests
Two dashboard cells can both say that a service is Universal Acceptance-ready. One may contain an operator’s answer to a questionnaire; the other may contain a completed multilingual account-recovery test. The words match. The evidence does not. ICANN’s final UA guidelines now…

ICANN
ICANN’s Alternative-Name Integration Needs a Verifiable Turn-Down
ICANN’s draft model would let a gTLD registry coordinate the same name across the global DNS and another naming system. The report recommends a mandatory plan for switching that integration off. The harder governance test is whether the operator can later prove that every…

ICANN
ICANN’s New gTLD On-Call Contract Needs a Public Sunset Test
An emergency rota can succeed so well that nobody notices when it becomes the operating model. In May, ICANN described enhanced out-of-hours support for the 2026 new gTLD round as a six-month response to a defined period of pressure, followed by a return to regular business…

ICANN
ICANN Authorized Strategic Engineering Augmentation. Capacity Is Not Authority
ICANN’s Board has authorized a preferred vendor to add flexible engineering and IT capacity across strategic initiatives and ongoing services. The public rationale explains why the organization wants outside expertise. It does not show how each external function will remain below…

ICANN
ICANN’s Authority Is Layered, Contractual and Procedurally Bounded
ICANN coordinates critical Internet identifiers through a stack of instruments rather than through a single sovereign mandate. Its corporate documents define a limited mission; contracts give it leverage over many registries and registrars; affiliates perform delegated…

ICANN
ICANN’s ITP Contract Has a Release Gate, Not a Date
ICANN’s Board has approved the authority to contract for the next generation of the organization’s publishing platform while concealing several negotiating particulars. That is not unusual procurement hygiene. The more interesting governance fact is that ICANN has also named who…

ICANN
ICANN’s Authority Has Five Separate Links
ICANN’s practical power is easiest to misunderstand when mission, policy, contract, implementation and review are treated as one thing. Its public materials describe a mission centred on Internet unique-identifier coordination, while its agreements and procedures show how…

ICANN
ICANN Kept Its Strategy Unchanged Without Showing the Trigger Test
ICANN’s latest annual strategy review ended with a clear Board decision and an incomplete public chain of reasoning. After eight environmental-scan sessions involving nearly 210 entities, the Board affirmed on 6 September that its FY26–30 Strategic Plan would remain unchanged.…

ICANN
ICANN’s New Reversal Rule Opens the Record After the Board Acts
The GNSO has finally written down how the ICANN Board should reverse its adoption of a policy recommendation that has not finished implementation. The new procedure creates dialogue, voting thresholds and a public explanation. Yet the public record becomes mandatory only after…

ICANN
ICANN’s Accountability Channels: Three Review Paths, Three Different Control Surfaces
ICANN’s accountability architecture is often described as a system of checks and balances. In practice, it is better understood as three distinct routes with different triggers, eligible users, reviewers and possible effects. The difference matters when a decision affects an…

ICANN
IAB Reappoints David Lawrence; Its ICANN Handoff Notices Disagree
Three public notices now describe one liaison transition. The first put ICANN87 in November. The second put it in October. The third named David Lawrence for another term but did not say when that term takes effect. ICANN’s own calendar and Bylaws resolve most of the puzzle, yet…

ICANN
At ccNSO, Nominating a Colleague Can Still Be Self-Nomination
Five Council seats are entering selection. The rules distinguish an institution putting someone forward from support that comes from outside it.

ICANN
ICANN's NomCom Invites Process Advice, Not Candidate Testimonials
The 2027 consultation puts contributors' views on the public record. It does not turn the selection process into an endorsement campaign.

ICANN
Fifth Allocatable Variant Triggers Full Evaluation Fee
For new applicants, ICANN’s 2026 fee structure includes up to four variant strings, then charges the full evaluation fee for each additional allocatable variant.

ICANN
ICANN’s UA Guidelines Give AI Two Jobs. One Metric Cannot Measure Both
An AI assistant can suggest a better email validator. An AI-powered service can also reject the very address that validator was meant to admit. Those are opposite positions in the same control loop. ICANN’s Universal Acceptance working group now says its final guidance was…

ICANN
A Submitted gTLD Application Still Has a Seven-Day Fee Clock
A timely gTLD submission is not complete for processing until ICANN receives the evaluation fee within the separate payment window.

ICANN
Administrative Check Is a Filing Gate, Not a Merits Decision
ICANN’s Administrative Check verifies filing facts and prepares identical-string sets; it does not approve an application on its merits.

ICANN
One RSP Evaluation Can Cover Many gTLDs—Only for Qualified Services
One evaluation may be reused across gTLDs, but ICANN qualification remains tied to specific registry services.

ICANN
RSP Coverage Is a Function Map, Not a Provider Count
An applicant can name several Registry Service Providers and still leave a critical registry function uncovered. ICANN’s 2026 Round framework is role-specific: Main, DNS, DNSSEC and optional Proxy RSPs carry different functions and different limits on how many may serve a gTLD.

ICANN
Naming an RSP Is Not Contracting Confirmation
An applicant can identify a Registry Service Provider in its application, while ICANN separately seeks confirmation from that provider during contracting. The applicant’s selection, ICANN’s request and any actual RSP response are distinct evidence events.
Member Unlock
Restricted Profile Intelligence
Login is required to unlock full profile briefings and deep-dive sections.
Strategic Circle Briefing
Join to unlock strategic briefings after signing in.
Join Strategic CircleLeadership Alliance Briefing
For qualified IP-asset owners and management; sign in to unlock alliance briefings.
Join Leadership Alliance