Content Type
Analysis
Within the Content Type facet, Analysis intelligence gathers BTW.MEDIA articles that share the same editorial format, helping readers compare briefings, profiles, risk notes, market analysis, and event coverage without mixing different kinds of evidence. The page explains how this content type frames internet infrastructure events, company movements, governance decisions, operational signals, and public evidence across the site. Readers can compare which actors or infrastructure systems appear most often, how source quality changes interpretation, and whether the material is a durable profile, a time-sensitive event, a strategic market signal, or a governance development. The result is a useful search page for operators, investors, customers, analysts, and policy stakeholders who need to understand the consequence, timing, and evidence behind similar article formats.
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
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
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
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.…