.NET: 209 Million Domains, the Internet's Oldest Registration, and the TLD That Became What It Was Named For

On 1 January 1985, a record was created in the Domain Name System for nordu.net — a domain for NORDUnet, the collaborative research network linking Denmark, Finland, Iceland, Norway, and Sweden. It is the oldest domain name on the Internet. Not the oldest .com — that is symbolics.com, registered 73 days later on 15 March 1985. The oldest domain, period. A Nordic research network chose .net because they were a network. The TLD was for networks.

RFC 920, published by Jon Postel in October 1984, laid the groundwork for the domain name system. When the first TLDs were implemented in January 1985, .net was designated for organizations involved in networking technologies — Internet service providers, backbone operators, infrastructure companies. RFC 1591, published in 1994, was explicit: "NET is intended to hold only the computers of network providers." Not general-purpose websites. Not anyone who missed out on a .com. Network providers.

A Reddit user Manovsteele asked us to analyze .NET. When we parsed the dataset, we did not find a general-purpose overflow namespace for .com. We found a map of the world's broadband infrastructure.

We parsed 209,148,051 entries under .NET from the DomainsProject dataset, cross-referenced with Verisign's Domain Name Industry Brief (Q3 2025), ICANN registry agreement documents, and Verisign's 2025 financial reports.

The headline: 68.8% of all .NET entries in our dataset — 143.9 million out of 209.1 million — are ISP reverse-DNS infrastructure. Comcast alone accounts for 40.6 million entries, more than triple Verisign's entire registered .NET domain base of 12.5 million. ISPs from 11 countries — the United States, Taiwan, the United Kingdom, France, Spain, Denmark, Chile, Ukraine, Thailand, Canada, and Australia — chose .NET for their reverse-DNS hostnames, turning a TLD that was supposed to be for network organizations into a literal map of global residential broadband. The TLD fulfilled its destiny. Just not the way anyone planned.

The Data

DomainsProject continuously crawls and indexes domains across every delegated TLD in the IANA root zone. For this analysis, we parsed the full .NET dataset file — all 209 million lines.

.NET ranks second in our entire dataset — behind only .com — yet holds just 12.5 million registry registrations. The 16.7x multiplier between our count and Verisign's official number is the largest of any major TLD. For comparison, .uk has a 3.5x multiplier, .br has 6.1x, and .nl has 4.6x. The reason is infrastructure: ISPs across the globe assigned reverse-DNS hostnames under their .net domains to hundreds of millions of broadband connections. Each hostname — each pool-71-184-xxx-xxx.bstnma.fios.verizon.net or cpc145438-basl14-2-0-cust768.20-1.cable.virginm.net — is a resolvable record in the global DNS. Our crawler found them.

Our dataset observes 20.3 million hostnames with no subdomain prefix — entries of the form example.net rather than subdomain.example.net. These map to approximately 20.4 million unique second-level domains. The gap between 20.4 million observed SLDs and Verisign's 12.5 million registry count reflects domains still resolving despite expiration, cached DNS entries pending deletion, and zone-file lag. The 16.7x multiplier compares total entries — including the 188.9 million subdomain hostnames — against Verisign's count of currently registered domains.

The Scorecard: The Internet's Invisible Address Book

Top ISP Infrastructure Domains in .NET

Nearly seven out of every ten .NET entries in our dataset are ISP reverse-DNS records. These are not websites. They are not services. They are the addresses of cable modems, fiber terminals, DSL gateways, and mobile handsets — the endpoints of the Internet itself. When you run a traceroute from New York to Tokyo, the intermediate hops resolve to names like be-33651-cr01-nyc1.core.as7922.net (Comcast backbone) or ae-2.r02.tokyjp05.jp.bb.gin.ntt.net (NTT Japan). You are reading .NET.

ISP Infrastructure by Country

The United States alone accounts for 36.2% of all .NET entries — 75.7 million hostnames from seven ISPs. Taiwan's single provider, Chunghwa Telecom (trading as HiNet), contributes 20.2 million entries — more than the UK's Virgin Media, more than France's two ISPs combined. This is not a reflection of Internet usage. It is a reflection of which ISPs chose .net domains for their reverse-DNS infrastructure in the 1990s, a decision that propagated through decades of network growth.

Comcast's .NET: One ISP, 40.6 Million Entries

Comcast is the largest cable Internet provider in the United States, serving approximately 32 million broadband customers. Its infrastructure runs on .net.

Comcast's combined footprint — 40.6 million entries under comcast.net plus 6.5 million under comcastbusiness.net — totals 47 million hostnames. That is 22.5% of every .NET entry in our dataset. One ISP, one-fifth of a TLD. For context: Comcast's .NET footprint exceeds the entire registered domain base of .de (Germany's 17.7 million), .uk (10.3 million), and .nl (6.1 million) combined.

These entries follow predictable patterns: c-73-37-17-179.hsd1.or.comcast.net (residential), 75-145-165-40-illinois.hfc.comcastbusiness.net (business), be-33651-cr01-nyc1.core.as7922.net (backbone). Each encodes geography (state abbreviation), network type (HFC, DSL, fiber), and customer classification. They are machine-generated, never typed into a browser, and invisible to anyone who does not run a traceroute or read a DNS log. Yet they are the most numerous hostnames under .net by an order of magnitude.

The irony is structural. Comcast — an ISP, a network provider, exactly the kind of organization RFC 1591 envisioned as a .net registrant — never chose .net for its corporate website (that is comcast.com) or its streaming service (peacock.com) or its brand identity (xfinity.com). It chose .net for the infrastructure underneath. The plumbing, not the storefront.

The Global Broadband Map: What ISP Data Reveals About Internet Topology

The .NET dataset is not just a domain list. It is a census of residential broadband infrastructure across 11 countries. Each ISP's presence tells a story about that country's Internet market.

Taiwan's HiNet dominates with 20.2 million entries under a single domain — hinet.net. Chunghwa Telecom, the former state telecom monopoly privatized in 2005, passes fiber to 97% of Taiwanese households. Its 20 million reverse-DNS entries under .net represent one of the densest ISP footprints per capita in our dataset: roughly one entry for every 1.2 Taiwanese residents. HiNet assigned individual hostnames in the format 218-162-60-169.dynamic-ip.hinet.net to dynamic IP allocations — a legacy decision from the late 1990s that the DNS has preserved ever since.

Virgin Media's 15.5 million entries are the fingerprint of the UK's cable monopoly. Unlike BT (which uses btcentralplus.com), Virgin Media routes its entire cable broadband infrastructure through virginm.net. The entries follow UK geographic patterns: cpc145438-basl14-2-0-cust768.20-1.cable.virginm.net encodes the exchange code ("basl" for Basildon) and network topology. Virgin Media is the only major UK broadband provider whose infrastructure appears under .net rather than .com — an artifact of its origins as NTL:Telewest, the cable company that predated Virgin's rebrand in 2007.

France contributes two ISPs with distinct profiles: SFR (Altice group, 14.8 million entries) and Free (Iliad group, 2.8 million under proxad.net). Together they account for 8.4% of all .NET entries. Free's parent domain — proxad.net, from "Proxad" (Provision et exploitation de serveurs d'accès aux données) — preserves the original 1990s company name in its DNS infrastructure, a pattern repeated across the dataset. ISPs change brands. Their reverse-DNS rarely follows.

The geographic spread tells a story about timing. The ISPs that dominate .NET's infrastructure layer are overwhelmingly providers that built their broadband networks in the late 1990s and early 2000s — Comcast, HiNet, Virgin/NTL, SFR, Telefonica, BellSouth, Qwest. They chose .net for reverse-DNS because the TLD was for networks, and they were networks. Newer providers — Google Fiber, Starlink, 5G-first operators — do not appear in significant numbers. The .NET infrastructure layer is a time capsule of the broadband buildout era.

The Oldest Domain on Earth: nordu.net and the Original Vision

The first entry in the domain name system was not a .com. It was not a university. It was nordu.net — registered on 1 January 1985 for NORDUnet, the Nordic research and education network collaboration.

nordu.net predates every other domain on the Internet by 73 days. Symbolics.com, commonly cited as the "first domain name," was registered on 15 March 1985. But the DNS database entries for nordu.net carry a creation date of 1 January 1985 — the day the root zone was initialized with the first TLD entries. NORDUnet's domain served as the identifier for nic.nordu.net, one of the original root server hosts. The oldest domain on the Internet was literally a piece of network infrastructure, registered under the TLD designed for network infrastructure.

Jon Postel's RFC 920 (October 1984) defined the initial top-level domain structure: .com for commercial, .edu for educational, .gov for government, .mil for military, .org for organizational. .NET was added during implementation as the sixth original TLD — specifically for entities "involved in networking technologies." The first six .net domains registered between 1985 and 1986 were all network organizations: nordu.net, nsf.net (the National Science Foundation Network that became the Internet backbone), isi.net (Postel's own Information Sciences Institute), and others.

.NET began its life as exactly what it was supposed to be. The deviation came later. By the mid-1990s, the explosion of commercial Internet demand exhausted desirable .com names, and .net had no enforcement mechanism for its "network providers only" restriction. Unlike .edu (verified by EDUCAUSE) or .gov (verified by the US General Services Administration), .net accepted anyone willing to pay. The TLD drifted from its purpose — and then, through ISP reverse-DNS, drifted back. The 143.9 million infrastructure entries in our dataset are the echo of Postel's original intent, realized through a mechanism he never anticipated.

Verisign's Dual Monopoly: One Company, Two Critical TLDs

Verisign operates the registry for both .com and .net — the #1 and #2 TLDs in our dataset, holding a combined 1.2 billion entries and 173.5 million registry registrations (Q4 2025). No other entity controls two top-level domains of this scale.

The Financial Picture

Verisign does not report .com and .net revenue separately. But the pricing tells a story.

The Pricing Paradox: .NET Costs More Than .com

.NET — the smaller, declining, less valuable TLD — costs $0.65 more per domain than .com and carries a more aggressive price escalation. At full exercise of the 10% annual increase, .NET's wholesale price would reach $19.31 by the end of the current contract in 2029. The trajectory from the 2005 competitive bid price of $3.50 to the potential 2029 price of $19.31 represents a 452% increase over 24 years.

The Competitive Bid That Was Never Repeated

In 2005, ICANN did something it has never done before or since for a major gTLD: it put .NET out to competitive bid. Five consortia submitted proposals — Verisign, Sentan/JPRS (Japan), Afilias, DENIC (Germany), and CORE++. ICANN hired Telcordia Technologies as an independent evaluator. All five were deemed technically capable. Verisign won, but the competitive pressure drove its bid price to $3.50 per domain — a 42% reduction from the prior rate.

The next .NET contract renewal, in 2011, was not competitive. Nor was the 2017 renewal, nor the 2023 renewal. When the 2023 contract was proposed, the Internet Commerce Association estimated that competitive pricing should place .NET at $1-3 per domain. TurnCommerce estimated the contract's total value at $1.17 billion over six years, with ICANN receiving $59.4 million from Verisign. When critics demanded a competitive rebid, ICANN responded that putting TLDs out to bid is "against internet users' interest."

ICANN collected $59.4 million from the entity it chose not to compete, for a contract critics valued at roughly $1 billion over market rate. Of the nearly 1,200 gTLDs overseen by ICANN, .com, .net, and .name remain the only three governed by maximum price restrictions — a structure that, paradoxically, guarantees Verisign the right to raise prices rather than constraining them.

The Shrinking Registry: Peak to Decline

.NET Registration Trend (Verisign DNIB)

.NET has lost 3.3 million registrations since its 2016 peak — a 20.9% decline in nine years. The zone grew 10x between 2000 and 2013, peaked at 15.8 million in the third quarter of 2016, and has contracted every year since. In 2022, .NET new domain creation fell 14% year-over-year — nearly double .com's 9% decline — indicating that .NET is significantly more price-sensitive than its sibling TLD.

The decline accelerated after the 2023 contract renewal authorized 10% annual price increases. Between Q1 2023 and Q3 2025, .NET lost 700,000 registrations while wholesale prices rose from $9.02 to $10.91. Verisign's revenue still grew — higher prices on fewer domains — but the registry is shrinking. At the current rate of decline, .NET will fall below 10 million registrations before its current contract expires in 2029.

The Microsoft Collision: When a Trillion-Dollar Company Appropriated a TLD Name

In June 2000, Steve Ballmer announced Microsoft's ".NET strategy" — described as the company's "most ambitious undertaking since Internet Strategy Day in 1995." Originally codenamed Next Generation Windows Services, Microsoft branded everything with ".NET": Visual Studio .NET, Visual Basic .NET, ASP.NET, .NET Passport, .NET My Services, .NET Enterprise Servers. The company even planned "Windows .NET Server" before renaming it Windows Server 2003.

The .NET Framework shipped on 15 January 2002 — and the naming collision between a programming framework and a top-level domain has persisted for 24 years. Microsoft chose ".NET" to evoke the Internet — the exact same rationale behind the TLD created 17 years earlier. The framework's official website is dotnet.microsoft.com (not dotnet.net or asp.net, both of which Microsoft owns). In November 2020, Microsoft dropped "Core" and "Framework" from its branding, leaving the platform simply called ".NET" — further cementing the collision.

The confusion is not theoretical. Search ".NET" and the first page of results is Microsoft documentation. The TLD that was supposed to be the Internet's network namespace shares its name with the most widely deployed server-side framework on Earth. Microsoft — a company with the resources to register any brand — chose a three-letter word that was already the addressing scheme for Comcast's 40.6 million broadband connections.

The "Second Choice" Problem: .NET as the Perpetual Understudy

For registrants who are not ISPs — the 31.2% of .NET entries that are not infrastructure — the TLD occupies an uncomfortable position: universally recognized but never preferred.

A GrowthBadger study found that .NET's memorability score is 25%, versus .com's 44%. Users are 3.8x more likely to guess that a website uses .com regardless of its actual extension. .NET has 88% awareness (versus .com's 95%) but far lower recall — people know it exists, but they default to .com when typing an address.

Three of the Fortune 500 use .net as their primary domain — all in healthcare (including HCSC, the Blue Cross Blue Shield parent). The remaining 497 use .com. In the Alexa Top 1 Million websites, roughly 32,700 (3.3%) use .NET. On the domain aftermarket, .NET holds approximately 4% of transactions by volume; every single domain sale exceeding $1 million in 2023-2024 was a .com.

The notable .NET websites that persist — speedtest.net (Ookla), behance.net (Adobe), battle.net (Blizzard), sourceforge.net — tend to be technical or infrastructure-adjacent services. Sourceforge.net, the pioneering open-source hosting platform launched in 1999, contributes 52,755 subdomains to our dataset. But even these are exceptions. Behance is accessible at behance.net but owned by Adobe (adobe.com). Battle.net was briefly rebranded to Blizzard App before Blizzard reverted the name. The pattern is consistent: .NET domains are either infrastructure or afterthoughts.

Non-ISP Infrastructure in the Dataset

Even the non-ISP entries are overwhelmingly infrastructure. GoDaddy's hosting backend (secureserver.net), Microsoft's CDN (azureedge.net), MongoDB's database clusters, Atlassian's SaaS platform — these are services that other websites depend on, not websites that users visit directly. The pattern reinforces the thesis: .NET is the Internet's plumbing layer, whether through ISP reverse-DNS or cloud infrastructure hostnames.

What's at Stake

The .NET data reveals structural dynamics that extend beyond a single TLD:

• 68.8% of the second-largest TLD by dataset volume is invisible infrastructure — ISP reverse-DNS that no human types but every packet traverses. Strip away the infrastructure and .NET's 209 million entries collapse to roughly 20 million direct registrations — smaller than .de, .org, or .xyz.

• Verisign operates both .com and .net with no competitive pressure — the only time ICANN introduced competition for .NET (2005), wholesale prices dropped 42%. ICANN has not repeated the experiment, while collecting tens of millions from the renewal.

• .NET's wholesale price exceeds .com's despite being 13x smaller and declining — the pricing paradox suggests Verisign extracts maximum revenue from a captive base of registrants who chose .NET decades ago and face switching costs to abandon it.

• The TLD is contracting at 20.9% from peak while prices rise 10% annually — this is the textbook death spiral for a subscription product: raise prices, lose customers, raise prices more to compensate. At current trajectory, .NET will breach 10 million registrations before the contract expires.

• .NET's ISP infrastructure layer is a time capsule — the ISPs that dominate are broadband-era providers from the late 1990s and 2000s. Newer providers do not use .NET for infrastructure. As legacy networks are retired, the infrastructure layer will erode alongside the registry.

What Would Help

1. ICANN: Put .NET out to competitive bid again. The 2005 bid produced a 42% price reduction and five technically capable bidders. The 2023 renewal produced a $1.17 billion contract with no competition. ICANN's claim that bidding is "against internet users' interest" is contradicted by the only evidence available — the 2005 bid itself.

2. Registrants: Audit defensive .NET registrations. If you own example.com and example.net solely to prevent others from registering it, calculate the cumulative cost. At $10.91/year rising 10% annually, a defensive .NET registration will cost $170+ over the next decade. For most organizations, that money buys nothing.

3. Security researchers: Use .NET infrastructure data for network mapping. The ISP reverse-DNS entries in our dataset — available at /dataset — provide a granular view of broadband topology across 11 countries. The hostname patterns encode geography, network type, and provider identity. This is open-source intelligence hiding in plain sight.

4. Verisign: Publish .NET financials separately. The combined .com/.net reporting obscures the economics of a declining TLD subsidized by an expanding one. Investors and regulators cannot assess whether .NET pricing is justified if the revenue and cost data are aggregated.

5. ISPs: Modernize reverse-DNS infrastructure. The .NET infrastructure layer preserves hostnames from decommissioned ISPs (mycingular.net ceased to exist as a brand in 2007; bellsouth.net merged into AT&T in 2006) and retired network architectures. Legacy reverse-DNS creates confusion for abuse reporting and network diagnostics. The broadband industry would benefit from an RFC-guided standard for reverse-DNS naming conventions.

This analysis is based on data from the DomainsProject dataset, which continuously crawls and indexes every delegated TLD in the IANA root zone. The .NET dataset file contains 209,148,051 entries. Registry statistics are from Verisign's Domain Name Industry Brief (Q3 2025). Financial data is from Verisign's FY2025 earnings release. Pricing data is from the ICANN .NET Registry Agreement (2023) and ICANN .COM Registry Agreement (2024). Historical registration data is from Verisign's DNIB quarterly reports. The GrowthBadger memorability study and Fortune 500 analysis are from publicly available research. Explore the full dataset at /dataset or browse TLD statistics at /stats/.