Topic
DNS Delegation Power
Within the Topic facet, DNS Delegation Power 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.
Global Institutional
The 2015 Root DNS Flood Made Cross-Operator Telemetry an Accountability Test
Two concentrated query floods exposed the difference between root-system continuity and localized saturation, making shared, layer-specific telemetry the basis for judging operator preparedness and response.
Europe and Middle East Institutional
Spamhaus's 2013 DDoS Made Open DNS Recursion a Network Accountability Test
The March 2013 campaign showed how exposed recursive DNS, source-address spoofing and shared interconnection paths could turn individually small configuration failures into a large external cost. Accountability depends on proving which operator controlled each executable step and…
North America Cloud Services
Microsoft's 2001 DNS Outage Made Shared Router Failure Domains an Accountability Test
Microsoft's January 2001 outage demonstrated a basic but still consequential property of network infrastructure: correct DNS records and several authoritative server processes do not create a resilient naming service when every reachable path to those servers depends on the same…
CASE FILE
After the Failed CPE: How DotMusic Reached the .MUSIC Root
A failed community-priority score did not end DotMusic Limited’s application, and a later delegation did not erase that failure. The route from 10 points in 2016 to a live top-level domain in 2021 ran through separate institutions, separate legal instruments and separate…
CASE FILE
Who Could Challenge EBU’s .RADIO—and Who Could Enforce Its Rules
EBU’s community-priority victory did not itself award an operating right, and the losing applicants’ access to ICANN accountability procedures did not entitle them to a fresh evaluation. The history of .RADIO is instead a sequence of distinct institutional gates: an outsourced…
CASE FILE
The .SHOP Clock: Bidder Exit, a $41.5 Million Price and Control of ICANN’s Proceeds
The price attached to .SHOP was produced by a public rulebook and a largely private sequence of bidder instructions. That distinction matters. Nine applications were listed in the contention set, but deposits were submitted for only seven, creating seven eligible bidders in…
CASE FILE
Who Decides Who Is a CPA Online? AICPA's Failed Community Bid, the Contract Without Specification 12, and the .CPA Appeal Chain
A failed community-priority application, a later non-sponsored registry contract and a registry-specific eligibility appeal now sit in the same institutional history. Reading them as one continuous grant of authority obscures the central governance question: which instrument lets…
CASE FILE
The Domain ICANN Did Not Order: .PHARMACY’s 2018 Contract Cure
A Public Interest Commitment Dispute Resolution Procedure standing panel found that the National Association of Boards of Pharmacy had not transparently applied its published eligibility rules to one rejected applicant. ICANN then issued a breach notice and later recorded the…
CASE FILE
Why Booking.com’s .HOTELS Contended with .HOTEIS but Not .HOTEL
Two decision processes within ICANN’s new-gTLD programme could compare similar-looking top-level-domain strings and produce opposite-looking outcomes because they were not answering the same procedural question. Booking.com’s route to .HOTELS shows how a visual screen…
CASE FILE
When Territorial Coexistence Met a Single Root: Merck KGaA, .MERCK and the Limits of ICANN Review
For decades, private agreements divided use of the Merck name by territory. ICANN’s root could not. The .MERCK record shows how contractual history could enter objections and accountability proceedings without giving any one forum power to partition a globally unique label, award…
CASE FILE
Verified, Bundled, Released: How .NGO/.ONG Turned NGO Eligibility into Registry Enforcement
Behind .NGO and .ONG’s verification promise was a contractual machine: a name could be created before documentary review finished; linked commands once moved matching labels across two top-level domains; and different failures could lead to lock, hold, termination, deletion or…
CASE FILE
When Wine-Origin Claims Reached the Root: .WINE, .VIN and the Contract Path to Identity Digital
The argument over .WINE and .VIN did not ask ICANN to decide who could lawfully use names such as Champagne, Rioja or Bordeaux. It asked whether a global naming contract could carry protections for wine-origin claims before international and national law had produced a single…
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
When a Registry Policy Became Browser Code: The .APP Contract, Delegation and HSTS Preload Chain
.APP did not become an HTTPS-enforced namespace through one decision by one institution. Its path ran through a governmental warning, an amended application, evaluation, a twelve-party auction, an ICANN contract, a root-zone change, a registry-to-registrar notice rule and…
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
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…