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
How ICANN Turned a .COM Renewal Into an Operative Contract
ICANN’s 2024 renewal of the .COM registry agreement shows where authority in internet governance actually changes form: community input becomes a proposal, the Board authorizes an institutional act, delegated officers complete the transaction, and a contract becomes the operating…

ICANN
ICANN’s Authority Chain: From Institutional Mandate to Contractual Remedy
ICANN’s power over the domain-name system is easiest to misunderstand when it is treated as a single grant of authority. The public record describes something more layered: institutional powers and accountability rules in the Bylaws, operational obligations in registry and…

ICANN
ICANN’s Authority Is a Chain, Not a Crown
ICANN can influence the global domain-name system without being a government. Its practical authority is assembled across several instruments: a California nonprofit charter, corporate bylaws, multistakeholder policy procedures, contracts with registries and registrars, technical…

ICANN
ICANN’s Authority Is Contractual Before It Is Public
ICANN can influence the global identifier system without being a government and without possessing unilateral control over every technical action that follows its decisions. Its authority is assembled from several instruments: corporate bylaws, operational agreements, registry…

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
ICANN’s Authority Is a Chain, Not a Sovereign Grant
ICANN can shape the global identifier system without possessing a general public-law mandate over the internet. Its authority changes form as it moves from corporate purpose to Bylaws, from multistakeholder policy to contractual obligation, and from contract to technical…

ICANN
ICANN’s Remedies Are Not One Appeal: Who Can Stop, Review or Reverse a Decision?
ICANN’s accountability system does not place every objection on one appellate ladder. It distributes authority among the Board, the Empowered Community, ICANN’s staff-facing reconsideration process and an independent review panel. The practical question is therefore not simply…

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
Allison Mankin and the Name-Collision Sample That Could Not Prove Its Cause
A root server can record a query for a private-looking name with great precision. The record still cannot say which application produced it, who owns the broken dependency, how many users rely on it or what a future delegation would harm. Allison Mankin’s work on RFC 8023 helps…

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