Topic
Institutional Legitimacy
Within the Topic facet, Institutional Legitimacy topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.
CASE FILE
Who Could Stop Site Finder? VeriSign’s Wildcard and the Birth of Registry-Service Preclearance
When VeriSign changed the answers returned by the authoritative .COM and .NET servers in September 2003, the registry operator controlled the technical switch. ICANN did not itself edit the zones: it could demand rollback, invoke the contracts and threaten enforcement. Technical…
CASE FILE
Registry.Africa and the Remedy Gap: Why DCA’s IRP Victory Did Not Reverse the .AFRICA Delegation Chain
DotConnectAfrica secured a consequential finding that ICANN had mishandled its `.AFRICA` application, but the ruling neither transferred the string nor erased the rival operator’s contract. The result becomes intelligible only when the dispute is followed across the separate…
CASE FILE
Emergency Custody, Not Ownership: The .WED Failure and ICANN’s EBERO Chain
The .WED case is not chiefly a story about a failed registry. It is a test of how contractual emergency powers, escrowed records, root-zone changes and a temporary operator can preserve a top-level domain without deciding who may hold its permanent registry role next. The record…
CASE FILE
Who Could Authorise .AMAZON? From GAC Objection to Enforceable Safeguards and Root Delegation
The dispute over .AMAZON was not resolved by a single veto, judgement or bargain. It advanced only when distinct powers aligned: governments advised, an accountability panel identified defective decision-making, the ICANN Board changed programme status, negotiators converted…
CASE FILE
Who Could Stop the .ORG Sale? PIR, ICANN and the Legal Objects Behind the Ethos Capital Rejection
The proposed transfer of Public Interest Registry to an Ethos Capital affiliate drew petitions, government scrutiny and accountability challenges, but none operated as a freestanding veto. The deal failed because authority was divided among a private purchase agreement, corporate…
CASE FILE
Who Could Restore the Caps? Namecheap and the .ORG/.INFO Accountability Chain
The removal of historical wholesale price caps from the .ORG and .INFO registry agreements produced thousands of objections, a successful accountability challenge and a court-confirmed award, yet none of those events rewrote the contracts. The case shows why public participation…
CASE FILE
The Contract Clause That Stopped the .ORG Sale
ICANN did not stop the proposed Ethos Capital acquisition through a registrant vote, a court injunction or a change to the domain-name system. It used a prior-consent clause in Public Interest Registry’s registry agreements—an ex ante gate that public opposition could influence…
CASE FILE
A $135 Million Auction, a Funding Agreement and .WEB’s Ten-Year Wait
A US$135 million auction removed six rival .WEB applications from contention, but it did not determine who controlled the winning position, whether the funding arrangement complied with the 2012 rulebook, what independent review could actually remedy, or which company would…
CASE FILE
A .AFRICA Process Victory Without the String
DotConnectAfrica’s 2015 Independent Review Process victory established that ICANN’s Board had handled its .AFRICA application inconsistently with ICANN’s Articles and Bylaws. The Board then preserved the undelegated string and returned the application to evaluation. Neither the…
CASE FILE
How a 14-Point Score Eliminated Six .HOTEL Applicants
A single Community Priority Evaluation report did not award a registry or place `.HOTEL` in the DNS root. It did something narrower and, for six competitors, immediately decisive: it supplied the score that activated ICANN’s pre-adopted rule for ending their applications’ route…
CASE FILE
The .ECO Community That Became a Registry Right
Big Room’s 14-point Community Priority Evaluation did not establish ownership of environmentalism or place .ECO in the DNS root. It gave one community-based application priority inside a four-way contention set. Narrow review left that score intact; a later registry agreement and…
CASE FILE
When .us Withdrew the Proxy Option
A proxy service could publish its own contact details while keeping a customer’s identity in a confidential file. In .us, that arrangement collided with a federal registry contract interpreted to require the registry to hold and publicly display the actual holder’s data. The…
CASE FILE
A Hijacked Domain Put the Proxy Holder in the Control Chain
The Solid Host dispute exposed a narrow but durable governance problem: a privacy intermediary can deny that it is the registrar while still appearing as the registrant, holding the customer’s identity, evaluating a theft complaint and occupying a practical route to restoration.…
CASE FILE
When Estonia Split an Identity Card in Two
Estonia’s 2017 eID crisis was not simply a chip failure or an emergency patch. It exposed a boundary: a component could retain formal evaluation credentials while new cryptographic evidence made keys produced through one library unsafe for continued operational reliance. Estonia…
CASE FILE
How Consensus Advice Held .AMAZON for Five Years
In the .AMAZON dispute, governments did not own the root-zone switch and an independent review panel did not acquire it. The decisive power moved through presumptions, reasons, application status, contract terms and finally delegation—showing how consensus can stop a namespace…
CASE FILE
Why Google Could Not Keep .SEARCH Closed
Google’s registry subsidiary applied to reserve a generic namespace for its own corporate group at a time when ICANN’s published rulebook did not expressly forbid that model. The application exposed a policy omission, and the decisive response came not from public comment…
NANOG
A Charitable Recipient Is Not a Working Successor
NANOG’s legal texts do serious, necessary work: they put liabilities before asset disposition and constrain the purposes for which what remains may be used. Their silence about registrar control, archive exports, protected reports, contractual rights and access revocation is not…
NANOG
From $918,545 to Six Weeks: Reading NANOG’s Reserve Boundary
NANOG’s 2024 audit placed the same exact amount under two different labels: Board-designated net assets and approximate maximum exposure on future meeting commitments. Later records made the control system more explicit, culminating in a December 2025 policy that separates…
NANOG
Two to Five Reports: Reading NANOG’s Confidential Accountability Record
NANOG’s public materials do more than promise a welcoming environment: they map covered spaces, confidential routes for help, an informal Ombuds function and separate powers over remedies and membership status. Their most concrete number—two to five reported incidents at each…
NANOG
Built for Three Days: What NANOG’s Meeting-Network Notices Can Prove
Before the first session, a hotel ballroom briefly becomes a network site; after the last, the build vanishes. NANOG’s attendee notices preserve a valuable trace of that temporary service—its profiles, support routes, venue limits and credited contributors—but they do not turn an…