What is .chrome?
Brand TLDs operate under Specification 13 of ICANN's registry agreement. It lets a trademark owner keep every second-level name for itself, so you won't find .chrome names for sale at any registrar.
ICANN's records put the delegation of .chrome on September 15, 2014. Like most of the newer endings, it was applied for in the 2012 New gTLD Program round and its registry agreement was signed on July 24, 2014.
Charleston Road Registry Inc. operates a large portfolio of 46 TLDs, including .ads, .android, .app, .boo and .cal.
Under the hood, the root zone points to 5 name servers for .chrome, every one of them reachable over IPv6. The delegation is DNSSEC-signed, so resolvers can verify that answers for .chrome haven't been tampered with on the way. Registration data is published over RDAP.
Same registry, other endings
45 other TLDs share this operator.
.chrome FAQ
What country is .chrome?
None. .chrome is a generic top-level domain, so it isn't tied to any country.
Who owns the .chrome domain extension?
Charleston Road Registry Inc. operates .chrome as its registry, under a registry agreement with ICANN.
When was .chrome created?
.chrome was delegated to the DNS root zone on September 15, 2014.
Is .chrome a valid domain?
Yes. .chrome is an active top-level domain in the DNS root zone, delegated in 2014, so .chrome addresses work in every browser.
Can I buy a .chrome domain?
No. .chrome is a brand TLD under ICANN Specification 13, so names are reserved for Charleston Road Registry Inc.
Is .chrome DNSSEC-signed?
Yes, the root zone holds a DS record for .chrome.
Sources
Data from IANA root zone version 2026102000. Last changed April 11, 2025. Spotted something wrong? Tell us.
