.chromium
Is .chromium a real TLD? Who’s applying to run it?
.chromium is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Google.
A brand TLD for the Chromium browser project; useful only to its operator, with no open market or resale value.
the applicant and the Chromium open-source project it is associated with, for project, documentation, and build infrastructure addresses; not for third-party registrants
The 2012 applications making the most similar bet. Chosen by AI from every string in that round, without being told what happened to any of them.
Identical bet: a single company's browser-platform name taken as its own namespace, where the registry's whole value rests on that one owner's product brand being recognized and its own properties being the primary identity on it.
Same bet as .chromium read as the open-source project: a corporate-stewarded codebase that a wide third-party developer and OEM ecosystem builds on, so the string has to serve both the steward's identity and a community that does not work for the steward.
Also a platform/runtime name owned by one vendor but worn by an outside developer ecosystem, though it is a looser parallel because the word is a pre-existing common noun rather than a project-coined technical name.
What a .chromium domain is
.chromium is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Brand. One application for it is on ICANN’s Reveal Day list.
Is the .chromium domain extension real yet?
.chromium is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. It is a string applicants have put forward in the ICANN 2026 new gTLD round, the process that decides whether it becomes one.
When can you buy a .chromium domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .chromium name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .chromium was .chrome, delegated on 15 September 2014.
Is .chromium a real TLD?
Not yet. .chromium is not in the DNS root, so nothing resolves under it. It’s here because .chromium is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Google · first recordedICANN
“CRRI2564-T40931 · Charleston Road Registry Inc. · primary”ICANN
- Band: 10-29 (vanity/narrow). The verified facts record a single confirmed application from Charleston Road Registry Inc. with no category tag, and the string matches a well-known open-source browser project name, so this reads as a single-registrant brand TLD rather than an open namespace. Not the band above (30-49) because brand TLDs of this kind do not take registrations from the public at volume and have no aftermarket; the address value accrues to one operator. Not the band below (1-9) because there is a realistic, if narrow, end use: a technically credible project could plausibly consolidate documentation, source, bug-tracking, or release addresses under a short exact-match namespace, which is a genuine primary-identity use for that one party. By analogy (flagged as analogy), brand TLDs run by the same registry family have had mixed outcomes: some are used for live corporate or product addresses, while others remain largely defensive or dormant, and open-source project brand TLDs in general have seen little visible use. Main market uncertainty: whether the operator actually migrates primary project surfaces onto the TLD within five years or holds it defensively; the former would push toward the top of this band, the latter toward the bottom. No figures are asserted because none appear in the verified-facts block.