.sushi
Is .sushi a real TLD? Who’s applying to run it?
Nobody has applied for .sushi in its own right, as of 7 October 2026. XYZ named .sushi as the replacement string of its .jia application.
A fun, narrow food-word ending that a few sushi restaurants and Japanese-food brands may use, but rarely as a serious main address.
sushi restaurants, Japanese-food delivery and product brands, and food bloggers wanting a playful memorable address; a secondary trickle of crypto-adjacent projects using the word as a mascot
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.
Identical bet: a single prepared-dish noun that only works if the specialty eateries, delivery brands and recipe sites built around that one dish will move their primary identity onto the dish name itself.
Same shape of bet — one consumable's name sold to the specialist trade around it — but it reaches past the serving venue into growers, roasters and retailers, so its buyer pool is broader and less restaurant-shaped.
Also a narrow single-product generic whose registrants are the niche producers and sellers of that one item, but identity sits with brands and merchants rather than with the storefront that serves it.
What a .sushi domain is
.sushi 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 .sushi in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .sushi domain extension real yet?
.sushi 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 .sushi domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .sushi name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .sushi was .pizza, delegated on 27 August 2014.
Is .sushi a real TLD?
Not yet. .sushi is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .sushi as part of an application for another string. Every entry on this page links to its source.
- XYZ · first recordedICANN
- Band chosen: 10-29 (vanity/narrow). .sushi is a single-dish food word, which places it below the broader food-and-drink category endings (.pizza, .restaurant, .cafe, .bar, .coffee) that already exist and, by analogy, have settled into modest registration bases with weak aftermarkets and little primary-identity use; a dish-specific string is narrower still. It is not in the 30-49 band because there is no clear mechanism for volume registrations beyond promotional pricing and the brand signal is playful rather than credible for a business; it is not in the 1-9 band because sushi is a globally recognised word with a real worldwide restaurant and delivery segment, and the word's use as a mascot by some crypto projects adds a small second buyer group (inference from analogy, since no demand figures are in the verified facts). Applicant facts, stated neutrally: the only recorded application is from XYZ.COM LLC, as a replacement string for .jia, with zero contention on the record; a registry with retail-channel reach makes modest adoption more plausible but does not change the string's ceiling. Main market uncertainty: whether any dish- or cuisine-level TLD can earn repeat, renewed primary-identity use by restaurants, or whether such names stay as redirects and vanity registrations.