.yum
Is .yum a real TLD? Who’s applying to run it?
Nobody has applied for .yum in its own right, as of 7 October 2026. Intercap named .yum as the replacement string of its .pal application.
A playful food-word domain: fun for recipe blogs and snack promos, but few serious businesses will make it their main address.
food bloggers, recipe creators, restaurants, snack and delivery brands wanting a short, playful promotional address rather than a primary business identity
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: a one-syllable everyday food word rather than a category noun, sold to the whole food/dining/recipe world as a friendly consumer-facing identity, and it only works if the public reads the word as a universal gesture about eating instead of one company's slogan.
Same buyer and same job — primary identity for anyone in food — but it is the plain generic category noun, the sober version of the bet, where .yum stakes the same ground on appetite and tone instead of on the dictionary category.
Closest match on what the string IS — a short exclamation whose whole value is affect rather than denotation, bet on registrants wanting a reaction instead of a classification — but it carries no sector anchor, so its buyer pool is everyone rather than food specifically.
What a .yum domain is
.yum 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 .yum in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .yum domain extension real yet?
.yum 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 .yum domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .yum name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .yum was .eat, delegated on 30 August 2014.
Is .yum a real TLD?
Not yet. .yum is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .yum as part of an application for another string. Every entry on this page links to its source.
- Intercap · first recordedICANN
“IRI2679T-T18569 · Intercap Registry Inc. · replacement string of .pal”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: 10-29 (vanity/joke/narrow), upper end. The string is an exclamation, not a category noun, so it reads as a slogan suffix (pizza.yum, mom.yum) rather than a place a business lives. By analogy (flagged as analogy), food-sector gTLDs such as .food, .restaurant, .pizza, .recipes and .cafe have seen modest, price-sensitive registration with thin aftermarkets, and even those are category nouns; exclamation strings such as .wow, .lol, .fun and .cool have, by analogy, drawn promotional and hobby registrations that rarely become a serious primary identity. That keeps .yum out of the 30-49 band, where volume registration on price would need to be sustained and the brand signal at least usable for a business card; here the signal is playful and the buyer is overwhelmingly a blogger or a campaign. It is above the 1-9 band because food is one of the largest hobby and small-business categories online and a three-letter, pronounceable, memorable suffix will find real if shallow demand for recipe sites, menus and promos. The verified record shows a single standard application by Intercap Registry Inc. as a replacement string for .pal, with no contention recorded; this is stated neutrally and bears only on adoption pacing, not on the string's market. A further qualitative caution (not from the facts block, inference only): the word is also strongly associated with an existing food-industry trade name, which could create rights friction or, conversely, a single anchor adopter, and I treat this as unknown. Main market uncertainty: whether registrars will distribute .yum as a cheap mass vanity string (driving volume but no credibility) or as a restricted, premium-priced food-brand namespace (driving credibility but very low volume); either path keeps it in the vanity band, but the shape of demand differs.