How to Transfer a Domain Without Any Downtime
Moving a domain to a new registrar sounds like it should take five minutes. Then you hit a locked domain, a WHOIS privacy email that never arrives, or a 60-day lock you didn't know existed - and now you're worried the site or email will go dark mid-transfer. It won't, if you do the DNS part correctly. Here's the whole process, the failure points, and how to keep everything live the entire time.
The one thing that actually causes downtime
A domain transfer moves ownership and billing from one registrar to another. It does not, by itself, touch your DNS records, your nameservers, your website, or your email. Downtime during a transfer almost always comes from someone changing nameservers or DNS records at the same time as the transfer, not from the transfer itself.
So the rule is simple: leave your nameservers and DNS zone exactly as they are until the transfer is fully complete. If Getwebup is already hosting your site and your nameservers already point to ns1.getwebup.in / ns2.getwebup.in, that stays true before, during, and after the registrar switches. The transfer just changes who you pay and where you manage the domain from.
Before you start: the checklist
- Unlock the domain at your current registrar. Every registrar locks domains against transfer by default (Transfer Lock / Registrar Lock). Log in, find Domain Settings, and toggle it off.
- Get the EPP / Auth code. Same settings page, usually labeled "Get Auth Code" or "Transfer Code." It's emailed or shown on screen - a 16-20 character string. Copy it exactly; it's case-sensitive and often has special characters.
- Turn off WHOIS/ID privacy temporarily if it's blocking the confirmation email (see below), or make sure the privacy-protected contact email still forwards to an inbox you check.
- Confirm the registration is at least 60 days old. ICANN blocks transfers within 60 days of initial registration or a previous transfer. There's no way around this - you'll have to wait it out.
- Check the domain isn't expiring soon. Renew first if it's within 15-20 days of expiry; some registries won't process a transfer that close to expiry, and a lapsed domain mid-transfer is a mess you don't want.
Starting the transfer
At the new registrar, choose "Transfer a domain," enter the domain name and the EPP code, and pay the transfer fee (most registrars bundle a 1-year renewal into that fee). From here, two approvals need to happen:
1. Losing registrar's release
Your current registrar sends a confirmation email to the domain's registered contact asking you to approve or deny the transfer. Approve it - either by clicking the link or, in some cases, by doing nothing (many registrars auto-approve after 5 days if you don't actively deny it).
2. Gaining registrar's confirmation
The new registrar (Getwebup, in this case) also sends a confirmation request. Approve that one too. Once both sides confirm - or the auto-approval window passes - ICANN's process completes the transfer, typically within 5-7 days. Some registrars can push it through in as little as 1-2 days if both approvals happen immediately.
Why the confirmation email never arrives
This is the single most common thing that stalls a transfer. A few causes, in order of likelihood:
- WHOIS privacy is hiding the real contact address. If your registrant email is a privacy-proxy address (like
abc123@whoisguard.com), the forwarding sometimes breaks or lands in spam at the proxy's mail server, not yours. Temporarily disabling privacy for the registrant contact fixes this - you can re-enable it right after the transfer completes. - The registrant email on file is stale. Domains registered years ago often still list an old email address. Update the WHOIS/registrant contact email before you request the auth code, not after.
- Corporate spam filters. Transfer confirmation emails come from automated registrar addresses and occasionally get quarantined. Check spam/junk folders and any mail security gateway logs before assuming it's lost.
- The domain is still locked. Some registrars silently reject the transfer request (no email at all) if the transfer lock wasn't actually removed. Log back in and re-verify the lock status.
Keeping email and the site running during the switch
Since DNS isn't touched, everything keeps working automatically - but here's what to double-check depending on your setup:
| Setup | What to check during transfer |
|---|---|
| Nameservers already point to Getwebup | Nothing to do. DNS zone stays live at Getwebup regardless of who owns the registration. |
| DNS managed elsewhere (Cloudflare, old registrar's DNS) | Don't move DNS at the same time as the domain transfer. Do them as two separate steps, days apart. |
| Email on Google Workspace / Microsoft 365 | MX records live in your DNS zone, not at the registrar - unaffected by ownership transfer. |
| SSL certificate (AutoSSL, Let's Encrypt) | Tied to the domain resolving correctly, not to registrar ownership. No action needed. |
Symptom → Cause → Fix quick reference
| Symptom | Likely cause | Fix |
|---|---|---|
| "Domain is locked" error at new registrar | Transfer lock still enabled | Unlock at losing registrar, wait 15-30 min for it to propagate, retry |
| Auth code rejected | Typo, expired code, or extra whitespace copied | Regenerate a fresh code and paste it directly, don't retype |
| No confirmation email after 24 hours | Privacy proxy or stale contact email | Disable WHOIS privacy temporarily, verify registrant email, check spam |
| "Transfer not eligible" message | Domain registered/transferred within last 60 days | Wait out the 60-day window - no workaround |
| Site or email went down during transfer | DNS or nameservers were changed at the same time | Revert DNS to the last known-good state; retry the domain move separately |
Prevention: doing it clean next time
Change one thing at a time. If you're moving hosting and the domain registration to Getwebup, sequence it: get the site running on Getwebup's servers first (using an A record or a temporary subdomain to test), confirm it loads correctly, then update nameservers if you want Getwebup to manage DNS, and only after that's settled, start the registrar transfer. Stacking all three changes in one afternoon is exactly how "it should've taken five minutes" turns into a support ticket.
Keep the registrant contact email current going forward - set a calendar reminder to check it once a year, since this is the address every future transfer, renewal notice, and expiry warning depends on.
Frequently asked questions
Will my website or email go down during a domain transfer?
No, not if you leave your nameservers and DNS records untouched. A registrar transfer only changes who owns and bills the domain - it doesn't touch your DNS zone, so your site and email keep running throughout the 5-7 day process.
Why can't I transfer my domain right now?
The two most common blockers are a transfer lock still enabled at your current registrar, or the domain being within 60 days of its initial registration or last transfer - ICANN enforces that 60-day window with no exceptions.
I never received the transfer confirmation email. What do I do?
Check whether WHOIS/ID privacy is masking your registrant email - the proxy forwarding sometimes fails. Temporarily disable privacy protection, confirm your registrant contact email is current, and check spam folders before assuming the email is lost.
How long does a domain transfer actually take?
Once both the losing and gaining registrar confirm, ICANN typically completes it in 5-7 days. If both approvals happen immediately instead of waiting for auto-approval, it can finish in as little as 1-2 days.
Should I move my domain and my hosting at the same time?
It's cleaner not to. Get your site working on the new host first, verify it loads correctly, update nameservers if needed, and only then start the registrar transfer - changing everything at once makes it hard to isolate what caused an issue if something breaks.