ICANN

ICANN (Internet Corporation for Assigned Names and Numbers), also known as the Internet Corporation for Assigned Names and Numbers, is a nonprofit, multi-stakeholder organization incorporated under California law in 1998. It is responsible for coordinating the technical policies and databases that make the global internet function as a single, unified network. Specifically, ICANN manages the allocation of IP addresses, the assignment of DNS names, and the distribution of protocol identifiers — tasks collectively known as the IANA functions. Without this coordination, the global DNS would fragment, making web addresses unresolvable across networks.

What ICANN does

ICANN's mandate covers three main areas:

Domain name system coordination. ICANN oversees the hierarchical DNS namespace, publishing and maintaining the root zone file — the authoritative list of all top-level domains (gTLDs and country-code TLDs). Changes to the root zone take effect only after ICANN authorization.
IP address allocation. ICANN delegates large blocks of IP address space to the five Regional Internet Registries (RIRs), which in turn sub-allocate addresses to ISPs and organizations. This delegation is administered through the IANA functions.
Protocol parameters. ICANN maintains registries of protocol numbers, port assignments, and other identifiers used by internet standards bodies such as the IETF, preventing conflicting use of the same protocol values.

In addition, ICANN sets policy for the accreditation of domain registrars and the operation of domain registries, runs dispute-resolution mechanisms, and convenes the global internet community to develop consensus-based policy.

History

ICANN was formed on 18 September 1998 when the United States Department of Commerce signed a Memorandum of Understanding with the newly incorporated nonprofit. Before ICANN, these coordination functions were performed informally by a small group of researchers — most famously Jon Postel — under US government contracts. The creation of ICANN represented a formal transfer of those functions to a private, international nonprofit, though the US government retained oversight through a contract known as the Joint Project Agreement (JPA), later replaced by an Affirmation of Commitments in 2009.

The most significant governance milestone since ICANN's founding was the 2016 IANA stewardship transition. For decades, ICANN performed the IANA functions under a contract with the US National Telecommunications and Information Administration (NTIA). International governments and civil society groups had long argued that this arrangement gave the US government disproportionate control over a global resource. On 1 October 2016, following an extensive multi-year process, the NTIA contract was allowed to expire. The IANA functions were transferred to ICANN on a permanent basis, with accountability mechanisms — including the power to remove ICANN's board — vested in the global multi-stakeholder community rather than any single government. This transition was widely regarded as a landmark in internet governance, though it also attracted criticism from some governments who wanted intergovernmental bodies such as the ITU to take over oversight.

The IANA functions

The Internet Assigned Numbers Authority (IANA) is the operational department within ICANN that carries out the day-to-day coordination tasks. Its three core functions are:

Root zone management. When a registry operator needs a new TLD or a change to an existing one published in the root zone, IANA processes and implements the change after ICANN authorization and publication by the root zone maintainer (currently Verisign under a cooperative agreement with the US Department of Commerce).
IP address allocation. IANA allocates large blocks of IPv4 and IPv6 address space to the five RIRs (ARIN, RIPE NCC, APNIC, LACNIC, AFRINIC), which then assign addresses regionally.
Protocol parameters. IANA maintains registries of values used in internet protocols as specified by the IETF, including port numbers, media types, and time zone data.

The gTLD program and new gTLDs

For most of the internet's commercial era, the generic top-level domain namespace was highly restricted — dominated by legacy strings such as .com, .net, .org, .gov, .edu, and .mil. ICANN launched its New gTLD Program in 2012, which for the first time allowed any organization to apply to operate a new gTLD — from .shop and .app to .nyc and .bank. The first round received 1,930 applications; by 2014 ICANN had begun delegating hundreds of new strings.

The new gTLD program fundamentally changed the domain landscape, increasing the number of TLDs from roughly 22 generic strings to over 1,200 by the mid-2020s. A second application round opened in 2026, again attracting hundreds of applicants from registries, brands, and geographic communities. The program is governed by ICANN's Applicant Guidebook and requires successful applicants to enter into a Registry Agreement with ICANN, pay an annual fee, and meet technical and financial obligations.

Registrar accreditation (the RAA)

ICANN does not sell domain names directly to the public. Instead, it accredits companies — called accredited registrars — to register domain names on behalf of end users. To become an ICANN-accredited registrar, an organization must sign the Registrar Accreditation Agreement (RAA), pay an accreditation fee, and meet ongoing technical, financial, and consumer-protection obligations (ICANN Registrar Accreditation).

The RAA governs how registrars handle registration data, respond to lawful data requests, implement domain security measures, and treat registrant rights. It has been updated several times — most notably in 2013 to strengthen consumer protection and abuse-handling obligations. As of 2024 there are over 2,000 ICANN-accredited registrars worldwide.

Dispute and policy frameworks

UDRP. The Uniform Domain-Name Dispute-Resolution Policy (UDRP) was adopted by ICANN in 1999 and is mandatory for all generic TLD registrations. It provides a streamlined administrative procedure for trademark holders to challenge registrations that are identical or confusingly similar to their marks, were registered in bad faith, and are being used in bad faith. UDRP proceedings are conducted through ICANN-approved dispute-resolution providers such as WIPO and the NAF, typically resolving in 45–60 days at a fraction of the cost of litigation.

URS. The Uniform Rapid Suspension (URS) was introduced alongside the new gTLD program as a faster, lower-cost mechanism for clear-cut cases of trademark infringement. Unlike the UDRP, a URS decision results in suspension of the domain rather than transfer, and the standard of proof is higher (clear and convincing evidence).

WHOIS and RDAP. ICANN historically required registrars and registries to maintain publicly accessible WHOIS databases containing registrant contact information. This policy created significant tension with data-protection laws — particularly the EU's General Data Protection Regulation (GDPR), which came into force in May 2018. ICANN responded with a temporary specification that restricted the public display of personal registrant data. A longer-term framework, the Registration Data Request Service (RDRS), is intended to provide a standardized way for legitimate requesters (law enforcement, intellectual property holders) to access non-public registration data. The technical successor to WHOIS is the Registration Data Access Protocol (RDAP), which offers a structured, machine-readable alternative to the legacy WHOIS protocol and is now mandatory for all new-gTLD registries.

The multistakeholder model

ICANN operates under a distinctive multistakeholder governance model, in which policy is made not by governments alone but by representatives of multiple communities: commercial and non-commercial users, civil society, the technical community, registrars, registries, and governments (the latter through the Governmental Advisory Committee, or GAC). The GAC advises ICANN's Board but does not have a veto; the Board may reject GAC advice but must explain why.

This model is intended to ensure that no single government or private interest controls the internet's naming infrastructure. Participation is open, though critics argue that in practice the process is dominated by well-resourced stakeholders who can afford to attend multiple ICANN meetings per year.

Criticisms

ICANN has attracted persistent criticism from several directions:

Accountability and capture. Despite accountability reforms introduced as part of the 2016 IANA transition — including a new "community powers" mechanism to remove board members — critics argue that ICANN remains difficult for ordinary stakeholders to influence and is susceptible to capture by the contracted parties (registries and registrars) who fund much of its budget.
WHOIS and privacy. The post-GDPR WHOIS regime has been criticized from both sides: privacy advocates argue that ICANN's data-retention requirements still conflict with data-protection principles, while law-enforcement and IP-rights communities argue that the removal of public contact data has hampered anti-abuse investigations and trademark enforcement.
New-gTLD costs and concentration. The new gTLD program's high application fees (US $185,000 per string in the first round) favored well-capitalized applicants, leading to concerns about concentration of ownership. Several strings are held by registries that are themselves owned by private equity firms, raising questions about whether public-interest safeguards in registry agreements are adequate.
Speed of policy development. ICANN's consensus-based policy development process is widely seen as slow relative to the pace of change in the industry. Major policy initiatives can take years to move from inception to implementation, leaving the system poorly positioned to respond to emerging issues such as DNS abuse, AI-driven domain fraud, and blockchain naming.

ICANN and web3/blockchain naming

Alternative naming systems — such as the Ethereum Name Service (ENS), Handshake, and Unstoppable Domains — operate outside the ICANN-administered root zone. These systems use blockchain infrastructure to issue names that are not recognized by standard DNS resolvers, meaning they require custom browser extensions or special resolvers to function. ICANN does not recognize or administer these namespaces, and names registered in them carry no rights or protections under ICANN's dispute-resolution frameworks such as the UDRP. Whether and how these parallel namespaces will eventually interact with the ICANN-governed DNS remains an open question in internet governance discussions.