.餐廳
Is .餐廳 a real TLD? Who’s applying to run it?
Nobody has applied for .餐廳 in its own right, as of 8 October 2026. Internet DotTrademark Organisation Limited named .餐廳 as an IDN variant label of its .餐厅 application.
A traditional-Chinese "restaurant" ending: readable to diners in Taiwan and Hong Kong, but few eateries would make it their main address.
restaurants, food-delivery and dining-guide businesses serving traditional-Chinese-script markets (Taiwan, Hong Kong, Macau, overseas Chinese communities), plus brand-protection registrants of the simplified 餐厅 form
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 exactly, only in the other script: a generic restaurant-vertical noun whose buyers are eateries putting their primary identity on a Chinese-language category word, so it must win trust from the same restaurant operators and diners.
The identical bet in Latin script: a bare profession/category generic that only works if independent restaurants choose a descriptive vertical namespace over .com, with no brand or community to anchor demand.
Also a plain traditional-script Chinese category noun sold to an entire commercial vertical, so it rides the same wager that traditional-character IDN generics get typed and trusted, differing only in which trade it serves.
What a .餐廳 domain is
.餐廳 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 .餐廳 in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .餐廳 domain extension real yet?
.餐廳 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 .餐廳 domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .餐廳 name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .餐廳 was .xn--imr513n, delegated on 30 May 2015.
Is .餐廳 a real TLD?
Not yet. .餐廳 is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .餐廳 as part of an application for another string. Every entry on this page links to its source.
- Band chosen: 10-29 (vanity/narrow). The string is the traditional-script form of "restaurant" and, per the record, is filed as a variant of the simplified 餐厅 application, so in market it would most likely be sold bundled with or mirrored to the simplified form rather than as an independent namespace. Its natural buyer base is restaurants in traditional-script regions, a sector that in practice anchors its identity on social platforms, delivery apps, map listings and conventional ASCII domains rather than on a descriptive-word ending. By analogy (flagged as analogy), earlier Chinese-script generic TLDs such as .公司 and .网络 saw registrations driven by promotional pricing and defensive holdings in mainland China, with little sign of sustained primary-identity use or a meaningful aftermarket; the traditional-script restaurant category is narrower still. It is not in the 30-49 band because volume-on-price registration is unlikely to materialize for a single-sector traditional-script string whose primary form is the simplified variant, and it is not in the 1-9 band because the word is universally understood by its target readers, a real sector exists, and some dining brands or food-delivery marketers could plausibly use it for memorable campaign addresses over the next 5 years. Main market uncertainty: whether traditional-script IDN display in browsers, email and app deep links has become reliable enough in Taiwan and Hong Kong for a restaurant to risk printing such an address on menus and signage. Registration counts, pricing and launch dates for this string are unknown.