.applebees
Is .applebees a real TLD? Who’s applying to run it?
.applebees is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Dine Brands Global, Inc..
A private brand extension for one restaurant chain: useful for its own campaign links, but nothing anyone else can buy or resell.
a single corporate registrant (the restaurant brand and its marketing and franchise teams), not the public; no third-party buyer group exists
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 exactly: a mass-market American franchised restaurant chain putting its corporate brand on a dot-brand it alone controls, with the value hinging on marketing campaigns and franchisee/location subdomains rather than on any open registration demand.
Also a restaurant-group trademark claiming its own name as a closed brand TLD, but the bet rests on a small luxury hospitality portfolio rather than on thousands of mid-market franchised units, so the scale and the audience differ.
Same structural bet of a household-name American consumer chain owning its brand string to organize per-store/local pages and promotions, differing only in that the chain sells groceries rather than meals.
What a .applebees domain is
.applebees 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 .applebees domain extension real yet?
.applebees 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 .applebees domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .applebees name can only be registered after that, once the string is delegated and its registry opens.
Is .applebees a real TLD?
Not yet. .applebees is not in the DNS root, so nothing resolves under it. It’s here because .applebees is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Dine Brands Global, Inc. · first recordedICANN
“DIN2676T-T15162 · Dine Brands Global, Inc. · primary”ICANN
- Band chosen: 10-29 (vanity/narrow). The verified record shows one confirmed application by Dine Brands Global, Inc. with no category tag and no contention, which is consistent with a closed .brand TLD where the operator is the only registrant. There is no open market, so end-use utility accrues solely to the brand: short promotional addresses (menu, order, rewards-style names), franchise or location routing, and tighter control over phishing lookalikes. Resale and aftermarket value are effectively nil because names are not sold to third parties. It is not in the 1-9 band because a real, serious organisation can plausibly put the string to primary or secondary identity use over the next 5 years, and brand TLDs from the earlier expansion round that stayed active did find campaign and redirect use (analogy). It is not in the 30-49 band because there are no volume or price-driven registrations at all and no brand signal for anyone other than the registrant itself. Analogy flag: in the prior round, brand TLDs in consumer dining and retail categories tended to be used lightly or retired rather than becoming the brand's primary web identity; a casual-dining chain with heavy franchise and third-party-delivery traffic is in that pattern. Main market uncertainty: whether the registrant commits to migrating primary identity and consumer-facing links to the new string, versus holding it defensively with occasional campaign redirects, which decides whether the TLD sits at the top or bottom of this band.