.dine
Is .dine a real TLD? Who’s applying to run it?
.dine is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Oinkadot.
Who is applying, and what they run today
Oinkadot filed 25 applications across the round.
Will names sell?
A pleasant web address for restaurants and food projects, but most eateries will likely stick with .com and social or delivery platforms.
Last round the AI scored the 2012 strings blind to their fate. Strings it scored 60 or more hold a median 27,168 names today; those under 30, a median of 30. .dine’s closest 2012 strings hold .eat 3, .restaurant 9K and .cafe 25K.
The nearest 2012 strings, and how many names each holds today
The closest 2012 string, .eat, held 3 names, June 2026. .restaurant held 8,890; .cafe held 25,445. Chosen by AI from every string in the 2012 round, without being told what happened to any of them.
Same bet exactly: a short, unowned English verb for the act of dining, sold as a memorable open-registry identity to restaurants and food brands, which only works if operators will move their primary brand off a .com onto an activity word.
Same buyer and same first-party-identity job, just stated as the category noun instead of the activity verb — the bet is that eating establishments will self-identify under a generic dining string rather than a corporate or geographic one.
Also a generic, unowned dining-venue word an operator would put its own name in front of, but it names a narrower venue type rather than the broad consumer activity, so it addresses a slice of the same buyer pool instead of the whole category.
restaurants, cafes, food halls, reservation and food-discovery apps, dining guides, and food bloggers who want a short verb-style address; secondarily local hospitality marketers building campaign or city-dining microsites.
What a .dine domain is
.dine is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Commerce category. One application for it is on ICANN’s Reveal Day list.
Is the .dine domain extension real yet?
.dine 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 .dine domain?
You can’t yet. A .dine name can only be registered once the string is delegated (added to the DNS root) and its registry opens. Last round's closest parallel to .dine was .eat, delegated on 30 August 2014.
Is .dine a real TLD?
Not yet. .dine is not in the DNS root, so nothing resolves under it. It’s here because .dine is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Oinkadot · now confirmedICANN
- Oinkadot · first recordedDomain Name Wire (Andrew Allemann)
“A new partnership has applied for 25 top level domain names in this year's ICANN TLD expansion round.”Domain Name Wire (Andrew Allemann)
- Band chosen: 30-49, usable but limited. The string is a clean, universally understood English verb with an obvious vertical (eating out), which puts it above the 10-29 vanity band: real businesses could plausibly register names like a city-dining guide or a booking widget domain, and left-of-dot pairings read naturally. It does not reach the 50-69 strong-niche band because, by analogy with existing food-vertical TLDs (.restaurant, .menu, .cafe, .bar, .kitchen), restaurant-sector strings have historically seen thin primary-identity adoption; exact registration figures are unknown, but the qualitative pattern (analogy, flagged as such) is that restaurants are local small businesses whose digital identity increasingly lives on aggregators, delivery apps, and social profiles rather than owned domains, and when they do buy a domain they default to .com or a ccTLD. The aftermarket for verb-style food TLDs is, by the same analogy, expected to be shallow, with few resales that would signal brand strength. Within the band it sits mid-low rather than high because .dine competes with several incumbent food TLDs for the same thin demand, diluting any category-standard claim. The applicant context is a modest positive for adoption likelihood: the verified facts state the applicant, Oinkadot, is a partnership between the CEOs of two consumer registrars (Porkbun and Dynadot), operating as its own venture, and applied for 25 strings in the ICANN 2026 round paying $5.675 million in fees per Domain Name Wire (2026-08-15); registrar-adjacent principals suggest credible retail distribution channels, which supports volume registrations at the low end of the band. Main market uncertainty: whether independent restaurants will, over the next 5 years, shift meaningful identity spend from platforms back to owned domains at all; if that channel shift happens, a short dining verb could outperform this score, and if it does not, demand stays promotional and disposable.