.edible
Is .edible a real TLD? Who’s applying to run it?
.edible is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Edible Arrangements.
A food-word TLD with a single brand applicant; useful as a vanity address for edibles and snacks, but not a serious identity.
food and cannabis-edibles brands, snack and gifting companies wanting a playful vanity address, plus the applicant's own brand properties if it runs the TLD for itself
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: an open-registry adjective asserting a consumable property, sold to food makers and brands whose whole value depends on buyers trusting the claim the word makes about what is inside.
Also an edibility adjective that functions as a fitness-to-eat assertion, but its meaning rests on an external certifying authority rather than being a self-applied descriptor anyone can adopt.
A short consumption-side food word betting on the whole eating vertical as one open namespace, though it is a consumer verb inviting restaurants and media rather than a product attribute a maker puts on its label.
What a .edible domain is
.edible 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 .edible domain extension real yet?
.edible 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 .edible domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .edible name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .edible was .organic, delegated on 13 June 2014.
Is .edible a real TLD?
Not yet. .edible is not in the DNS root, so nothing resolves under it. It’s here because .edible is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Edible Arrangements · first recordedICANN
- Band chosen: 10-29 (vanity/narrow). The verified record shows one confirmed application from Edible Brands LLC with no category tag; the string is a common English adjective that reads as a brand name in that applicant's context and as a generic food or cannabis-edibles descriptor otherwise. It is not in the 30-49 band because, by analogy with other food-themed new gTLDs (.recipes, .kitchen, .cafe), open registration of a narrow food adjective has historically produced modest volume, weak brand signal and a thin aftermarket, and an adjective like 'edible' is harder to pair with a left-of-dot name than a noun like .cafe. It is not in the 1-9 band because the word has genuine semantic demand in food, gifting and the regulated cannabis-edibles segment, and a committed brand operator is a plausible primary user of its own namespace. Figures for comparable TLDs are unknown here; the above is reasoning by analogy. Main market uncertainty: whether the TLD is run as a closed brand space (then value is confined to the applicant's own properties and resale is effectively nil) or opened to general registration (then a small cannabis-edibles and snack-brand niche could form over the next 5 years, still vanity-tier).