Transferring a domain between registrars is the kind of task you only do every few years — long enough to forget exactly what bites you. And the things that bite are not the ICANN steps you'll find in any registrar's help center. They're the sequence-of-operations details: when to lower your TTL, when to copy your DNS records, when to actually pull the trigger on the transfer, and what to do if your email goes dark for an hour.
Done correctly, a domain transfer is invisible. Your site keeps serving traffic, your email keeps flowing, your search rankings don't budge, and nine days later the only evidence is a slightly cheaper renewal price on your new registrar's dashboard. Done sloppily, you spend a weekend on the phone with two support teams while your contact form bounces every submission.
This guide is the playbook for the first scenario. It's written for a single domain that's actively in production — running a website, MX records, maybe a CDN, maybe a Google Workspace setup. The same sequence works for a portfolio of domains; you just run it once per name.
A domain transfer changes the registrar — the company that ICANN-recognizes as the sponsor of your registration. It does not, by itself, change anything about how your domain resolves. The transfer can leave your DNS, your website, and your email exactly where they were the day before. That's the secret to zero downtime: you separate the registrar change from any DNS change, and you do them in the right order.
Three concepts get conflated and matter to keep straight:
You can transfer the registrar without touching the other two. You usually should.
Most transfer disasters happen because someone discovers a blocker mid-flight. Run through this list a week before you want to pull the trigger.
ICANN imposes a 60-day transfer lock after any of: initial registration, a previous transfer, or a change of the registrant contact info. If you updated your WHOIS name or email recently, you're stuck for 60 days. Check your current registrar's dashboard — there's almost always a "transfer status" field that tells you the exact date you become eligible.
The transfer authorization email goes to the registrant contact on file. If that's an old Gmail you can't access, the transfer will silently stall. Verify you can receive mail at that address. If WHOIS privacy is on, your registrar may forward; some don't — temporarily disable privacy if you can't confirm forwarding works.
Every gTLD transfer requires an EPP authorization code — a one-time string generated by the losing registrar. Grab it from the current registrar's domain settings now, so you're not hunting for the right menu under time pressure. Treat it like a password: don't email it to yourself in plaintext if you can avoid it.
Every registrar defaults to "registrar lock" (also called clientTransferProhibited). Turn this off. It propagates instantly in WHOIS but some registrars take a few minutes to reflect.
This is the step everyone skips and everyone regrets. Export the full zone file from your current DNS host — every A, AAAA, CNAME, MX, TXT, and CAA record. Take a screenshot if there's no export. You'll need this to rebuild the zone if you choose to migrate DNS as part of the move (and even if you don't, you want a backup).
This is the timeline that produces zero observable downtime. The trick is moving DNS hosting before the registrar transfer — or leaving it where it is — so the registrar change itself becomes a non-event.
| When | Action | Why |
|---|---|---|
| T-7 days | Lower TTL on all DNS records to 300 seconds (5 min) | Old TTLs (often 3600+ or 86400) determine how long stale records can live in resolvers worldwide. Lowering early means any later change propagates in minutes. |
| T-3 days | (Optional) Copy your zone to your new DNS host. Don't change nameservers yet. | Pre-stage the new zone so the cutover is just a nameserver swap, not a rebuild. |
| T-0 (transfer day) | At the gaining registrar: paste the EPP code, initiate transfer. Approve the email when it arrives. | The transfer itself is registrar-to-registrar; your nameservers and zone are unaffected. |
| T-0 to T+7 | Wait for transfer to complete (typically 5-7 days for .com; can be instant if both registrars use the IRTP fast-track). | ICANN's 5-day window lets the losing registrar contest. You can usually accept early from the losing side's dashboard. |
| T+8 (optional) | If you pre-staged the new DNS host: change nameservers at the new registrar. | With TTL at 300s, the swap is fully propagated in under 10 minutes. |
| T+9 | Raise TTL back to 3600+ once you're stable. | Lower DNS query load on your resolver. |
Notice what's not in that sequence: any moment where your nameservers stop serving the right records. The transfer of registrar sponsorship is independent of nameserver delegation. As long as your nameservers are configured correctly, the gaining registrar will respect them by default.
If you're already migrating, it's a good moment to ask whether this is still the right name. Generate 60+ alternatives in seconds and see what's actually available before you commit another year of renewals.
Try the Domain Name Generator free →Once you've initiated the transfer, leave nameservers alone for 5-7 days. Mid-transfer, both registrars may have inconsistent views of who's authoritative, and some DNS hosts decline to serve records for domains they don't see as "current." If you absolutely must change nameservers, do it before the transfer initiates or after it completes — never during.
Many registrars bundle a "free DNS hosting" offer with the transfer. If you accept it without thinking, your nameservers may be silently flipped to the new registrar's defaults — and your records, if not pre-staged, may not exist there. Read the transfer confirmation flow carefully. The safe default is "keep current nameservers, don't change DNS hosting."
If your DMARC policy is p=reject and the transfer notification email comes from a domain that doesn't pass your alignment rules, you'll never see it. Same goes for over-aggressive spam filters on the WHOIS email. Add the gaining registrar's verification domains to an allow-list before T-0.
No — not if you do it correctly. Search engines key off the domain name itself, not the registrar of record. The registrar change is invisible to Google's crawlers because it doesn't alter what nameservers return. The risks that can hurt SEO are downstream effects of a botched transfer:
Each of those is avoidable with the T-7 to T+9 sequence above. If you've already moved hosts mid-transfer and want a sanity check on your current setup, our SEO Meta Tag Generator can rebuild your meta tags from scratch with proper canonicals — useful if the transfer also moved you to a different CMS.
The registrar market in 2026 is roughly three tiers:
If you're moving because the renewal price doubled, the cheap tier wins. If you're moving because you want infrastructure-as-code DNS and integration with your CDN, Cloudflare Registrar is the obvious answer. For a domain you might sell later, Dan.com's integration with most registrars matters less than how easy it is to update WHOIS.
Once transfer completes, run this five-minute check:
dig +short yourdomain.com NS — verify nameservers are what you expectdig +short yourdomain.com — verify the A record returns your origin IPspf=pass dkim=pass dmarc=pass)https://yourdomain.com in an incognito window — confirm the cert is valid and the page loadsIf all five pass, you're done. If any fail, you have a clear, isolated thing to investigate — not a vague "something's broken."
Lower your TTL a week ahead. Get the EPP code and confirm your WHOIS email works. Initiate the transfer; don't touch nameservers during the window. After it completes, run a five-point audit and raise TTL back up. The transfer itself is registrar-to-registrar bookkeeping — the only thing that can break is your DNS, and only if you change it at the wrong moment.
One last thing: a transfer is an excellent moment to revisit whether this is still the right domain. If you've outgrown the name, or it's longer than you'd like, or you're paying a premium renewal on something you'd rather replace, this is the cheapest pivot you'll ever do. Spin up 60+ alternatives with our Domain Name Generator first — if nothing better surfaces, you've validated the keeper. If something does, you've just saved yourself another year of paying for a name you didn't love.
Brandable, descriptive, modern — with live availability checks. 100% free, no sign-up.
Try it free →