Charleston Road Registry Inc.

.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, finally, security logic shipped in browser software. Reconstructing those layers shows how private policy can become executable at scale—and why each remedy stops at the layer its decision-maker can actually change.

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, governmental advice or root-zone engineering alone, but from the Board committee that could delay a registry contract and define the terms on which the string would proceed.

Charleston Road Registry Inc. (CRR), doing business as Google Registry, is a wholly owned subsidiary of Google LLC. It is the domain name registry that Google uses to manage its top-level domains (TLDs).