What is ICANN and what role does it play in domain names?
ICANN, the Internet Corporation for Assigned Names and Numbers, is a non-profit organisation that coordinates the internet's unique identifiers, most visibly the domain name system. It oversees the root zone that lists every top-level domain, decides which new generic TLDs are created, accredits the registrars that sell generic domains such as .com and .org, and sets the policies they must follow on transfers, renewals, registration data, and disputes. ICANN doesn't sell domains, host websites, or control what's published online, and most country-code domains such as .uk and .de are governed by their own registries rather than ICANN policy.
You rarely deal with ICANN directly, but its rules shape almost everything you do with a domain, from the auth code you use to transfer it to the redemption period that might save it after expiry. This article explains what ICANN is, how it's organised, which domain policies it sets, how its rules affect you as a domain owner, and what it doesn't do.
What Is ICANN?
ICANN was founded in 1998 as a California non-profit to take over coordination of the domain name system and related functions from the US government's contractors. Its mission is to help keep the internet's unique identifier systems stable, secure, and globally interoperable.
Those identifiers include:
- Domain names: The names in the DNS, starting from the root zone.
- IP addresses: The numeric addresses allocated to regional internet registries.
- Protocol parameters: Port numbers and other values used by internet standards.
ICANN is a coordinator, not an operator of most of the infrastructure. Thousands of registries, registrars, DNS operators, and network providers do the day-to-day work. ICANN sets the framework they work within for the parts it oversees.
ICANN and IANA
The Internet Assigned Numbers Authority (IANA) functions are the technical core of ICANN's role. They include maintaining the root zone database, allocating IP address blocks to the regional internet registries, and keeping protocol parameter registries. Since 2016, these functions have been performed by Public Technical Identifiers (PTI), an affiliate of ICANN, following the transition of IANA stewardship away from the US government to ICANN's global multistakeholder community.
You can query IANA's records yourself. IANA runs a WHOIS server with information about every TLD:
whois -h whois.iana.org com
domain: COM
organisation: VeriSign Global Registry Services
address: 12061 Bluemont Way
address: Reston VA 20190
address: United States of America
nserver: A.GTLD-SERVERS.NET 192.5.6.30 2001:503:a83e:0:0:0:2:30
nserver: B.GTLD-SERVERS.NET 192.33.14.30 2001:503:231d:0:0:0:2:30
...
ds-rdata: 19718 13 2 8ACBB0CD28F41250A80A491389424D341522D946B0DA0C0291F2D3D7...
whois: whois.verisign-grs.com
status: ACTIVE
remarks: Registration information: http://www.verisigninc.com
created: 1985-01-01
The output above is shortened. It shows who operates the TLD, its nameservers, its DNSSEC key, and its creation date.
How ICANN Is Organised
ICANN uses a multistakeholder model. Instead of governments alone making the rules, policy is developed by groups representing businesses, technical experts, governments, civil society, and individual internet users.
| Body | Who it represents | Main focus |
|---|---|---|
| Board of Directors | Selected by the community | Final approval of policies and budgets |
| GNSO (Generic Names Supporting Organization) | Registries, registrars, businesses, non-commercial users | Policy for generic TLDs |
| ccNSO (Country Code Names Supporting Organization) | ccTLD managers | Global issues affecting ccTLDs |
| ASO (Address Supporting Organization) | Regional internet registries | Global IP address policy |
| GAC (Governmental Advisory Committee) | National governments and intergovernmental organisations | Public policy advice |
| SSAC (Security and Stability Advisory Committee) | Security experts | Security and stability advice |
| RSSAC (Root Server System Advisory Committee) | Root server operators | Root server system advice |
| ALAC (At-Large Advisory Committee) | Individual internet users | User interests |
Policy for generic TLDs usually starts in the GNSO through a policy development process, which involves working groups, public comment periods, and Board approval. That process is slow by design, which is why changes such as new transfer rules can take years from proposal to implementation.
ICANN holds three public meetings a year in different regions, and most of its working sessions and public comment periods are open to anyone.
What ICANN Does for Domain Names
Manages the Root Zone
The root zone is the top of the DNS. It lists every TLD and the nameservers responsible for it. Through the IANA functions, ICANN processes changes to the root zone, such as a TLD changing its nameservers or DNSSEC keys. Verisign acts as the root zone maintainer, publishing the changes to the root server operators.
You can see the root's nameservers with dig:
dig +short . NS | sort
a.root-servers.net.
b.root-servers.net.
c.root-servers.net.
d.root-servers.net.
e.root-servers.net.
f.root-servers.net.
g.root-servers.net.
h.root-servers.net.
i.root-servers.net.
j.root-servers.net.
k.root-servers.net.
l.root-servers.net.
m.root-servers.net.
These 13 named root server identities are run by 12 independent organisations, and each is served by many physical instances around the world. ICANN itself operates one of them, the L-root. For how the root fits into resolution, see what DNS is and what a TLD name server is.
IANA also publishes the full list of TLDs, which you can download and inspect:
curl -s https://data.iana.org/TLD/tlds-alpha-by-domain.txt | head -n 5
curl -s https://data.iana.org/TLD/tlds-alpha-by-domain.txt | grep -vc '^#'
The second command counts the TLDs currently in the root, which is well over a thousand.
Approves New Top-Level Domains
ICANN decides when and how new generic TLDs are added. Its New gTLD Program opened applications in 2012 and led to hundreds of new extensions, such as .app, .shop, and .blog. ICANN has been preparing a further application round for several years, so more extensions are likely to appear. Country-code TLDs are delegated based on the ISO 3166-1 list of country codes rather than an application round.
For the differences between these types of extension, see gTLDs vs ccTLDs vs new TLDs.
Contracts With Registries and Accredits Registrars
For generic TLDs, ICANN has two key contracts:
- Registry Agreements with each gTLD registry operator, such as Verisign for
.com. These set technical, service-level, and policy obligations. - The Registrar Accreditation Agreement (RAA) with every accredited registrar. It sets rules on contact data accuracy, email verification, renewal reminders, data escrow, and handling abuse reports.
Registrars that break the RAA can be investigated by ICANN Contractual Compliance and, in serious cases, lose their accreditation. Read more about the retail side in what a domain registrar is.
Sets Domain Policies
Many rules you meet as a domain owner come from ICANN consensus policies for generic TLDs:
| Policy | What it covers |
|---|---|
| Transfer Policy | How domains move between registrars and registrants, including auth codes and transfer locks |
| Expired Registration Recovery Policy (ERRP) | Renewal reminders and the chance to renew after expiry |
| Uniform Domain-Name Dispute-Resolution Policy (UDRP) | Resolving cybersquatting claims by trademark holders |
| Registration Data Policy | What registration data is collected, published, and redacted |
| Registration Data Access Protocol (RDAP) requirements | How registration data is published in a structured format |
Some examples of how these affect you:
- Transfers: The Transfer Policy is why you need an auth code, why transfers can be blocked for a period after registration or a previous transfer (typically 60 days, being shortened to 30 under ICANN's updated Transfer Policy), and why transfers auto-approve after five days if the losing registrar doesn't respond. See how to transfer a domain to another registrar.
- Expiry: The ERRP requires registrars to send renewal reminders before expiry and to give you a chance to recover the domain afterwards. See what happens when a domain expires.
- Registration data: ICANN's requirements on registration data and privacy, along with laws such as the GDPR, are why most personal contact details are now redacted. In January 2025, the obligation for gTLD registries and registrars to run port 43 WHOIS ended, and RDAP became the standard. See what RDAP is.
Funds Its Work Through Fees
ICANN is funded mainly by fees paid by gTLD registries and registrars. Part of this is a small per-domain-year transaction fee, currently around 20 cents for most gTLDs, which is usually built into the price you pay for registrations, renewals, and transfers. Registries and registrars also pay fixed fees under their contracts.
What ICANN Doesn't Do
ICANN's role is narrower than many people assume. It doesn't:
- Sell domains: You register domains through registrars, not ICANN.
- Set retail prices: Registrars set their own prices. Some registry agreements include pricing provisions, but ICANN doesn't control what your registrar charges.
- Host websites or run DNS for your domain: That's your host and DNS provider.
- Control content: ICANN doesn't regulate what's published on websites. Content complaints usually go to the host, the registrar's abuse team, or law enforcement.
- Govern most ccTLDs: Country-code registries set their own rules. A
.ukdispute follows Nominet's policies, not the UDRP, unless the registry has adopted it. - Resolve individual customer disputes: ICANN Compliance can act when a registrar breaches its contract, but it's not a customer service desk for billing or support problems.
How ICANN Affects You as a Domain Owner
In practice, you'll feel ICANN's influence in a few places:
- At registration: Your registrar must verify your email address and collect accurate contact details for generic TLDs. See how to register a domain name step by step.
- When changing details: Some contact changes can trigger transfer restrictions, depending on the registrar and policy version. See how to change the registrant contact details for your domain.
- When transferring: Auth codes, lock periods, and the extra year added to most gTLD transfers all come from ICANN policy.
- When renewing: Renewal reminders and post-expiry recovery options come from the ERRP.
- In disputes: If someone registers a domain that infringes your trademark, the UDRP offers a faster alternative to court.
When to Contact ICANN Compliance
If your registrar refuses to provide an auth code, won't process a legitimate transfer, fails to send required renewal notices, or ignores other RAA obligations, you can file a complaint with ICANN Contractual Compliance through ICANN's website. Try to resolve the issue with the registrar first and keep records of your communications. Compliance only covers gTLDs and ICANN-accredited registrars, so ccTLD problems go to the relevant registry.
FAQ: ICANN
ICANN stands for the Internet Corporation for Assigned Names and Numbers. It's a non-profit organisation founded in 1998 that coordinates the internet's domain names, IP address allocation and protocol parameters.
No. ICANN coordinates a small but essential set of identifiers, mainly the root of the DNS and policies for generic TLDs. Networks, servers, websites and most infrastructure are run by thousands of independent organisations.
No. ICANN doesn't sell domains to the public. You register domains through an ICANN-accredited registrar or one of its resellers.
No. ICANN is a non-profit organisation based in California. The US government's oversight role over the IANA functions ended in 2016, when stewardship passed to ICANN's global multistakeholder community.
Not their day-to-day rules. ICANN, through the IANA functions, manages their entries in the root zone, but each ccTLD registry sets its own registration, transfer and dispute policies.
Use the complaint forms on ICANN's Contractual Compliance pages. It handles breaches of ICANN agreements by accredited registrars and gTLD registries, such as refusing transfers or failing to send renewal reminders.
It's a small per-domain-year fee, currently around 20 cents for most gTLDs, paid by registrars to ICANN. Many registrars include it in the price, while some list it separately at checkout.
Conclusion
ICANN is the non-profit that coordinates the internet's naming and numbering systems. Through the IANA functions, it maintains the root zone that lists every TLD, and through its contracts with registries and registrars, it sets the rules for generic domains: how they're registered, transferred, renewed, and disputed, and how their registration data is published.
You won't usually deal with ICANN directly, but knowing what it does helps you understand why your registrar asks for email verification, why transfers have lock periods, and where to go if a registrar breaks the rules. Just remember its limits: ICANN doesn't sell domains, control content, or run most country-code extensions, so many day-to-day questions are best answered by your registrar or the relevant registry.
