Our verdict: protect DNS first, then move the registration
A registrar transfer changes who sponsors the domain, not where your mail is delivered. The risk to email comes from DNS. Namecheap's transfer article says a domain transfer does not imply an automatic DNS change, and that if the domain uses the previous registrar's default DNS, that registrar will delete the domain from its DNS zone shortly after the transfer, causing downtime for the website and email [3]. If your nameservers belong to a host or DNS provider, Namecheap says there should be no interruption [3].
We would never start a transfer without a full copy of the zone and a plan for where DNS will live afterward.
Eligibility rules from ICANN
ICANN's Transfer Policy page shows the version updated on 21 February 2024, which registrars had to implement no later than 21 August 2025 [1]. Policy can change, so confirm the current rules with both registrars before you act.
| Rule | What the policy text says | What to do |
|---|---|---|
| New registration | A registrar may deny a transfer requested within 60 days of the creation date [1] | Wait until day 61 or ask the registrar |
| Recent transfer | Denial is allowed within 60 days after a previous transfer [1] | Wait, or keep the current registrar for now |
| Change of Registrant | The registrar must impose a 60-day inter-registrar transfer lock; it may offer an opt-out before the change [1] | Ask about the opt-out before editing owner details |
| Auth code | ICANN's registrant guide says the registrar should provide the AuthInfo code within five calendar days of your request [2] | Request it early and store it privately |
| Registrar of record response | No response within five calendar days to the registry results in default approval [1] | Expect most transfers to finish within about a week |
Step-by-step transfer checklist
- Export or screenshot every DNS record: MX, SPF and other TXT, DKIM, CNAME and A records.
- Decide where DNS will live after the move. If it is at the old registrar's default nameservers, move DNS to the new registrar or a DNS host first, wait for it to work, then transfer.
- Make any urgent DNS edits now. Namecheap says nameservers cannot be updated once a transfer is initiated [3].
- Check eligibility: Namecheap's requirements say the domain must have been registered or transferred at least 60 days ago and be unlocked, with a Whois status of OK or Active [3].
- Make sure the registrant email is current, since transfer notices go there.
- Unlock the domain and request the Auth/EPP code at the current registrar [2] [3].
- Start the transfer at the new registrar and enter the code [3].
- Watch for the release. Namecheap says the old registrar should release within up to 5-7 calendar days [3].
- After completion, confirm the transfer lock is back on and test sending and receiving mail.
Who should transfer, and who should wait
Transfer when renewal pricing, support or consolidation clearly justifies the work and you control DNS. Wait if the domain is within its 60-day windows, if mail runs on the old registrar's default DNS and you have not yet moved it, or if the domain is close to expiring with a registrar that handles expired transfers differently. Namecheap notes separate rules for expired domains [3].
Worked example and pitfalls
Hypothetical example: a consultant's domain uses her old registrar's free DNS, with MX records pointing at a hosted mailbox. She copies all records, recreates them at the new registrar's DNS, switches nameservers, and waits two days while checking that mail still arrives. Only then does she unlock the domain and start the transfer. When the old registrar later deletes its zone, nothing breaks, because no one is using it.
- Starting the transfer before copying DNS records.
- Changing the registrant name or organization right before a transfer, which can trigger the 60-day lock [1].
- Leaving an outdated registrant email, so approval or notice messages go unseen.
- Assuming the extra year applies to every extension; Namecheap says it depends on the TLD [3].
Our decision rule
Move DNS first, transfer second, verify mail third. If you cannot say which nameservers your domain uses today, stop and find out before requesting the auth code.
Questions before you decide
Why can't I transfer my domain yet?
ICANN's Transfer Policy lets a registrar deny a transfer requested within 60 days of the domain's creation date or within 60 days after a previous transfer, and requires a 60-day transfer lock after a Change of Registrant unless the registrar offered an opt-out beforehand.
Does a domain transfer add a year?
Often, but it depends on the extension. Namecheap's transfer article says that, depending on the TLD, the domain will be renewed for one year when the transfer completes. Check the gaining registrar's own terms for your extension.
How long does a transfer take?
Namecheap says the previous registrar should release the domain within up to 5-7 calendar days, and that the transfer is approved automatically if it takes no action. ICANN's policy sets a five calendar day window for the registrar of record to respond.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- ICANN Transfer Policy Accessed 13 Oct 2026
- ICANN: 5 Things Every Domain Name Registrant Should Know About ICANN's Transfer Policy Accessed 13 Oct 2026
- Namecheap Knowledgebase: How do I transfer my existing domain to Namecheap? Accessed 13 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.