.bbq
Is .bbq a real TLD? Who’s applying to run it?
.bbq is contested: 2 applications for it are on ICANN’s Reveal Day list, as of 7 October 2026. They are GoDaddy Registry and Phoenix Domain Partners. XYZ named .bbq as a backup string for its .motors application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup.
Fun and memorable for barbecue joints, sauces, and grill brands, but few will make it their primary web address over the next 5 years.
barbecue restaurants, pitmasters, sauce and grill-gear brands, competition BBQ teams, and food-culture hobby projects wanting a playful, semantic name
One of 13 strings Phoenix Domain Partners published as applied-and-paid in the ICANN 2026 round, reported by Domain Name Wire on 2026-08-17.
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .motors application, shown as deactivated: another applicant applied for the same string or named it as a backup
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: a single colloquial food noun narrow enough that a restaurant, pitmaster, or sauce brand will hang its whole identity on it, betting that a hyper-specific vertical beats a generic like .restaurant.
Same bet on a consumable that is simultaneously a commercial category and a hobbyist subculture, so the registry needs both producers/retailers and enthusiast-hobbyists to adopt it for the volume to work.
Same bet on a food-adjacent activity noun whose primary registrants are content and enthusiast sites rather than corporations, but it is a broad activity where .bbq is a narrow named cuisine, so the addressable pool is much wider.
What a .bbq domain is
.bbq is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Commerce. 2 applications for it are on ICANN’s Reveal Day list.
Is the .bbq domain extension real yet?
.bbq 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 .bbq domain?
You can’t yet. A .bbq 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 .bbq was .pizza, delegated on 27 August 2014.
Is .bbq a real TLD?
Not yet. .bbq is not in the DNS root, so nothing resolves under it. It’s here because .bbq is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- XYZ · first recordedICANN
- GoDaddy Registry · first recordedICANN
- Phoenix Domain Partners · now confirmedICANN
- Phoenix Domain Partners · first recordedDomain Name Wire
“MLG2688T-T77522 · 101130013 Saskatchewan Ltd. · primary · contention set 2026-21 NA2631T-T48096 · Registry Services, LLC · primary · contention set 2026-21 XL2625T-T77639 · XYZ.COM LLC · replacement string of .motors · Deactivated”ICANN
“MLG2688T-T77522 · 101130013 Saskatchewan Ltd. · primary · contention set 2026-21 NA2631T-T48096 · Registry Services, LLC · primary · contention set 2026-21”ICANN
“Phoenix Domain Partners published 13 strings for which it says it has applied and paid the application fees.”Domain Name Wire
- The string is instantly legible and maps to a real, passionate commercial-plus-hobby vertical, but by analogy to food-niche TLDs like .pizza, .bar, and .restaurant (flagged as analogy), such strings tend to see modest registration volume, price-driven spikes, and only scattered primary-identity use, since restaurants and food brands over the next 5 years still default to .com or local ccTLDs and treat niche endings as redirects or campaign names. BBQ is a narrower category than pizza or dining generally, which caps the ceiling further, though the culture around pitmasters and competition BBQ gives it more organic charm than a generic string. Comparable food TLD volumes are unknown, so this is qualitative. I place it in the 10-29 band: it is above 1-9 because a genuine, identifiable buyer group exists and some real businesses would plausibly register, but below 30-49 because sustained at-volume registration and any meaningful aftermarket are doubtful without heavy discounting, and the brand signal reads playful rather than credible. Main market uncertainty: whether food businesses' willingness to adopt semantic TLDs as primary identities grows at all in the next 5 years or stays flat.