Who owns the internet?
Nobody. Sort of.

There is a pleasing version of this story: on September 18, 1998, a tiny California nonprofit appeared and took charge of the world’s domain names. It fits neatly into an “on this day” box. It also compresses months of policy arguments, draft documents, public comments, and legal steps into a birthday that the primary record does not support.

ICANN’s board record says its Articles of Incorporation were filed with California’s Secretary of State on September 30, 1998. A later ICANN declaration uses the same date. September 18 survives in secondary accounts as the day ICANN was “created,” but the clearest corporate milestone is September 30. Today’s useful discovery is therefore a warning about internet history: even the organization responsible for unique identifiers can acquire two competing dates.

The problem was bigger than domain shopping

By the late 1990s, the internet’s naming and numbering functions had outgrown their research-network origins. The U.S. Department of Commerce’s June 1998 “White Paper” proposed moving technical coordination toward a private, nonprofit corporation built around stability, competition, private bottom-up coordination, and international representation. It did not propose a ministry of the internet. It proposed a home for a small set of functions that cannot tolerate conflicting answers.

A domain such as example.com works because the Domain Name System can lead a resolver from the root, to the servers responsible for .com, and then to the authoritative record for the requested name. The root does not store every website. It stores referral information for top-level domains. ICANN helps coordinate the index to the address books, not the contents of every book.

What ICANN actually coordinates

ICANN’s mission centers on the internet’s unique identifier systems. In practice, that includes the DNS root zone, high-level coordination of IP address resources, and registries for protocol parameters used by networked systems. ICANN also contracts with operators of generic top-level-domain registries and accredits domain registrars.

Its reach is real but bounded. ICANN does not decide what appears on a website, connect your home to the internet, remove spam, or operate most root-server infrastructure. It operates the L-root identity; independent operators run the others. The current system uses 13 root identities delivered through more than 1,500 server instances around the world—not 13 lonely machines in one room.

Why one root still matters

The DNS was designed to return consistent answers. If incompatible roots both claimed authority over the same name, typing one address could lead to different destinations depending on which system answered. ICANN calls the desired property “universal resolvability”: the same domain should predictably refer users to the same place wherever they are.

This does not make ICANN the owner of the network. Its Articles of Incorporation describe the internet as an international network of networks “owned by no single nation, individual or organization.” The authority is closer to a shared rulebook and a coordinated ledger than a master switch.

The practical lesson for a domain owner

When you register a domain, you are not buying a permanent piece of the internet from ICANN. You are purchasing a time-limited registration through a registrar, under policies and contracts that connect the registrar, the top-level-domain registry, and ICANN’s coordination system. That is why renewal dates, registrar access, contact details, transfer locks, and account security matter more than the phrase “own your domain.”

Keep the registrar account under an address you control, enable strong multi-factor authentication, record the renewal date outside the registrar’s dashboard, and make sure a future buyer can verify ownership cleanly. Those mundane steps are where internet governance lands on an ordinary site owner’s desk.