What Is ICANN? What It Does, and Why the 60-Day Rule Exists

Published October 19, 2026

Every few years, domain owners discover ICANN exists — usually when a transfer is blocked, a domain is locked for 60 days, or a registrar does something outrageous and people ask “who regulates this?” Here’s the honest version of what ICANN is, what it can and can’t do for you, and why its rules are shaped the way they are.

What ICANN actually is

ICANN (Internet Corporation for Assigned Names and Numbers) is a California nonprofit that coordinates the internet’s naming system. It doesn’t own the internet and it doesn’t host anything. Its job is narrower: it manages the root zone (the master list that maps top-level domains like .com to their registries), accredits registrars, and writes the policies registrars must follow.

Think of it as the rulebook author and referee — not a player. When you register example.com at Porkbun, the chain is: you → registrar (Porkbun) → registry (Verisign, for .com) → root zone (coordinated by ICANN). ICANN sets the rules for the registrar-to-registry relationship, including how transfers work.

It’s funded mostly by fees on domain registrations — a small slice of every .com registration flows to ICANN. That funding model is worth knowing: ICANN’s budget grows when domain sales grow.

What ICANN controls that affects you

The 60-day transfer lock

You can’t transfer a domain within 60 days of registering it, or within 60 days of a previous transfer. This is ICANN’s Transfer Policy, and it applies at every accredited registrar — no exceptions, no workarounds.

Why it exists: the rule was written to fight domain theft and fraud. Stolen domains used to be bounced between registrars quickly to cover tracks; the 60-day window gives the original owner time to notice and recover. It also cools down impulse transfers made under social-engineering pressure.

The cost: it’s genuinely annoying in legitimate cases. Bought a domain at a bad registrar and want out immediately? You’re waiting 60 days. There’s no appeal process — the registry enforces it mechanically.

A related lock: changing the registrant contact details (name, email, organization) historically triggered another 60-day lock. ICANN updated this policy to let registrars offer an opt-out, so many registrars now let you confirm the change and skip the lock — but not all do. Check before updating contact details if a transfer is on your horizon.

The 5-day transfer waiting period

When you transfer a domain between registrars, the losing registrar has 5 days to release it. If they do nothing, the transfer auto-completes. If you approve the confirmation email promptly, most registrars release it in a day or two.

Why it exists: it’s a cooling-off period — a last chance to catch an unauthorized transfer. The confirmation email to the registrant is the actual security mechanism; the 5 days are the backstop.

Expired-domain protections

ICANN’s Expired Registration Recovery Policy requires registrars to send renewal reminders — typically around 30 days and 7 days before expiry, plus one notice shortly after expiry. Registrars must also clearly state their post-expiry policies: what happens to your domain, and what it costs to get it back.

This policy exists because registrars used to quietly auction expired domains without telling the owner. Now they have to tell you — though “tell you” means an email to the registrant contact, so keep that address current.

The UDRP (dispute resolution)

If someone registers a domain infringing your trademark, ICANN’s Uniform Domain-Name Dispute-Resolution Policy is the standard remedy. You file with an approved provider, a panelist decides, and the domain is transferred or cancelled. Filing costs start around $1,500 for a single panelist — cheaper than a lawsuit, but not cheap.

The UDRP only covers clear cybersquatting (bad-faith registration of someone else’s mark). It doesn’t settle legitimate disputes between two parties with plausible claims to a name.

What ICANN doesn’t do

This is the part that surprises people:

• It doesn’t set prices. Registry operators (like Verisign for .com) have price caps in their ICANN contracts, but registrars charge whatever they want. Nothing stops a registrar tripling renewal prices.
• It doesn’t police registrar business practices beyond the letter of its policies. Aggressive upsells, confusing checkout flows, terrible support — all fine as far as ICANN is concerned.
• It can’t reverse a registrar’s account action quickly. When a registrar suspends or seizes domains — as in the October 2026 Namecheap seizure — ICANN’s compliance process moves in weeks and months, not hours. Your sites are down now; the process is later.
• It doesn’t guarantee your registrar stays in business. If a registrar fails, ICANN has a transition process to move domains to another accredited registrar, but it’s disorderly by nature.

A brief history (why it looks like this)

ICANN was created in 1998 to take over domain-name coordination from the US government — before that, one man (Jon Postel at USC) effectively ran the DNS root on a government contract. The 2016 “IANA transition” completed the handover, moving the root-zone management contract from the US Commerce Department to ICANN’s affiliate.

This history explains ICANN’s odd shape: it’s a California nonprofit doing global governance, funded by domain fees, accountable to a multi-stakeholder community of governments, businesses, and civil society. It’s not a regulator in the traditional sense — nobody elected it — but it’s the only body all the registries and registrars contractually answer to.

The 2012 “new gTLD” round — which created .app, .dev, .blog, and over a thousand others — was ICANN’s biggest expansion of the namespace. Whether that was good for users or just good for ICANN’s fee revenue is still debated.

Country-code domains: the ICANN-free zone

Everything above applies to generic TLDs (.com, .net, .org, new gTLDs). Country-code domains (.de, .uk, .ca, .io) are run by national registries under their own rules — ICANN coordinates them technically but doesn’t set their transfer or dispute policies.

This matters because ccTLD rules vary wildly: some have no transfer locks at all, some require local presence, some have idiosyncratic dispute processes. If you hold ccTLDs, learn that registry’s rules separately — the ICANN playbook doesn’t apply.

Filing a complaint against your registrar

If your registrar violates ICANN policy — ignores a transfer request, withholds an auth code, skips required renewal notices — you can file a complaint with ICANN Contractual Compliance. It’s a real process with real outcomes (registrars have lost accreditation), but it’s slow: weeks to months, not days.

Practical advice: complain to the registrar first, in writing, citing the specific policy. Escalate to ICANN if they stonewall. And for anything time-sensitive — a domain about to expire, a hijacking in progress — don’t wait for the process. Act through the registrar’s support channels and, if needed, move the domain the moment policy allows.

ICANN and you: the practical takeaways

You don’t need to love ICANN or even think about it most days. But three things are worth internalizing:

1. The 60-day rule is absolute. Plan transfers around it — don’t buy a domain at a bad registrar expecting to flip it immediately.
2. Keep your registrant email alive. Renewal notices, transfer approvals, and UDRP notifications all go there. A dead email address silently disables every protection ICANN built for you.
3. The policies are floors, not ceilings. ICANN sets minimum protections; good registrars exceed them (longer grace periods, clearer notices, saner redemption fees). Registrar choice is where the real protection lives.

The honest assessment

ICANN’s transfer and expiry rules are genuinely protective — the 60-day lock, the 5-day window, the renewal reminders all exist because of real abuse. But ICANN is a policy body, not a consumer protection agency. It writes the rules of the game; it doesn’t ensure the players treat you well.

That’s why registrar choice matters more than ICANN policy. The rules are the same everywhere — the difference is whether your registrar follows the spirit or just the letter. Our registrar comparison and best registrars for small business cover who’s who.