.gke
Is .gke a real TLD? Who’s applying to run it?
.gke is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Google.
A three-letter string tied to one cloud product; useful mainly as that product's own namespace, with no real third-party market.
the applicant's own product and developer-platform teams, for product-scoped hostnames; not a namespace a third party would choose as a primary identity
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.
Same bet exactly: a short, opaque acronym for one company's cloud/developer platform, applied for by the parent so the product line's own engineering and docs surfaces sit on a string that means nothing to anyone outside the customer base.
Also a single company's cloud-platform product claiming its own namespace for developer-facing identity, but the string is a real word with standalone appeal rather than an insider abbreviation, so it carries brand weight .gke has to earn.
A consonant-skeleton abbreviation of one company's platform product used as corporate shorthand — the same bet that a technical audience already recognizes the contraction, though it points at an acquired ad platform rather than a self-built developer service.
What a .gke domain is
.gke 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 .gke domain extension real yet?
.gke 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 .gke domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .gke name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .gke was .aws, delegated on 25 March 2016.
Is .gke a real TLD?
Not yet. .gke is not in the DNS root, so nothing resolves under it. It’s here because .gke is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Google · first recordedICANN
“CRRI2564-T61797 · Charleston Road Registry Inc. · primary”ICANN
- Band chosen: 10-29 (vanity/narrow). The record shows a single confirmed application from Charleston Road Registry Inc. with no category tag and no contention, which is the profile of a single-registrant brand-style string rather than a generic namespace. To a technical audience the string reads as a cloud-product acronym (my own knowledge, qualitative), so even assuming general availability, demand from unrelated registrants is unknown and by analogy to other product-acronym brand TLDs it would be thin, event-free, and without an aftermarket. It is not in the 1-9 band because the string has a recognized meaning to a defined developer audience and plausible first-party utility as a product namespace (docs, consoles, cluster-scoped hostnames) — an analogy drawn from how other operators have used their brand TLDs for product surfaces. It is not in the 30-49 band because there is no evidence of volume registrations, price-driven demand, or any brand signal that transfers to a third party; a serious unaffiliated project would not adopt it as primary identity. Main market uncertainty: whether the operator actually puts product-facing hostnames on the string (which would give it real, if captive, utility) versus leaving it defensive and idle, which has been the more common outcome for brand TLDs by analogy.