ICANN (Internet Corporation for Assigned Names and Numbers) is the nonprofit organization that coordinates the Internet’s unique identifier systems: domain names, IP address blocks, autonomous system numbers and protocol parameters. Founded in 1998 and headquartered in Los Angeles, it is the central institution of Internet governance for naming, because it sets the policies under which top-level domains are created and operated.
ICANN does not control Internet content, run most of the DNS or decide who may connect to the network. Its role is narrower and more technical: it keeps the shared identifier systems globally unique, stable and interoperable, through a policy process open to governments, companies, technical experts and individual users.
What ICANN coordinates
ICANN coordinates identifiers that must be unique worldwide for the Internet to function as one network. Two names cannot point to different places, and two networks cannot use the same public address block without breaking routing.
The operational record-keeping, known as the IANA functions, is performed by Public Technical Identifiers (PTI), an affiliate of ICANN. The table below shows how responsibilities are divided.
| Identifier system | ICANN role | Who operates it day to day |
|---|---|---|
| DNS root zone | Approves changes to top-level domain delegations through PTI | Root zone maintainer and 12 root server operators |
| Generic top-level domains | Sets policy, signs registry agreements, accredits registrars | Registry operators and accredited registrars |
| Country-code top-level domains | Records delegations; policy remains largely local | National ccTLD managers |
| IP addresses and AS numbers | Allocates large blocks to regional registries through PTI | Five Regional Internet Registries |
| Protocol parameter registries | Maintains registries defined by IETF standards through PTI | PTI under IETF direction |
The division matters because ICANN’s policy authority is strongest over generic TLDs such as .com, .org or newer names. For country-code domains, national managers set their own rules, and for IP addresses, the global policy is developed bottom-up in the regional registry communities.
The multistakeholder governance structure
ICANN uses a multistakeholder model, in which policy is developed by community groups and then approved by the Board of Directors, rather than by governments or by ICANN staff alone. Each group represents a defined constituency.
| Body | Type | Represents or advises on |
|---|---|---|
| GNSO | Supporting organization | Policy for generic top-level domains |
| ccNSO | Supporting organization | Global issues concerning country-code domains |
| ASO | Supporting organization | Global number policy from the Regional Internet Registries |
| GAC | Advisory committee | Public policy views of national governments |
| SSAC | Advisory committee | Security and stability of naming and addressing |
| RSSAC | Advisory committee | Operation of the root server system |
| ALAC | Advisory committee | Interests of individual Internet users |
The Board has 16 voting directors plus non-voting liaisons, selected largely by these bodies and by a nominating committee. Advice from the Governmental Advisory Committee carries special weight: the Board must explain and attempt to reconcile any decision that departs from consensus GAC advice.
The IANA stewardship transition
Until 1 October 2016, ICANN performed the IANA functions under a contract with the United States Department of Commerce, which gave one government a formal oversight role over root zone changes. When that contract expired, stewardship passed to the global multistakeholder community.
The transition added new accountability mechanisms in place of government oversight. The Empowered Community, made up of supporting organizations and advisory committees, can reject budgets, block bylaw changes and remove individual directors or the entire Board. An independent review process allows affected parties to challenge Board decisions.
In technical terms, the transition changed almost nothing in daily operation. Root zone changes still pass through verification by PTI and publication by the root zone maintainer; what changed is who holds ICANN accountable.
How ICANN shapes the domain name market
ICANN shapes the domain industry through contracts rather than legislation. Every generic TLD registry signs a registry agreement, and every registrar that sells generic domains must hold an ICANN accreditation and follow the Registrar Accreditation Agreement.
- New gTLD program: the 2012 round received about 1,930 applications at an evaluation fee of $185,000 each and led to more than 1,200 new top-level domains; a further round was approved for the 2026 timeframe.
- UDRP: the Uniform Domain-Name Dispute-Resolution Policy, adopted in 1999, lets trademark holders recover domains registered in bad faith without going to court.
- Registration data: after the European GDPR took effect in 2018, public WHOIS output was heavily redacted, and RDAP has since replaced WHOIS as the authoritative lookup protocol for generic domains.
- Transaction fees: registrars pay ICANN a small fee per domain-year, which together with registry fees funds most of ICANN’s budget.
ICANN compared with related institutions
ICANN is often confused with other Internet institutions, but each covers a distinct layer. ICANN coordinates identifiers; it does not write protocols or web standards and does not regulate network operators.
| Institution | Main responsibility | Relationship to ICANN |
|---|---|---|
| ICANN | Policy for names and coordination of identifiers | Central coordinator |
| IANA | Registries of root zone, number blocks and protocol parameters | Functions performed by PTI, an ICANN affiliate |
| IETF | Protocol standards published as RFCs | Defines many registries that IANA maintains |
| W3C | Web standards such as HTML and CSS | Independent, no formal role in naming |
| Regional Internet Registries | Distribution of IP addresses and AS numbers | Receive large blocks through IANA |
A common misconception is that ICANN could switch off a country’s domains or the Internet itself. In practice, ccTLD operations are controlled nationally, root servers are run by independent operators, and any attempt to misuse root zone authority would undermine the trust on which ICANN’s legitimacy depends.
In plain words
ICANN is the organization that keeps the Internet’s address book consistent. Every website name and every network address must be unique, otherwise traffic would end up in the wrong place. ICANN sets the rules for who can run endings such as .com or .shop and which companies may sell names under them.
It does not decide what appears on websites. Its job is closer to a coordinator of a shared phone directory, working with governments, businesses and users so that one name always leads to one place, everywhere in the world.
A real-world example
A mid-sized outdoor equipment brand discovers that someone has registered its brand name under .com together with the word “sale” and is running a counterfeit shop. The brand’s registered trademark predates the domain by more than ten years.
Its counsel files a complaint under the UDRP, the dispute policy that ICANN requires every accredited registrar to follow. The complaint must show that the domain is confusingly similar to the trademark, that the registrant has no legitimate interest and that it was registered and used in bad faith. The case is decided on written submissions by a panel at an approved dispute-resolution provider.
About two months after filing, the panel orders a transfer, and the registrar moves the domain to the brand. No court, no national lawsuit and no cross-border enforcement were needed, because the obligation to comply flows from ICANN’s contracts with registrars.