Booking.com B.V.

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, objections, accountability mechanisms, a Board direction, an auction, a registry contract and root-zone processing each controlled a different status switch.

Delegation, DNSSEC, RDAP and continuity records expose a dual-TLD control surface while leaving private architecture, longitudinal reliability and customer production outcomes subject to separate evidence.