.net domain names

What .net is

.net is short for network. It was created for organisations involved in networking technologies and infrastructure — network providers, internet service providers, and the operators of the internet's plumbing — but that intent has had no operative force for decades. Its IANA type is a generic top-level domain (gTLD), non-sponsored and legacy, with an IANA registration date of 1 January 1985. The first .net registered was nordu.net, the Nordic university network, that same day.

The registry operator as of 2026 is VeriSign, Inc., through VeriSign Global Registry Services in Reston, Virginia, with the IANA record last updated 10 March 2026. The lineage matches .com: SRI International's Network Information Center, then Network Solutions under a National Science Foundation agreement, then Verisign after the 2000 acquisition. Verisign kept the registry when it sold the registrar arm in 2003, and there has been no change of operator since.

One structural difference from .com matters: .net's contract went through a genuine competitive rebid. Verisign's agreement expired on 30 June 2005, ICANN put the registry out to tender, and Verisign won against rival bidders. Renewals since have been presumptive, with the current agreement renewed in 2023 for a term running to 30 June 2029.

Who can register .net

Anyone, anywhere, for any purpose. There is no nexus requirement, no networking-industry test, no documentation, no validation and no registry verification. The for-network-organisations framing is purely historical.

This cuts both ways. Some buyers wrongly assume they are ineligible because they are not an infrastructure company; others assume, more damagingly, that a .net signals technical credentials to visitors. It confers nothing. The only check is the registrar-level contact verification required of all gTLD registrars.

What .net costs to own

.net has no external price cap. Unlike .com it is not covered by the NTIA Cooperative Agreement, and its only constraint is the ICANN registry agreement, which permits Verisign to raise the wholesale fee by up to 10% a year. That is a looser leash than .com's 7% in four years out of six, and the asymmetry surprises most buyers: the smaller, less commercially critical zone has more pricing freedom, purely because no US government instrument applies to it.

Increases have been real but periodic rather than annual — a documented example is the 10% rise effective 1 February 2023, the first since 2018, and analysis of the 2023 renewal noted that maximum permitted increases to June 2029 would roughly double the wholesale fee. Before any increase, registrars get six months' notice and registrants may renew up to ten years at the pre-increase price.

There is no registry premium tier for .net, so an elevated price on a desirable name is an aftermarket ask rather than a registry charge. First-year and renewal fees are identical at the registry level, and any retail gap is a registrar promotion — often proportionally larger for .net, a frequent loss-leader. After expiry a name passes through an auto-renew grace period, then the Redemption Grace Period, the window after deletion during which only the original registrant can restore it, at a fee substantially above a renewal.

Registration terms, renewals, and transfers

Minimum registration is one year, maximum ten, and expiry may never sit more than ten years in the future. Renewals stack up to that ceiling.

Transfers follow standard gTLD policy, with no .net-specific restrictions. Authorisation uses a per-domain EPP authInfo code, and the losing registrar must supply it and remove the clientTransferProhibited status within five days of a valid request. A successful transfer adds one year to the term. Sixty-day locks apply after initial registration, after a prior inter-registrar transfer (except transfers back to the original registrar where both agree), and after a Change of Registrant, which the registrant may opt out of before the change but not afterwards.

The pending ICANN Transfer Policy reform reaches .net on the same industry-wide timetable as everything else. Approved by the GNSO Council on 12 March 2025, it would replace the sixty-day locks with 720-hour (thirty-day) locks and a time-limited Transfer Authorization Code. No effective date is confirmed, so the sixty-day locks remain live.

WHOIS, RDAP, and privacy

RDAP has been the definitive protocol for gTLD registration data since 28 January 2025, superseding port-43 WHOIS as the contractual system of record.

.net is a thin registry, exactly like .com: the registry holds the sponsoring registrar, nameservers, status and dates, while contact data sits with the registrar and a registry-level query returns a referral. ICANN's 2017 Thick WHOIS Transition Policy would have changed this, but implementation stalled over unresolved Registry-Registrar Agreement amendments and GDPR concerns. Research on a .net owner therefore takes two lookups, and your registrar is the sole custodian of your contact record.

Registrant data is redacted by default under the ICANN Registration Data Policy, in force since 21 August 2025, with contact through an anonymised email address or a registrar web form. Privacy and proxy services are permitted; Verisign imposes no registry-level restriction.

DNSSEC is supported — Verisign signed .net in 2010, ahead of .com in March 2011 — and internationalized domain names are supported at the second level across the same broad range of scripts as .com.

Who .net suits, and who should avoid it

.net genuinely suits networking, infrastructure, hosting, ISP, telecom, VPN, CDN and connectivity businesses, where the extension is semantically apt rather than a consolation prize. It works for technical communities, developer tooling and open-source infrastructure, where it carries credibility it would not carry for a bakery. It suits membership networks and multi-site organisations, and it is the sensible defensive registration for anyone who owns a strong .com. Where a .com is genuinely unavailable, .net remains the least jarring alternative.

It should be avoided by consumer brands that depend on word of mouth and voice recall when the matching .com is an active, live business: traffic leakage is real and permanent, and you will spend the life of the brand saying dot net, not dot com. It should be avoided outright by anyone taking the .net because the .com belongs to a trademark holder in the same field — that is a dispute waiting to be filed under the Uniform Domain-Name Dispute-Resolution Policy.

Common mistakes with .net

• Treating .net as a free pass to a name someone else has branded under .com. If the .com is a live business in your sector, the .net gives you trademark exposure and permanent traffic leakage at once, and the loss compounds with every pound spent promoting it.
• Misreading eligibility in either direction. Some buyers rule out .net believing it is reserved for networking companies; others register it believing visitors will infer technical competence. It is fully unrestricted, and it confers no credential.
• Not modelling renewal cost. .net is a frequent deep-discount first-year loss-leader, and its registry fee may climb 10% a year. The gap between the promotional first year and the ten-year total is wider than most buyers expect, and portfolio registrants meet it across dozens of names at once.

The extension that outlived its job

.net is the only original top-level domain whose stated purpose was genuinely technical, and the only one that has completely lost it. The 1985 plan was coherent: .com for commerce, .org for everything else organisational, .net for the organisations running the network itself. nordu.net, the first registration, was exactly that — a Nordic academic networking consortium using an extension built for its kind, which almost no .net registrant today could claim.

The expectation collapsed for the same reason .com's commercial rule collapsed: nobody enforced it, and demand for names vastly outran the categories. By the mid-1990s .net was open to anyone, and its meaning shifted from a statement about what you do to a statement about what was still available. That is the role it has held since: the reflexive second choice, taken when the .com is gone and the buyer wants the smallest possible drop in familiarity.

Being the default alternative is both an asset and a trap. The asset is recognition — .net is the one non-.com extension a mainstream audience reads without hesitation. The trap is that the same audience knows a .net is often a .com's understudy, and their fingers type .com anyway.

The numbers describe a giant that stopped growing. Verisign's Domain Name Industry Brief reported .net at 12.5 million registrations at the end of the second quarter of 2026, still among the ten largest TLDs and ranked fourth in the brief's first-quarter 2026 table, but essentially flat to declining for a decade while the overall market grew to 401.6 million domains. It did not shrink so much as stand still while everything around it expanded.