---
name: ICANN
type: organization
status: running
version: 27.0.0
released: 1998-09-18
maintainer: Multistakeholder Community (loosely)
dependencies:
  - DNS
  - IANA
  - global consensus
  - US Department of Commerce (legacy, mostly exited)
license: Custom Nonprofit Bylaws v3 (self-authored)
tags:
  - internet governance
  - domain names
  - infrastructure
  - bureaucracy
  - california nonprofit
---

ICANN

What it actually is

A California nonprofit that holds the keys to the internet's address book and answers to approximately everyone, which means it answers to no one in particular.

How it works

ICANN coordinates the assignment of domain names and IP addresses through a structure best described as "a homeowners association for the root of the DNS, governed by a UN-sized committee, funded by registrar fees, and headquartered in Los Angeles for reasons that have never fully been explained."

The actual work runs through:

IANA: the technical function. Numbers, names, protocols. Quiet. Effective.
Generic Names Supporting Organization (GNSO): policy for gTLDs. Loud. Slow.
Country Code Names Supporting Organization (ccNSO): slightly more polite version of same.
At-Large Advisory Committee: represents end users. Advisory. Not binding. This is load-bearing irony.

"It's not a government. It's not a company. It's a process that became a building." — attributed to a participant at every ICANN meeting ever held

Features

Maintains the authoritative root zone. One file. Quietly critical.
Runs global DNS policy without formal legal authority in most jurisdictions
Introduced new generic TLDs in 2012 (.bank, .sucks, .ninja) for a one-time fee of $185,000 per application
Hosts three public meetings per year in rotating global cities, generating enormous hotel bills and moderate policy output
Successfully transitioned stewardship of IANA from the US government in 2016, a process that took longer than most international treaties

Known bugs

Bug ID	Description	Status
BUG-001	Capture by incumbent registrars	Chronic, not resolved
BUG-002	Accountability mechanisms that cannot actually be triggered	Open since v1.0
BUG-003	Meeting outputs measured in PDFs, not decisions	Won't fix
BUG-004	.org sale attempt (2019)	Patched by public outcry
BUG-005	WHOIS privacy reform took two decades	Closed, eventually

Configuration

governance_model: multistakeholder
accountability_to: community (see: bug BUG-002)
veto_holders: []
funding_source: registrar fees (indirect tax on having a domain)
meeting_frequency: 3x annually
official_language: English (with simultaneous translation and no guarantees)
board_size: 21
consensus_threshold: "rough consensus and running code" (inherited from [IETF](/ietf))

Edge cases

What happens if a government demands a TLD be removed from the root? ICANN has no clean answer. Neither does anyone else.
Sovereign ccTLDs like .uk or .de operate semi-independently. ICANN coordinates. It does not command.
If ICANN failed overnight, the existing root zone would continue propagating. The internet is more durable than its caretaker.

Changelog

v1.0 (1998): Founded under Jon Postel's shadow, weeks after his death. Inauspicious and permanent.
v10.0 (2012): New gTLD program launched. The market flooded. Most new TLDs remain lightly used.
v18.0 (2016): IANA stewardship transition completed. US government formally steps back.
v27.0 (2024): Still running. Still meeting. Still drafting policy on things that deployed years ago.

drafting spec…