.biz domain names

What .biz is

.biz is a phonetic rendering of business, created explicitly as a business-oriented alternative to a saturating .com. It was one of the seven new gTLDs ICANN selected in late 2000, and its IANA registration date is 26 June 2001 - the same day as .info.

Its classification needs care. IANA's root database labels .biz a restricted generic top-level domain, while ICANN's registry agreement listing records the current agreement, executed 30 June 2019, as Base, Non-Sponsored. Both are correct: the IANA label reflects the nominal restrictions below, not a sponsored structure. .biz is a restricted generic gTLD in name and a functionally open one in practice.

The operator as of 2026 is Registry Services, LLC, trading as GoDaddy Registry, of Tempe, Arizona, with the IANA record last updated on 10 March 2026. NeuLevel - a joint venture between NeuStar and Melbourne IT - won the registry in ICANN's 2000 round; Neustar absorbed it; and GoDaddy acquired Neustar's registry business, announced 6 April 2020, covering more than 215 TLDs and roughly 12 million domains including .biz, .co, .in, .nyc and .us. Neither earlier name is correct in the present tense.

Who can register .biz

.biz is the only widely used legacy gTLD that still carries a written eligibility restriction, and the enforcement question is what separates a useful answer from a copied one.

Per ICANN's published .biz registration restrictions, a registration must be used or intended to be used primarily for bona fide business or commercial purposes. The restrictions expressly exclude registering a name solely to sell, trade or lease it for compensation; using one exclusively for personal, non-commercial purposes or solely to express non-commercial opinions; and bulk email, phishing and other abusive purposes. There is no geographic nexus and no legal-entity prerequisite.

Enforcement is where the restriction dissolves. ICANN's own documentation states that the registry operator will not review, monitor, or otherwise verify compliance: no check at registration, no documentation, no proactive audit. Enforcement is reactive and third-party-driven, through the Restrictions Dispute Resolution Policy (RDRP) for use-based allegations and the UDRP for trademark claims, and RDRP filings are rare. Treat it as a real contractual term with near-zero practical gatekeeping, and never describe .biz registrants as vetted.

What .biz costs to own

.biz has no price caps. It moved onto the standard base gTLD registry agreement in the 2019 legacy-TLD renewals, executed 30 June 2019, which removed the previous cap structure.

GoDaddy Registry raises prices in periodic portfolio rounds rather than one-off adjustments - a documented example being an increase across 26 top-level domains effective 1 April 2025 - and .biz has been named in registrar price-increase notices alongside extensions such as .club and .vip. No specific .biz percentage should be inferred from those rounds, but the direction of travel is clear enough to plan around. The base agreement supplies the two protections worth acting on: six months' notice of any increase, and the right to renew for up to ten years at the pre-increase price during that window.

GoDaddy Registry operates premium and tiered pricing across its portfolio generally; whether a particular .biz name is registry-designated as premium is best confirmed against live pricing. .biz is also a frequent deep-discount first-year extension at retail, so model the renewal rather than the offer - and note that restoring a lapsed name during the redemption grace period costs substantially more than a renewal.

Registration terms, renewals, and transfers

.biz uses standard gTLD terms: a minimum of one year and a maximum of ten, in whole-year increments, with expiry never more than ten years out. Renewals stack to that ceiling, which is the mechanism behind the pre-increase lock-in.

Transfers use the ordinary EPP authorization code, the per-domain authInfo secret issued by the losing registrar. There is no .biz-specific mechanism, no tag system and no registry form. The losing registrar must release the code and lift clientTransferProhibited within five days of a valid request, and a transfer adds a year to the term. The three standard sixty-day locks apply - after initial registration, after a prior transfer, and after a Change of Registrant, the last with an opt-out exercised before the change. A reform approved by the GNSO Council on 12 March 2025 would replace them with 720-hour locks, but no effective date has been published.

One clarification: the RDRP is a dispute process, not a transfer restriction. A domain under RDRP or UDRP proceedings is locked for the duration, no differently from any gTLD under dispute.

WHOIS, RDAP, and privacy

.biz is a thick registry - contact data is held at the registry rather than only at the sponsoring registrar. GoDaddy Registry operates the registration data services, with nic.biz as the registry-designated site.

RDAP became the definitive source for gTLD registration data on 28 January 2025, superseding sunsetted WHOIS as the contractual system of record. Under ICANN's Registration Data Policy, in force since 21 August 2025, registrant name and contact details are redacted by default, with contact routed through an anonymised email address or a registrar web form. Privacy and proxy services are permitted, though a fully anonymised .biz sits oddly against a contractual representation of bona fide commercial use, which the registry does not police.

DNSSEC is supported, and .biz has a claim to early leadership - the zone was signed on 8 September 2010 by Neustar, roughly six months before Verisign signed .com. Internationalised domain names are supported, though the current script list should be checked against the registry's own IDN tables.

Who .biz suits, and who should avoid it

.biz works best where the audience arrives by search or referral rather than by typing a remembered name. It suits small and local businesses - trades, contractors, service businesses, local retail - whose traffic is regional and whose .com went long ago; B2B and trade-facing operations; Turkish-language projects, where biz means we, one of very few cases of a gTLD acquiring an unintended second meaning in a major language; and defensive registration alongside a strong .com.

It is the wrong choice for:

• Consumer brands that depend on recall, word of mouth or voice. .biz reads as second-choice, and a meaningful share of visitors will type .com whatever the business card says.
• Anyone whose business depends on email deliverability. Like .info, .biz has historically carried a poor reputation with spam filters, driven by cheap registration and past abuse.
• Financial services, healthcare, legal services and anyone asking users to trust a payment form.
• Pure domain investors. The restrictions explicitly exclude registering solely to sell, trade or lease a name, and the aftermarket is thin anyway.

Common mistakes with .biz

Believing the business-use restriction means registrants are vetted. The error runs both ways. Some buyers choose .biz expecting an implied credential and get a restriction that protects nobody and signals nothing. Others avoid it because they wrongly believe they must be an incorporated company; there is no legal-entity requirement at all.

Putting a personal, hobby, portfolio or opinion site on a .biz. This is the one restriction with a real, if rarely used, enforcement path: the rules expressly exclude domains used exclusively for personal, non-commercial purposes, and the RDRP lets a third party challenge precisely that. The probability is low; the exposure is specific to .biz.

Taking the .biz because the .com belongs to an established competitor. .biz was designed as a .com alternative, which makes it a magnet for exactly this move - and exactly this is what the UDRP exists to unwind. If the .com is a live trademarked business in your sector, the matching .biz is a liability.

A restriction with no gatekeeper: STOP, the RDRP, and the quiet opening of .biz

.biz was the more ambitious half of the 2001 experiment. Where .info was designed as an unrestricted general-purpose namespace, .biz was designed to mean something - an address that told you the holder was in business. Twenty-five years later the restriction is still in the contract and almost nothing rests on it.

The launch went badly before the restriction was ever tested. Rather than run a trademark sunrise, NeuLevel built an IP Claims Service and the Startup Trademark Opposition Policy (STOP), which let trademark holders challenge registrations after the fact, and allocated contested pre-registrations by random selection - drawing allegations that the exercise amounted to an illegal lottery. Amazon.com threatened suit; NeuLevel filed for declaratory judgment in a Virginia federal court in 2001, seeking confirmation that its policy violated neither trademark nor lottery law. The outcome cannot be stated with confidence from the public record.

The RDRP was the enforcement half of the design, and it rested on an assumption that did not hold. Because the registry was never required to verify anything, the whole weight of enforcement fell on third parties willing to pay to file. That works for trademark disputes, where the complainant has an obvious economic interest and a recognised right to assert. It does not work for a use restriction: nobody is commercially harmed by a stranger running a personal blog on a .biz, so nobody files, and the rule stops operating without ever being repealed.

Commercial reality finished the job. .biz peaked above two million registrations by June 2008, had fallen to roughly 1.47 million by January 2022 on the most commonly cited figure, and does not appear in Verisign's first-quarter 2026 top-ten ranking. A registry losing registrations does not add friction to registration. The 2020 operator change closed the loop: .biz now sits at a company that is also the world's largest registrar and, unlike Verisign on .com, is under no vertical-integration ban. The restriction is a term you agree to and should not knowingly breach - but it is not a filter, not a credential, and not a reason to prefer .biz over anything else.