What Is ICANN and What Does It Do?

ICANN is the Internet Corporation for Assigned Names and Numbers, a nonprofit formed in 1998 to coordinate the internet's unique identifier systems. Its work connects domain-name policy, the DNS root and identifier administration so independent networks can use a common naming system.

A domain ending such as .com must have an agreed place in that system, with authoritative nameservers identified at the root. Without coordinated identifiers, the same address could mean different destinations to different networks. The DNS guide explains how that coordination becomes a lookup when a visitor opens a website.

ICANN is not the owner of every website or a general internet government. It does not sell ordinary registrations to site owners, write your website or decide whether an article is true. Its contractual authority is distinct from the authority of courts, governments, hosting companies and registry operators.

• Names: coordination of the DNS root and domain-name policy.
• Numbers: global coordination of address resources through the regional registry system.
• Protocol parameters: identifier administration through the IANA functions, not control over the applications using those identifiers.

ICANN's gTLD transfer framework covers moving a registration between registrars, including authorisation and circumstances that can block a transfer. It is separate from moving website files or changing nameservers.

ICANN's transfer FAQs explain that registrars may refuse a transfer within 60 days of initial registration or a previous transfer. A change of registrant can also impose a 60-day inter-registrar lock. Some registrars offer an opt-out before the registrant change, but they are not required to do so.

Changing registrant details merely to prepare a move can therefore delay it. Ask the current registrar about the order of operations before editing the registrant name, organisation or email. The domain authorisation-code guide explains the credential used for applicable transfers; treat it as sensitive.

• Check the extension, registration date and current domain status.
• Confirm you control the registrant contact and account.
• Ask whether a registrant-change lock already applies.
• Plan expiry and transfer timing separately from the website migration.

A transfer lock does not usually prevent pointing the name at another hosting service. Domain transfer describes changing the registration provider, not a prerequisite for every hosting move.

ICANN provides the UDRP framework for applicable domain disputes, but an approved dispute provider and its appointed panel decide individual cases. ICANN itself is not the tribunal for every trademark complaint.

The Uniform Domain-Name Dispute-Resolution Policy addresses complaints based on confusing similarity to a trademark, lack of rights or legitimate interests, and registration and use in bad faith. The policy remedies are transfer or cancellation rather than a damages award. A domain owner should obtain legal advice promptly when a formal complaint arrives.

The applicable policy depends on the extension. .in has NIXI's INDRP rather than simply inheriting the gTLD UDRP procedure. Some other country-code registries adopt different frameworks. The Indian domain dispute guide discusses the practical difference; do not assume a single deadline or fee applies to all TLDs.

Registering an available spelling is not a trademark clearance. Avoid names designed to impersonate another business, and document legitimate use of a name you select.