.bun
Is .bun a real TLD? Who’s applying to run it?
Nobody has applied for .bun in its own right, as of 7 October 2026. Oinkadot named .bun as the backup string of its .bug application.
A cute short word with bakery, rabbit and JavaScript-runtime flavours, but few projects would make it their main address.
bakeries, baked-goods and street-food brands, rabbit-owner and pet communities, and developers in the Bun JavaScript-runtime ecosystem wanting a playful domain hack
Nobody has applied for .bun in its own right.
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 prepared-food item, not a category, sold on the premise that an entire trade of independent shops will hang its primary identity on the one thing it makes.
Same product-noun-as-trade-identity bet with the same independent-shop buyer pool, but it sits behind a global roaster and cafe culture with far more businesses able to claim it than the target's thin trade.
Same narrow single-consumable bet whose whole demand case rests on one small maker-and-seller trade adopting it, with no general-interest buyer underneath if that trade stays on legacy names.
What a .bun domain is
.bun is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Culture category. Nobody has applied for .bun in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .bun domain extension real yet?
.bun 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 .bun domain?
You can’t yet. A .bun 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 .bun was .pizza, delegated on 27 August 2014.
Is .bun a real TLD?
Not yet. .bun is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .bun as part of an application for another string. Every entry on this page links to its source.
- Oinkadot · first recordedICANN
“OI2692T-T46092 · Oinkadot Inc · replacement string of .bug”ICANN
- Band chosen: 10-29 (vanity/joke/narrow). The string is a short, friendly dictionary word with three loosely connected meanings: a bread roll (bakery and street-food commerce), a rabbit nickname and hairstyle (pet and lifestyle culture), and the Bun JavaScript runtime (developer tooling), which offers a domain-hack angle for projects in that ecosystem. On the record there is a single application, by Oinkadot Inc, recorded as a replacement string whose primary application's string is .bug; no category tag and zero contention are recorded, which suggests limited competitive interest in the string itself (inference from the record, not a judgment of the applicant). By analogy with food and lifestyle word TLDs such as .pizza, .cafe and .bar, demand for a string like this has tended to be modest, novelty-led and price-sensitive rather than a primary identity for serious businesses; a bakery is more likely to keep its .com and use a .bun address as a vanity redirect. Not in the 30-49 band because there is no evident category where registrations would happen at volume or where the TLD carries a brand signal a buyer would pay for; not in the 1-9 band because real, if shallow, demand plausibly exists from bakeries, pet communities and the Bun developer community, and the word is memorable enough to attract some aftermarket interest for one-word hacks. Main market uncertainty: whether the Bun JavaScript-runtime community treats .bun as a natural namespace for its packages and projects (which would pull it toward a small but genuine tech niche) or whether the string remains a food/pet vanity word with event-driven registrations only. Actual registration volumes, pricing and any registry positioning are unknown.