How to Transfer a Domain Name (Step-by-Step + Best Registrar in 2026)

Domain transfers should take 5 minutes of work and 2–5 days of waiting. The process has been the same since the late 1990s: unlock at current registrar, get an EPP transfer code, pay the new registrar, approve the transfer email. Most people botch it because they don’t understand which registrars are worth moving to and which gotchas can lock them out of their own domain mid-transfer.

This guide walks through the exact domain transfer process for moving between registrars in 2026. The registrars I’d actually recommend (and the ones to leave), the seven gotchas that cause failed transfers, and how to handle email/DNS continuity so your site doesn’t go dark during the transfer window.

Why transfer your domain in the first place?

• Pricing. The registrar that gave you the cheap first-year deal is likely overcharging on renewal. Cloudflare Registrar charges at-cost (~$10/yr for .com); GoDaddy renewal is $20–$22.
• Better security defaults. Mature registrars (Cloudflare, Namecheap, Porkbun) ship with WHOIS privacy free, DNSSEC support, and domain locking enabled by default.
• Better DNS management. Cloudflare’s DNS interface is faster and better than GoDaddy’s by every measure. If you spend any time in DNS, the time saved adds up.
• Consolidating registrars. Managing 12 domains across 5 registrars is administrative chaos. Consolidate to one or two registrars with auto-renewal and consistent pricing.
• Removing upsells. Some registrars (looking at you, GoDaddy) have aggressive cross-sells, hidden checkboxes, and renewal traps. The peace of mind of moving to a non-aggressive registrar is real.

Best registrars to transfer to in 2026

My default in 2026: Cloudflare Registrar for any domain I’m not actively reselling, Porkbun for portfolios where the UI matters. Both ship with security defaults that GoDaddy charges extra for.

The exact step-by-step transfer process

1. Confirm domain age. ICANN rules: domain must be at least 60 days old since registration or last transfer. If it’s newer, you cannot transfer.
2. Disable WHOIS privacy at the current registrar. Some registrars block transfers if WHOIS is privatized. Re-enable after transfer completes.
3. Unlock the domain at the current registrar. “Domain lock” or “transfer lock” toggle. Without this, the transfer request will fail.
4. Get the EPP / authorization code. Sometimes called “authorization code” or “transfer code”. The current registrar will email it or display it in the control panel.
5. Initiate the transfer at the new registrar. Add the domain to your cart, paste the EPP code, pay (typically $9–$15 which adds 1 year to the registration).
6. Approve the email confirmation. The new registrar emails the WHOIS contact (you, if WHOIS is unprivatized) for approval. Click the link.
7. Wait 2–5 days. ICANN-mandated transfer window. During this time, you can typically cancel the transfer if needed.
8. Verify DNS is intact. Most transfers preserve DNS records. Some registrars wipe DNS during transfer; verify post-transfer that nameservers and records are correct.

Seven gotchas that cause failed transfers

• 1. Recently registered or recently transferred domain. 60-day waiting period applies. Plan ahead if you’ve just registered.
• 2. Expired or near-expired domain. Most registrars block transfers within 30 days of expiration. Renew first, then transfer (the renewal year carries over).
• 3. WHOIS contact email out of date. The transfer approval email goes to the WHOIS admin. If it’s an old or wrong email, you can’t approve. Update WHOIS first, then transfer.
• 4. Domain lock not removed. Easy to forget; the transfer request will silently fail.
• 5. Wrong EPP code. Some registrars regenerate codes; use the most recent one. Code is case-sensitive.
• 6. Pending registrar dispute. If you have an open ticket or dispute with the current registrar, transfers are blocked until it resolves.
• 7. DNS migration assumption. Transferring the registrar doesn’t move the DNS provider. If you used GoDaddy’s DNS and transfer to Cloudflare Registrar, you’ll likely want to also move DNS to Cloudflare’s nameservers (separate step).

DNS and email continuity during transfer

The transfer itself usually doesn’t disrupt DNS or email. The risk is configuration drift — either you change DNS at the wrong time, or the new registrar doesn’t import existing records correctly.

• Document existing DNS records before transfer. Screenshot or export every record (A, AAAA, CNAME, MX, TXT, SRV) at the source registrar.
• If keeping the same DNS provider: the transfer affects only the registrar relationship; DNS stays where it is. Lowest-risk path.
• If changing DNS provider: set up the new DNS first with all records imported, verify it works, then change nameservers. The cutover is the only window where DNS could be misconfigured.
• For email: verify MX records survive the transfer. If you use Google Workspace or Microsoft 365 email on the domain, MX misconfiguration during transfer is the #1 way to take down corporate email.

Post-transfer cleanup

• Re-enable WHOIS privacy if you disabled it for the transfer.
• Re-enable domain lock at the new registrar.
• Enable 2FA on the new registrar account. Domain accounts are high-value targets; 2FA is non-negotiable.
• Set the registration to auto-renew. Domains that lapse for 30+ days can become available for opportunistic squatters.
• Update WHOIS contact info if your details have changed since registration.
• Cancel the old registrar account if you have no other domains there. Otherwise you may continue receiving renewal/upsell emails.

For broader site setup context, see my integrated web security plan and essential tests for new websites.

Frequently asked questions