How to transfer a domain to another registrar without downtime

This guide explains how to move a domain to a different registrar while your website and email keep working the whole time. It is written for site owners and administrators who manage their own domains and DNS. The key point: a registrar transfer changes who manages and bills the registration, not which nameservers answer for the domain, so downtime is entirely avoidable with basic preparation.

Why a transfer does not touch DNS serving

Every domain involves three separate roles: the registry that operates the TLD database, the registrar that sells and manages the registration, and the DNS host that runs the nameservers answering queries for your zone. A registrar transfer moves only the second role. The delegation records stored at the registry are copied over unchanged, so resolvers worldwide keep querying exactly the same nameservers before, during and after the transfer.

As long as those nameservers keep serving your zone, visitors see nothing. There are only two realistic ways a transfer causes an outage: the losing registrar was also your DNS host and deletes the zone when the transfer completes, or the domain expires in the middle of the process. Both are avoidable and covered below.

Record the current state first, so you can verify later that nothing changed:

dig NS example.com +short
dig A example.com +short
dig MX example.com +short

Pre-transfer checks

• Expiry date. Do not start a transfer with less than 30 days of registration left. Check with whois.
• 60-day locks. gTLDs cannot be transferred within 60 days of initial registration, a previous transfer, or, at many registrars, a change of registrant name or email.
• Reachable contact email. Approval emails go to the registrant or admin contact listed in WHOIS. Make sure that mailbox is one you actually read.
• DNS location. If the domain's nameservers belong to the losing registrar, move DNS hosting somewhere independent first, then transfer. Otherwise the zone may vanish the moment the transfer completes.

whois example.com | grep -Ei 'expir|status|name server'

The transfer, step by step

1. Unlock the domain. In the old registrar's panel, disable the transfer lock. In whois output the status clientTransferProhibited must disappear.
2. Get the auth code. Also called EPP code or transfer key. Under ICANN rules the old registrar must provide it within 5 calendar days of your request.
3. Fix the contact email. Temporarily disable WHOIS privacy or confirm the proxy address actually forwards mail to you.
4. Start the transfer at the new registrar. Pay the transfer fee and enter the auth code exactly, with no trailing whitespace.
5. Approve the confirmation. Depending on the TLD and the registrars involved, an approval email can come from the gaining registrar, the losing one, or both. Act on them: this is the step where most stalled transfers are stuck.
6. Wait out the window. A gTLD transfer completes automatically after 5 days if the losing registrar does nothing. Many registrars offer an "accept transfer" button that releases the domain within minutes instead.

whois example.com | grep -i status
# pendingTransfer means the request is in progress

What renews and what does not

A gTLD transfer includes one year of registration, added on top of the current expiry date, up to the 10 year maximum. That is why the transfer has a price: you are effectively paying for a renewal. Do not renew manually right before transferring: if the domain was renewed within the last 45 days, some registries do not stack the transfer year on top and the money is wasted.

What does not move: anything that was a service of the old registrar rather than part of the registration itself. DNS hosting, email forwarding, URL redirects and WHOIS privacy all stay behind. If you use any of them, recreate the equivalent at the new registrar or at a separate DNS host before the transfer, not after.

.lv specifics vs gTLDs

The rules above are ICANN policy and apply to gTLDs such as .com, .net and .org. Country TLDs set their own rules. For .lv, operated by the Latvian registry NIC: the registrar change is confirmed by the domain holder, it usually completes much faster than 5 days, it does not add a year to the registration, and there is no 60-day lock. The registration period simply continues and future renewals are billed by the new registrar. Other ccTLDs differ again, so read the registry documentation instead of assuming gTLD behaviour.

Common traps

• Expired domain. Once a domain has expired and entered the redemption period it cannot be transferred at all. You must pay the old registrar's restore fee first, then transfer.
• Transferring right before expiry. A lost approval email plus a 5 day window can eat your remaining time. Start with at least 30 days of margin.
• Privacy-masked email. The approval email goes to the proxy address shown in WHOIS. If the privacy service drops or delays it, the transfer silently stalls. Disable privacy for the duration.
• Editing registrant data first. Updating the registrant name or email can trigger a fresh 60-day transfer lock. Do WHOIS cleanups after the move, not before.
• Changing nameservers at the same time. Migrate one thing at a time. Transfer the registration with nameservers untouched, verify, then change DNS later if you need to.

Checklist

• More than 30 days left until expiry, domain not in redemption
• No registrant changes or previous transfer in the last 60 days (gTLD)
• DNS hosted independently of the losing registrar, zone file backed up
• dig NS, A and MX output saved for later comparison
• WHOIS privacy off, contact mailbox verified
• Transfer lock removed, auth code received
• Transfer started, confirmation email approved the same day
• whois monitored until the new registrar appears, then dig re-checked
• Old registrar account kept until the transfer is confirmed complete

If you are consolidating domains anyway, we handle transfers and new registrations for gTLDs and .lv alike: see domain registration for current pricing.