.buzz domain: registry, ownership and registration rules

The organisation named in the IANA root zone record and in the ICANN Registry Agreement is DOTSTRATEGY CO., a US company based in Conway, Arkansas. It signed the original .buzz Registry Agreement with ICANN on 2 October 2013 and is still the contracted operator on paper.

There's a wrinkle, though. An October 2025 press release from ShortDot SA, a Luxembourg-based registry group, lists .buzz among the extensions it manages under its Registry Services Program, alongside .icu, .cyou, .bond, .sbs, .cfd and .qpon. Nothing in that release says whether this is a services arrangement running underneath DOTSTRATEGY CO.'s existing ICANN contract, or a genuine change of operator that ICANN's public records simply haven't caught up with. So take any firm claim about who actually runs .buzz with a pinch of salt.

On the technical side, GoDaddy Registry is the back-end provider named in the IANA record. Earlier reporting from 2015 has Neustar running the infrastructure during .buzz's first years. ICANN sits above all of it as the policy authority, the body DOTSTRATEGY CO. answers to.

In practical terms for .buzz: the registry (DOTSTRATEGY CO., possibly alongside ShortDot) holds the master database and writes the registry-level rules. A registrar, Gandi or GoDaddy for instance, is who you actually buy the name from and manage it through. You, the registrant, hold the registration itself and are bound by both the registry's terms and whatever contract your registrar has you sign.

.buzz has open eligibility. Anyone, anywhere, can register a name, whether that's an individual, a business or some other type of organisation. No residency requirement, no local-presence test, no need to show a trademark or any other legal claim to the string. This sits at the registry level, not something individual registrars have bolted on.

The one registry-level restriction on record is a block on names deemed patently offensive, put in place to keep the namespace broadly family-friendly, according to TLD-List's registry policy summary. Names between 2 and 63 characters are accepted, numbers and IDN characters are supported, and hyphens are allowed in the middle of a label.

Beyond that baseline, registrars are left to set their own practices. Some ask for identity and payment verification before a domain goes live, some bundle in privacy protection, DNSSEC or a free SSL certificate as part of the price, and premium or reserved names get priced individually by the registry. None of that touches who is allowed to register, it just shapes what a given registrar asks for or charges on top of rules that are, at root, pretty wide open.

.buzz transfers work the same way as any other gTLD under the ICANN Transfer Policy. The losing registrar issues an authorisation code, the gaining registrar submits it, and the registrant confirms the move before it completes. Standard registrar locks kick in after registration, a transfer, or a change of registrant contact. ICANN's GNSO did vote in March 2025 to strip the 60-day lock out of future transfer policy, according to Domain Incite, but nothing in the sources confirms whether that change has actually landed for .buzz yet.

.buzz is a non-sponsored gTLD, so it sits under ICANN's Expired Registration Recovery Policy, which mandates a 30-day Redemption Grace Period once a domain is deleted, as set out by ICANN. Beyond that baseline, the details shift from registrar to registrar. Gandi, for instance, gives a 45-day late-renewal window after expiry, charges $84.68 to restore a domain in its first year past that window, and holds it in pending-delete for five days after restoration, per Gandi. Registration and renewal terms run from one to ten years, according to TLD-List. There's no single restore fee set by the registry that applies everywhere, so what it actually costs to claw back a lapsed .buzz name comes down to who you registered it with in the first place.

Volkswagen's electric van sub-brand is the clearest public example, running at id.buzz, which the current registry operator cites as a live site under the extension. There's also a reserved gaming.buzz sitting in the same premium inventory, per ShortDot. Registrar copy points to a fairly predictable crowd beyond that: media outlets, marketing agencies, event organisers and influencers after a name that sounds current, per Network Solutions.

A few practical points before you go live. None of the sources reviewed document a registry-mandated HTTPS or HSTS requirement for .buzz, so TLS configuration comes down to your hosting choice rather than any registry rule. None of the sources we checked flags specific email deliverability or spam-filter problems tied to .buzz either, but with any newer gTLD it's still worth testing outbound mail against the major providers before you lean on a @yourname.buzz address for anything that matters. As a primary domain it suits content or campaign sites where the name itself is part of the pitch. For a formal business identity, it works better as a secondary redirect pointing at a more conventional domain. One naming tip specific to this string: don't pair it with words that already mean the same thing, "news" or "hype" for instance, since "buzz" already carries that meaning and the combination just reads as redundant.