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

If you want to transfer your domain to a cheaper or saner registrar, the honest answer is that it takes about five minutes of clicking and 2 to 5 days of waiting. Unlock the domain, grab the authorization code, pay the new registrar, approve one email. That’s the whole job. People botch it because nobody tells them about the 60-day lock, the renamed transfer code, or the two or three gotchas that quietly lock you out of your own domain halfway through.

So here’s the verdict up front. For most people in 2026, the right move is to transfer a domain name to Cloudflare Registrar (at-cost, around $10.44/yr for a .com) or Namecheap if you want a friendlier dashboard and real support. Avoid GoDaddy renewals and the old Google Domains inventory that moved to Squarespace. The domain transfer process itself is standardized by ICANN, so the registrar barely matters for the mechanics. What matters is timing it so you don’t trip the lock.

What I’m working from: I’ve registered and moved domains across GoDaddy, Namecheap, Cloudflare, Porkbun, and BigRock over 18 years and roughly 90 client brands. I’ve watched a Google Workspace mailbox go dark because someone changed nameservers mid-transfer, and I’ve waited out the 60-day lock more times than I’d like. The steps below are the exact ones I run, in order, every time.

What changed in 2026: The thing registrars used to call the “EPP code” or “auth code” is now standardized as the TAC (Transfer Authorization Code) across the industry. It’s the same string, just one consistent name now, so don’t panic if your registrar’s dashboard says “TAC” instead of “EPP code”. ICANN’s transfer policy also confirms the 60-day lock now triggers on a change of registrant name, organization, or email, not just on registration and prior transfers. Source: ICANN Transfer Policy and Namesilo’s 2026 transfer-rules breakdown.

Why transfer your domain in the first place?

Most domain transfers come down to money, security defaults, or sanity. If you grabbed a domain on a cheap first-year promo, the renewal is almost always where the registrar makes it back. Here are the five reasons that actually justify a move.

• Pricing. The registrar that gave you the cheap first-year deal is likely overcharging on renewal. Cloudflare Registrar charges at-cost (about $10.44/yr for a .com, including the $0.18 ICANN fee), while a GoDaddy .com renewal runs $20 to $22.
• Better security defaults. Mature registrars (Cloudflare, Namecheap, Porkbun) ship with WHOIS privacy free, DNSSEC support, and domain locking on by default. GoDaddy still charges roughly $10/yr extra for privacy.
• Better DNS management. Cloudflare’s DNS interface is faster and cleaner than GoDaddy’s by every measure. If you spend any real time in DNS, the time saved adds up fast.
• Consolidating registrars. Managing 12 domains across 5 registrars is administrative chaos. Pull everything onto one or two registrars with consistent pricing and auto-renew.
• Removing upsells. Some registrars lean hard on cross-sells, pre-checked boxes, and renewal traps. Moving to a registrar that doesn’t do that is worth something on its own.

If you’re still deciding where a new project should live, my breakdown of the real costs of free web hosting covers why the “free” registrar or host is rarely free once renewals hit.

When you should NOT transfer (and who should wait)

A transfer is the wrong move more often than people think. Don’t start one if any of these apply to you, because you’ll either fail the request or risk losing the domain.

• The domain is under 60 days old, or you just transferred it. ICANN’s 60-day lock blocks you flat. There’s no override. Register at your preferred registrar from the start if you can.
• You changed the registrant name, org, or email in the last 60 days. In 2026 this also trips the lock. If you updated WHOIS contact details recently, wait it out.
• The domain expires in under 30 days. Most registrars block transfers near expiry. Renew first (the year carries over to the new registrar), then transfer.
• It’s mission-critical email and you can’t risk a cutover. If a Google Workspace or Microsoft 365 mailbox lives on this domain and you’re nervous about MX records, plan the DNS side carefully before you touch the registrar.
• You only want Cloudflare DNS but not its registrar limits. Cloudflare Registrar requires you to use Cloudflare’s nameservers. If you need Route 53 or another DNS provider, Cloudflare Registrar isn’t for you. Pick Porkbun or Namecheap instead.

Best domain registrar to transfer to in 2026

Here’s how the mainstream registrars stack up on .com pricing, privacy, and who each one actually suits. Prices are 2026 renewal rates, which is the number that matters once the promo year is gone.

Registrar	.com price/yr	WHOIS privacy	Best for
Cloudflare Registrar	~$10.44 (at cost)	Free, default	Most users; requires Cloudflare DNS
Porkbun	~$11.06	Free, default	Power users wanting a better UI than Cloudflare
Namecheap	~$13.98	Free, default	Established option, strong support
Namesilo	~$10.95	Free, default	Cheapest mainstream option, plainer UI
Google Domains (now Squarespace)	$12 to $20	Included	Avoid. Moved to Squarespace, prices rose
GoDaddy	$20 to $22	$10/yr extra	Avoid. Aggressive upsells, costly renewals
BigRock (India)	₹800 to ₹1,200	Free	Indian users; ResellerClub-backed

My default in 2026: Cloudflare Registrar for any domain I’m not actively reselling, Porkbun for portfolios where the dashboard matters, and Namecheap when I want hand-holding support and free privacy without the Cloudflare nameserver lock-in. All three ship with the security defaults GoDaddy charges extra for. If you want the long version with screenshots, see my full guide to the best domain registrars.

The exact step-by-step transfer process

This is the move domain registrar checklist I run every time, in order. Skip a step and the request usually fails silently, so do them top to bottom.

1. Confirm domain age. ICANN rules: the domain must be at least 60 days old since registration or its last transfer, with no registrant-info change in that window. If it’s newer, you can’t transfer yet.
2. Disable WHOIS privacy at the current registrar. Some registrars block transfers while WHOIS is privatized. Re-enable it after the transfer completes.
3. Unlock the domain at the current registrar. Flip the “domain lock” or “transfer lock” toggle off. Without this, the request fails.
4. Get the EPP code (now called the TAC). Your current registrar emails it or shows it in the control panel. It’s case-sensitive and expires after use. ICANN bars registrars from withholding it from a legitimate owner.
5. Initiate the transfer at the new registrar. Add the domain to your cart, paste the TAC/EPP code, and pay (typically $10 to $15, which adds one year to the registration).
6. Approve the email confirmation. The new registrar emails the WHOIS contact (you, if privacy is off) for approval. Click the link.
7. Wait 2 to 5 days. The ICANN transfer window. During it, you can usually cancel if something looks wrong.
8. Verify DNS is intact. Most transfers preserve DNS records, but some registrars wipe them. Confirm nameservers and records are correct once it lands.

Seven gotchas that cause failed transfers

Nearly every failed transfer I’ve seen traces back to one of these. Check them before you start the clock, not after.

• 1. Recently registered or transferred domain. The 60-day waiting period applies. Plan ahead if you’ve just registered.
• 2. Recent registrant-info change. Changing the registrant name, org, or email also starts a fresh 60-day lock in 2026. Update WHOIS, then wait, then transfer.
• 3. Expired or near-expired domain. Most registrars block transfers within 30 days of expiration. Renew first, then transfer. The renewal year carries over.
• 4. WHOIS contact email out of date. The approval email goes to the WHOIS admin. Wrong email, no approval. Fix WHOIS first.
• 5. Domain lock not removed. Easy to forget; the request fails silently.
• 6. Wrong or stale EPP/TAC code. Some registrars regenerate codes. Use the most recent one, and remember it’s case-sensitive.
• 7. Cloudflare nameserver assumption. Moving the registrar doesn’t move your DNS provider. And if you transfer into Cloudflare Registrar, you must use Cloudflare’s nameservers. Plan the DNS move as a separate, deliberate step.

DNS and email continuity during transfer

The transfer itself usually doesn’t disrupt DNS or email. The real risk is configuration drift: you change DNS at the wrong moment, or the new registrar doesn’t import your existing records cleanly. If your site is already fighting load times, my notes on why a WordPress site is slow and how to fix it cover the DNS and caching side worth checking after a move.

• Document existing DNS records before transfer. Screenshot or export every record (A, AAAA, CNAME, MX, TXT, SRV) at the source registrar first.
• If you’re keeping the same DNS provider, the transfer touches only the registrar relationship. DNS stays put. This is the lowest-risk path.
• If you’re changing DNS provider, set up the new DNS with every record imported, verify it resolves, then change nameservers. The cutover is the only window where DNS can break.
• For email, confirm MX records survive. If Google Workspace or Microsoft 365 email runs on the domain, MX misconfiguration during a transfer is the number one way to take corporate email down.

Post-transfer cleanup

The transfer landing in your new account isn’t the finish line. Run this short cleanup so the domain is locked down and won’t surprise you at renewal.

• Re-enable WHOIS privacy if you turned it off for the transfer.
• Re-enable the domain lock at the new registrar.
• Turn on 2FA for the new registrar account. Domain accounts are high-value targets, so 2FA is non-negotiable.
• Set the registration to auto-renew. Domains that lapse for 30-plus days can fall to opportunistic squatters.
• Update WHOIS contact info if your details have changed since registration.
• Close the old registrar account if you have no other domains there, so the renewal and upsell emails stop.

For broader site setup once the domain is settled, see my SEO-friendly WordPress setup guide and, if you run a store, my pick of the best WooCommerce hosting to point the freshly moved domain at.

Frequently asked questions

Disclaimer: This site is reader-supported. If you buy through some links, I may earn a small commission at no extra cost to you. I only recommend tools I trust and would use myself. Your support helps keep gauravtiwari.org free and focused on real-world advice. Thanks. - Gaurav Tiwari