What Is ICANN and What Does It Do?

For a domain owner, ICANN shows up in four places: the transfer lock on a new name, the WHOIS verification email, the expiry timeline, and the dispute policy your registrar accepted. This page explains what the organisation actually coordinates, what it stays out of, and which of its rules reach a registration bought in India — including the .in exception.

What ICANN Is (Plain Language)

ICANN is the Internet Corporation for Assigned Names and Numbers: a nonprofit, public-benefit corporation incorporated in California on 30 September 1998. It was created to take over the IANA functions that Jon Postel had been running informally at USC’s Information Sciences Institute, and since 1 October 2016 it has answered to a global multistakeholder community rather than the US Department of Commerce.

In practice its coordination covers three pools of identifiers:

• Domain names — it maintains the DNS root zone through the IANA function: the master list that says which nameservers run each TLD.
• IP addresses — it allocates IPv4 and IPv6 blocks to the five Regional Internet Registries, which pass them on to network providers.
• Protocol parameters — port numbers, protocol identifiers and even the world’s time zone database are coordinated through IANA.

Just as important is what it does not do. ICANN is not a content regulator: it cannot block a website, stop spam or rule on speech. It is not a government — governments advise it through the Governmental Advisory Committee. And it does not sell or operate any domain itself; registries and registrars do that under ICANN’s contracts.

Registries, Registrars, ICANN: Who Does What

Three roles sit between you and a working domain, chained by contracts, and each answers to the next:

You never talk to a registry directly. Your registrar pushes your registration data into the registry’s zone and its nameservers publish it. Domain registration in India works the same way whether the TLD is .com or .in — only the registry behind it changes.

How ICANN Rules Touch Your Domain

ICANN’s contracts reach your own registration through four specific rules:

• WHOIS accuracy duty. Your registrant contact data must be real and current. Registrars must send periodic verification emails, and unconfirmed data can lead to suspension.
• The 60-day transfer lock. After registration or a change of registrant, ICANN’s Transfer Policy blocks moves between registrars for 60 days. If a move is pending, plan the transfer around that window.
• Authorisation code and registrar lock. Every transfer needs the EPP code from your current registrar and the clientTransferProhibited status lifted — that lock is what stops domain hijacks.
• Expiry lifecycle. An expired name runs through a renewal grace period, a paid redemption grace period, a pendingDelete hold, then the drop. Each stage has a deadline you can work to.

WHOIS to RDAP: Why Data Went Private

Public WHOIS used to list the owner’s name, email, phone and address for every domain. GDPR changed that: since 2018 registrars redact personal data by default, and ICANN’s registration-data policy now defines what may be shown and to whom. The lookup layer moved to RDAP, a structured JSON successor to plain-text WHOIS served at lookup.icann.org — the same records, machine-readable and rate-limited.

Privacy does not make the data secret. Registries, registrars, ICANN compliance and lawful requests still see it, and registrars must keep it accurate. To see what the public record says about your own name, run it through our Whois domain lookup.

UDRP: When Domains Get Disputed

UDRP — the Uniform Domain-Name Dispute-Resolution Policy — is how trademark holders challenge a gTLD registration they say infringes their mark. A complainant files with an approved provider such as WIPO, and a panel hears the case.

The panel applies a three-part test: the name is identical or confusingly similar to the mark, the registrant holds no legitimate interest in it, and it was registered and used in bad faith. Outcomes are transfer or cancellation — no damages. A respondent who disagrees can sue in a competent court within ten business days to hold the decision.

One India-specific point: .in is a country-code TLD, so UDRP does not apply to it. The .IN Registry (NIXI) runs its own policy, INDRP, and complaints are decided by an arbitrator appointed under Indian arbitration law. Same idea — bad-faith registration of someone else’s mark — different forum, procedure and fees.

The New gTLD Explosion

The 2012 round of the New gTLD Programme added hundreds of endings at once; today more than 1,200 gTLDs are delegated, alongside 151 internationalised TLDs in 37 languages and 23 scripts — including Devanagari names an Indian buyer can register. A next round is planned for 2026, which will add more.

For buyers this means real choice, with two cautions. Look-alike endings multiply — .app, .dev, .shop, .top — so typosquatting expands with them. And older systems do not always accept newer TLDs; the Universal Acceptance push exists because form fields and email validators still reject valid names. Read what a TLD is before betting a brand on a new ending.

Can You Lose a Domain? (Suspension and UDRP)

Yes — through defined channels, each with procedure:

• Dispute loss. A UDRP or INDRP panel can order your name transferred or cancelled.
• Registrar suspension for abuse. Phishing or malware complaints trigger takedown demands; registrars must act on credible reports with notice, and hacked sites are typically restored once cleaned.
• WHOIS inaccuracy. Unverified or falsified contact data, after notices, can lead to cancellation — answer registrar verification emails.
• Expiry. Not an ICANN process but the commonest loss: grace, redemption (paid), pendingDelete, drop.
• Court order. Trademark and cybersquatting lawsuits can compel transfer.

What protects you is boring and effective: accurate registrant data, the transfer lock left on, auto-renewal, and a registrar that actually answers. The registration layer manages exactly these statuses for every name it handles.