Domain transfer checklist

A registrar transfer changes who manages the domain registration; it does not need to move the website, email or DNS hosting. Before requesting the transfer, confirm the registrant can receive approval messages, record every DNS setting, check registry-specific eligibility and keep the domain renewed. After completion, verify ownership, nameservers, DNSSEC and renewal settings.

Scope and limitations

This checklist describes a typical transfer between registrars. Transfer rules, locks, authorization methods, costs and timing vary by top-level domain, registry and registrar. ICANN policy principally applies to covered generic top-level domains; country-code domains can follow different registry rules.

Do not publish an authorization code or place it in a shared ticket. A registrar transfer is not the same as changing the registrant, nameservers or web host, although a provider workflow may offer those actions together.

Phased domain transfer checklist

1. Confirm control and eligibility

Verify the exact domain, current registrar, registered holder and authoritative registry rules.
Confirm access to the registrant account and the email or approval method used for transfer notices.
Check expiry, renewal, recent registration or transfer dates and any dispute or lock that can block transfer.
Avoid an unnecessary registrant-contact change immediately before transfer because some policies can trigger a lock.
Enable strong account security and record who is authorised to approve the transfer.

2. Preserve DNS and service continuity

Export or document all authoritative DNS records, including less visible TXT, MX, CAA and verification records.
Record current nameservers, DNSSEC state, TTL values and which provider actually hosts the zone.
Confirm that the existing DNS service will remain active during and after registrar transfer.
Do not change registrar, nameservers, web hosting and email routing simultaneously unless the combined change has its own tested plan.
Check website and mail from independent networks before starting.

3. Authorise and track the transfer

Unlock the domain only when ready and request the required authorization code through the registrar's secure workflow.
Start the transfer with the intended gaining registrar and review the domain and account before confirming.
Respond to legitimate approval messages within the stated window and verify their origin rather than following unexpected links.
Keep a timestamped record of requests and confirmations without storing secrets in the record.
Leave DNS records unchanged while the registrar transfer is pending unless a separate incident requires action.

4. Verify after completion

Confirm the gaining registrar now shows the correct domain and registrant control.
Verify nameservers, DNS records, DNSSEC delegation, website, TLS and email delivery from outside the local network.
Review the new renewal date, auto-renewal preference, payment method and expiry contacts.
Re-lock the domain when operational work is complete and retain strong account authentication.
Remove obsolete registrar access only after all records and invoices needed for administration are retained.

Domain transfer FAQ

Will transferring a domain move the website?

Normally no. A registrar transfer changes registration management. The website and email continue to depend on nameservers and DNS records, which is why those settings must be documented and verified.

Why can a transfer be blocked?

Possible reasons include registry or registrar locks, recent registration or transfer, a recent registrant change, expiry state, disputes, unpaid obligations allowed by policy or inability to confirm the request. The applicable registry and registrar rules decide the case.

Should nameservers be changed during transfer?

Usually it is safer to leave them unchanged and make a DNS move separately. Combining changes increases the number of failure points and makes an outage harder to diagnose.