.gemma
Is .gemma a real TLD? Who’s applying to run it?
.gemma is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Google.
A string tied to one company's AI model name; useful mostly to that brand, with little room for outside buyers.
the applicant's own AI-model ecosystem (official model pages, developer and community redirects); outside that, at most people named Gemma seeking a vanity address if registration is ever opened
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 megacorp putting one of its own product platforms' names in the root as a closed brand namespace for official product pages and a developer ecosystem, where the string is an ordinary word the company has annexed rather than its corporate name.
Also an everyday noun claimed as the name of a single company's software product, bet on the product brand being strong enough to carry a namespace on its own — with the same exposure that outsiders have a legitimate prior claim to the plain word.
The same shape from a different parent: a common word repurposed as a developer-facing platform brand whose namespace only works if the product's name, not the company's, is what buyers recognize.
What a .gemma domain is
.gemma is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. One application for it is on ICANN’s Reveal Day list.
Is the .gemma domain extension real yet?
.gemma 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 .gemma domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .gemma name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .gemma was .android, delegated on 12 November 2014.
Is .gemma a real TLD?
Not yet. .gemma is not in the DNS root, so nothing resolves under it. It’s here because .gemma is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Google · first recordedICANN
“CRRI2564-T14283 · Charleston Road Registry Inc. · primary”ICANN
- Band chosen: 10-29 (vanity/narrow). The sole applicant on the record is Charleston Road Registry Inc., which from general knowledge is Google's registry arm, and the string matches the name of a Google open-weight AI model family (my own knowledge, not on the record); the record carries no category tag and no stated registration policy. By analogy with other single-applicant, company-name-aligned strings run by the same applicant in the prior round (e.g. .google, .youtube), the likely outcome is a brand-controlled namespace used for a handful of official redirects and developer destinations rather than a public registration market, so there is no meaningful aftermarket and no third-party primary-identity use. It is not in the 30-49 band because no volume or price-driven registration dynamic is plausible under brand control. It is not in the 1-9 band because the string does have a real identity: an active AI developer community around the model, plus 'Gemma' as a common given name, which could support narrow vanity or community demand if the operator ever opened registration. Main market uncertainty: whether the operator ever offers names to third parties (open developer/community namespace vs. fully closed brand use); an open AI-developer namespace would be a different, higher-scoring product.