.nest
Is .nest a real TLD? Who’s applying to run it?
.nest is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Google.
A closed brand TLD for Google's own use; no outside buyer can get a .nest address, so there is no market beyond the applicant.
the applicant's own product, device and service identities (a brand TLD), not third-party registrants; the word's generic appeal to home, family and finance brands is unreachable under a brand application
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 as .nest: a short, warm dwelling word offered as the connotation-driven alternative to the literal home category, counting on registrants who want "where you live" to feel personal rather than descriptive.
Also a small shelter noun sold on cozy/design connotation instead of category coverage, with the same diffuse buyer (home, interiors, hospitality, personal sites) putting its identity on a feeling rather than a keyword.
A plain one-syllable English noun for a dwelling space that is generic in form but owns no commercial category, so like .nest it has to earn registrations as a figure of speech rather than as the obvious term of art for an industry.
What a .nest domain is
.nest 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 .nest domain extension real yet?
.nest 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 .nest domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .nest name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .nest was .casa, delegated on 23 September 2014.
Is .nest a real TLD?
Not yet. .nest is not in the DNS root, so nothing resolves under it. It’s here because .nest is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Google · first recordedICANN
“CRRI2564-T59660 · Charleston Road Registry Inc. · primary”ICANN
- Band chosen: 10-29 (vanity/narrow), at its floor. The verified facts show a single confirmed application from Google (Charleston Road Registry Inc.) with ICANN application type: brand, so the TLD is expected to be operated for the applicant's own names, not sold to the public. Judged as it would stand in market, the only buyer is the brand owner, so end-use utility exists (device, service or redirect addresses under a short, memorable word tied to a known consumer product line) while resale and aftermarket value are effectively nil. It is not in the 30-49 band because a brand TLD produces no volume registrations and no third-party primary identities. It is not in the 1-9 band because, by analogy with earlier brand TLDs operated by large technology companies (flagged as analogy), such strings do see some real, if light, first-party use, and 'nest' is a strong dictionary word that would carry genuine generic demand if it were ever opened. Main market uncertainty: how actively the applicant will use .nest for live product identities versus holding it defensively, and whether the Nest brand remains a front-line consumer brand over the next 5 years; both are unknown from the record.