How Domain Transfers Work

People use "transfer" for several different operations. Clarifying which one is intended avoids a common handover mistake: moving the registration while assuming that hosting and email moved with it.

Identify the operation

An inter-registrar transfer changes the sponsoring registrar. A change of registrant changes the registration holder. An account move may keep the domain at the same registrar. A website migration moves files or an application. These operations can be related but are not interchangeable.

Ask the registrar to describe the applicable sequence for this domain and extension. Eligibility, authorization and lock conditions can differ. The ICANN Transfer Policy is a starting point for covered generic domains, not a universal instruction for every country-code extension.

Preserve services during the handover

Export or otherwise document the DNS zone before altering nameservers. Inventory web addresses, mail routing, verification records and any subdomains used by business tools. Do not rely only on the visible homepage: a working website does not demonstrate that invoice delivery or account-recovery email still works.

A receiving account should be ready before the transaction starts. Secure it with a recovery address that will not disappear when the domain changes hands.

Verify completion through more than one signal

Check the domain in the destination account, then compare public registrar and nameserver data with the agreed plan. Public records may update on a different schedule from an account interface; neither an old cached lookup nor a single screenshot should settle a disputed handover.

Document who will renew the name and who retains access to hosting, DNS and email services after the transaction. Remove former access only after the authorized handover is confirmed.

Use DNS Lookup for individual public records and Domain Lookup for registration data. Neither tool initiates or authorizes a transfer.

Maintained by WebOneWord Team. Last reviewed: 2026-10-07.