.bistro
Is .bistro a real TLD? Who’s applying to run it?
Nobody has applied for .bistro in its own right, as of 7 October 2026. Phoenix Domain Partners named .bistro as the replacement string of its .jackpot application.
A charming name for small restaurants, but most eateries will stay on .com or social pages; narrow demand, thin resale value.
independent restaurants, cafes and wine bars wanting a short memorable web address, plus hospitality groups and food-delivery brands in French- and English-speaking markets
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: a narrow, format-specific word for a style of eating establishment, sold as primary identity to independent owner-operators rather than to a brand or a whole industry.
The parent category noun for the identical trade and buyer — an operator choosing between the two is choosing between the whole category and a connotation-bearing slice of it, which is the same wager on hospitality SMBs naming themselves by trade.
Also a narrow food-service format word that works only if small independent operators adopt it as their own identity, though it names a dish rather than a room, so a supplier/delivery layer rides along that .bistro has no equivalent of.
What a .bistro domain is
.bistro 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 .bistro in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .bistro domain extension real yet?
.bistro 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 .bistro domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .bistro name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .bistro was .cafe, delegated on 5 April 2015.
Is .bistro a real TLD?
Not yet. .bistro is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .bistro as part of an application for another string. Every entry on this page links to its source.
- Phoenix Domain Partners · first recordedICANN
“MLG2688T-T25734 · 101130013 Saskatchewan Ltd. · replacement string of .jackpot”ICANN
“MLG2688T-T61684 · 101130013 Saskatchewan Ltd. · replacement string of .beach · Deactivated XL2625T-T45963 · XYZ.COM LLC · replacement string of .mart · Deactivated”ICANN
“Phoenix Domain Partners published 13 strings for which it says it has applied and paid the application fees.”Domain Name Wire
- Band chosen: 10-29 (vanity/narrow). The string is a widely understood hospitality word that reads naturally across many languages, which gives it genuine end-use appeal for a single business type. It is not in the 30-49 band because, by analogy with the 2012-round hospitality strings (.restaurant, .cafe, .bar, .pizza, .kitchen), food-service TLDs have drawn modest registration volumes and little aftermarket: small restaurants overwhelmingly rely on a .com, a delivery-platform listing, or a social profile as their primary identity, and .bistro is narrower than .restaurant or .cafe (figures for those TLDs: unknown; this is reasoning by analogy). It is not in the 1-9 band because the word is real, positive and self-explanatory, so a steady trickle of primary-identity use by independent eateries and a few hospitality brands over the next 5 years is plausible. Applicant facts on the record: one application, by Phoenix Domain Partners (101130013 Saskatchewan Ltd.), recorded as a replacement string for .jackpot, with contention count 0 - this suggests a portfolio-style operation rather than a hospitality-industry sponsor, which modestly lowers the odds of category-led marketing driving adoption. Main market uncertainty: whether restaurant-discovery and delivery platforms, rather than owned websites, remain the dominant online identity for small eateries, which would cap primary-identity demand regardless of how well the string reads.