.net domains: the infrastructure TLD that became everyone's plan B

• Registry operatorVerisign (IANA lists VeriSign Global Registry Services)
• IntroducedOriginal generic set, January 1985
• RestrictionsNone in practice
• Typical useTech, hosting, services, fallback brands

Built for networks

.net was created in the original DNS rollout, and the name comes from "network". It was meant for organisations that ran network infrastructure: ISPs, backbone providers, gateways and similar operators. The first registered .net name, according to Wikipedia, was nordu.net, still used by the Nordic research network NORDUnet. Over the years the restriction faded, and today it is a general-purpose extension with no eligibility test for new registrants.

Operator and contract history

Verisign, which acquired Network Solutions, ran .net under a contract that expired in 2005. ICANN opened a competitive process for a new operator, and Verisign won it and kept the registry. The agreement has since been renewed on a multi-year cycle. IANA's root zone database still lists Verisign as the manager as of 2026. Because the same company runs .com and .net, they share infrastructure behaviour: the same style of daily zone updates, the same drop mechanics and similar contract terms.

Why it is "second choice"

When a business wants brand.com and finds it taken, brand.net is the usual next attempt. It has the same recognition-by-association, works in any email or app that accepts ".com-like" suffixes, and users type it correctly more often than newer extensions. That is a strength and a weakness: you get credibility, but you also invite visitors to mistype .com and land on a competitor, or on a parked page of whoever owns the .com.

Where .net still looks natural

• Hosting providers, DNS and CDN-style services
• Network and ISP-adjacent businesses
• Developer tools and technical communities
• Regional brands for which the .com is held by an unrelated company

Scale

Verisign's quarterly Domain Name Industry Brief series put .net at about 12.5 to 12.6 million registrations in 2026 (12.5 million at the end of Q2, 12.6 million at the end of Q3 per trade coverage), placing it among the top few TLDs by size but far below .com. Its absolute size is large enough that the aftermarket is liquid for good names, though prices are generally lower than the equivalent .com. Our overview of how many domains exist puts these numbers in context.

Pricing pattern

Verisign sets a wholesale price under its ICANN agreement, with limits that have historically restricted large jumps. Retail prices follow that wholesale rate plus registrar margin. Expect first-year promotions that are modest, and renewal close to the list price. Do not assume .net is cheaper than .com in practice: the gap at registrars is often small. The price you care about is the renewal, since you will pay it every year.

Practical setup notes

Because .net sits next to .com in many buyers' minds, a few habits help. Register both if you can, and point the secondary name at the primary with a permanent redirect so that typos still land on your site. Set up email on the name you will publish, not on the redirect. If you run a service that exposes hostnames to customers (for example node1.example.net style infrastructure names), a short, stable .net name tends to age well, because customers recognise the suffix as technical. For a consumer shop, a .net name can feel dated beside a clean .com or a short modern extension, so test it on real users before committing.

Also check history before buying a second-hand .net. A name that served spam or a hosting abuse case years ago can carry a damaged sender reputation even after it changes hands. See how to evaluate an expired domain for the checks that apply.

Reputation

.net has a solid reputation overall and does not carry the stigma of low-cost new TLDs. Like every large extension it hosts some abuse, but I would not cite a rate without a named source for a particular year; Spamhaus and Interisle both publish periodic comparisons you can check. Email deliverability is typically fine.

Drops and the aftermarket

.net names expire and are deleted under the same lifecycle as .com; see the domain lifecycle. Because fewer people hunt .net drops than .com drops, a good .net name sometimes lasts longer in the pending-delete queue, although drop-catching services do cover it. Look at backorder services if you want a specific name.

When to pick it

Choose .net if the name fits a technical or service brand, or if you cannot acquire the .com and are prepared to explain the difference. Otherwise consider .org for communities or a modern TLD such as .io, and see the three-way .com, .net and .org comparison.

Frequently asked questions

Who operates .net?

Verisign, the same company that runs .com. The IANA root zone database lists VeriSign Global Registry Services as the .net manager.

Is .net only for network companies?

No. It was designed for networks but has no practical eligibility restrictions today, so anyone can register a .net name through a registrar.

Is .net bad for SEO?

No. Search engines treat it as a generic TLD, and there is no ranking penalty compared with .com.

Is .net cheaper than .com?

Sometimes slightly, but the difference at most registrars is small, and both follow Verisign wholesale pricing. Always compare the renewal price, not only the first-year price.

Should I buy the .net as well as my .com?

Defensive registration makes sense if the brand is valuable, because visitors may mistype. For a small project, it is usually optional.

Can a .net domain be found in a daily zone file?

Yes, .net is a generic TLD whose zone is available via ICANN CZDS to approved requesters. See zone files and CZDS.