.bud
Is .bud a real TLD? Who’s applying to run it?
Nobody has applied for .bud in its own right, as of 7 October 2026. XYZ named .bud as the replacement string of its .neo application.
A cheap, catchy address for cannabis shops and growers, but legal limits and a famous beer nickname keep it from becoming a serious home.
cannabis dispensaries, growers and accessory brands wanting a short on-theme address, plus casual "buddy"-style vanity and community sites
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: an open generic product-category word for a regulated consumption vertical, sold by a registry to a fragmented pool of small producers and retailers who must be marketed to rather than arriving on their own.
Same vice-vertical open-generic bet but one notch narrower — it wagers on a single product word inside the category rather than the category itself, which is the structural risk .bud carries as slang for one plant product.
Also a consumption-category generic aimed at growers, sellers and enthusiasts with regulated marketing, though its buyers are an older, established trade more willing to put primary identity on a name than .bud's newer, compliance-bound operators.
What a .bud domain is
.bud 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 .bud in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .bud domain extension real yet?
.bud 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 .bud domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .bud name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .bud was .beer, delegated on 15 May 2014.
Is .bud a real TLD?
Not yet. .bud is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .bud as part of an application for another string. Every entry on this page links to its source.
- XYZ · first recordedICANN
- Band chosen: 30-49, usable but limited, at its low end. The string reads two ways: cannabis slang ("bud") and the friendly "buddy" sense, with a third, well-known association to a beer brand nickname that makes it trademark-sensitive. The cannabis retail and cultivation vertical does generate steady naming demand, and the applicant on the record, XYZ.COM LLC, filed .bud as a replacement string for its primary .neo application; by analogy with other portfolio-registry strings, distribution tends to produce volume on price promotions rather than a vertical standard, flagged as analogy. Why not 50-69: cannabis businesses are fragmented by jurisdiction, constrained in advertising and payments, and have no established alternative to .com-style identities, so a .bud primary identity would still need explaining and the beer association discourages some brand owners; the aftermarket for a slang-vertical string is thin by analogy with other single-vertical slang TLDs. Why not 10-29: unlike a pure joke string, there is a real industry with recurring new entrants and a plausible short-name appeal, so registrations should occur at volume on price with some genuine primary use among small dispensaries and growers. Specific registration counts, pricing and comparable-TLD outcomes are unknown. Main market uncertainty: whether cannabis operators adopt .bud as a primary identity at all, versus registering it defensively or for a lander, given regional legality and the competing beer-brand reading.