.sushi
Is .sushi a real TLD? Who’s applying to run it?
.sushi is not contested. One application for it is on ICANN’s Reveal Day list, as of 18 November 2026. It is XYZ Registry.
Who is applying, and what they run today
XYZ Registry filed 139 applications across the round.
Will names sell?
A fun, narrow food-word ending that a few sushi restaurants and Japanese-food brands may use, but rarely as a serious main address.
Last round the AI scored the 2012 strings blind to their fate. Strings it scored 60 or more hold a median 27,168 names today; those under 30, a median of 30. .sushi’s closest 2012 strings hold .pizza 11K, .coffee 28K and .vodka 2K.
The nearest 2012 strings, and how many names each holds today
The closest 2012 string, .pizza, held 10,742 names, June 2026. .coffee held 28,464; .vodka held 1,803. Chosen by AI from every string in the 2012 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.
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
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, in our Commerce category. One application for it is on ICANN’s Reveal Day list.
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. 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 .sushi domain?
You can’t yet. A .sushi name can only be registered once the string is delegated (added to the DNS root) 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 .sushi is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- 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.