.drink
Is .drink a real TLD? Who’s applying to run it?
Nobody has applied for .drink in its own right, as of 7 October 2026. Intercap named .drink as the replacement string of its .sell application.
A readable beverage-category name that bars and drinks brands could use, but most will still default to .com and resale value stays thin.
beverage brands, bars, cocktail and recipe publishers, and drinks startups wanting a short descriptive address for a product line or venue
No applications recorded for this TLD yet.
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 at the same altitude: an unownable mass-noun consumable category where the registry wagers that an entire consumption industry plus everyday consumers will put primary identity on a word they already use generically.
A generic beverage category noun sold to the producers, retailers and venues of that trade, differing from the target only by being one step narrower over the same buyers.
Also a generic beverage noun aimed at the drinks trade, but it rides an established producer/appellation industry with its own naming habits, so the bet leans on that trade rather than on a broad everyday consumption word.
What a .drink domain is
.drink is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Commerce. Nobody has applied for .drink in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .drink domain extension real yet?
.drink is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. Nobody has applied for it on the public record; the ICANN 2026 new gTLD round is the process that would decide whether it becomes one.
When can you buy a .drink domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .drink name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .drink was .food, delegated on 10 November 2016.
Is .drink a real TLD?
Not yet. .drink is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .drink as part of an application for another string. Every entry on this page links to its source.
- Intercap · first recordedICANN
“IRI2679T-T88066 · Intercap Registry Inc. · replacement string of .sell”ICANN
“EDI2665T-T28371 · Endpoint Domains, Inc. · primary IRI2679T-T96997 · Intercap Registry Inc. · replacement string of .wiz · Deactivated NA2626T-T63059 · ShortDot (Ireland) Limited · replacement string of .ask · Deactivated XL2625T-T48604 · XYZ.COM LLC · replacement string of .con · Deactivated”ICANN
- Band chosen: 30-49, usable but limited. .drink is a plain English generic covering the whole beverage category (soft drinks, water, alcohol, coffee, cocktails), so it reads naturally on the right of a brand or venue name and has genuine end-use utility for drinks launches and bars. By analogy (flagged as analogy), the 2012-round beverage and hospitality strings such as .beer, .wine, .coffee, .bar and .pub reached modest registration bases, were used mostly for secondary or campaign sites, and developed little aftermarket; I would expect .drink to behave like a broader version of that group rather than break out of it. It is not in the 50-69 band because I see no evidence of sustained primary-identity adoption in beverage retail, where .com and brand-owned domains dominate and any .drink address would need explaining to consumers and investors. It is not in the 10-29 band because the string is a real consumer category with everyday meaning, not a joke or event word, and a venue or product line could credibly use it as its main address. Applicant fact, stated neutrally from the record: one application is recorded, from Intercap Registry Inc., with status replacement and a primary application string of .sell; contention count on the record is 0. This single-applicant, replacement-string context says nothing about the string's merit but suggests adoption will depend on how actively the operator markets it. Registration volume, retail pricing and any premium-name program are unknown. Main market uncertainty: whether beverage brands and bars treat .drink as a memorable primary identity (lifting it toward the niche band) or only as a defensive or campaign registration, which would keep it near the bottom of this band.