Domain Transfer Checklist: Zero Downtime, No Lost Email
Short answer. Transferring a domain to another registrar or host risks site downtime and lost email unless you prepare. The key steps: lower DNS TTL in advance, check expiry and status via whois, unlock the domain and get the auth code, migrate every DNS record one-to-one (including MX), then confirm propagation with dig. Below is a practical checklist with commands.
Why transfers break sites
A domain is the entry point to everything: site, email, API документацию. During a transfer people rarely lose the domain itself — they lose individual DNS records: forgetting MX (email stops), TXT for SPF/DKIM (mail goes to spam) or CNAME запись for subdomains. The second common mistake is a high TTL, which keeps old records alive in resolver caches for a day after the switch.
A domain transfer is not "click a button at the registrar". It is a controlled DNS migration where success is measured by users noticing nothing.
Step 1. Check expiry and status
Before transferring, make sure the domain is not near expiry and not locked. Most registrars forbid transfers in the final days before expiry:
# Look up the registration expiry date
whois example.com | grep -i expir
# Example output:
# Registry Expiry Date: 2027-03-14T09:00:00Z
# Registrar Registration Expiration Date: 2027-03-14If less than 2–3 weeks remain, renew first, then transfer.
Step 2. Snapshot current DNS records
Take a full zone snapshot before starting. It is the reference you'll compare the new configuration against:
# Snapshot of key records BEFORE the transfer
dig +short example.com A
dig +short example.com AAAA
dig +short example.com MX
dig +short example.com TXT
dig +short www.example.com CNAMESave the output. After the transfer you'll re-run the same commands and compare.
Step 3. Lower TTL in advance
24–48 hours before the transfer, reduce the TTL of key records to 300 seconds (5 minutes). Then the world sees new records quickly after the switch, not a day later.
The transfer checklist
- Lower TTL to 300s a day or two before the switch.
- Check expiry and status via whois; renew if needed.
- Unlock the domain (remove clientTransferProhibited) and get the auth code (EPP).
- Migrate every DNS record one-to-one: A, AAAA, MX, TXT (SPF/DKIM/DMARC), CNAME.
- Check SSL — confirm the certificate is valid on the new host.
- Start the transfer at the new registrar and confirm by email.
- Verify DNS with dig before and after, wait for propagation.
Records you must not forget
| Record | Responsible for | What breaks if forgotten |
|---|---|---|
| A / AAAA | Site IP address | Site unreachable |
| MX | Mail servers | Email stops arriving |
| TXT (SPF/DKIM/DMARC) | Email authentication | Mail goes to spam |
| CNAME | Subdomains and aliases | Subdomains don't resolve |
| NS | Zone delegation | The domain's entire DNS stops working |
Step 4. Confirm propagation after the transfer
# Re-run the snapshot AFTER the switch and compare
dig +short example.com A
dig +short example.com MX
# Check which resolver already sees the new records:
dig @8.8.8.8 +short example.com A
dig @1.1.1.1 +short example.com AIf different public resolvers return different addresses, propagation is still in progress. Wait for convergence before declaring the transfer done.
Automated control after the transfer
Manual verification is good at transfer time, but afterwards you must not miss that the domain is about to expire or that DNS has "drifted" again. enterno.io can monitor domain expiry (WHOIS) and track DNS-record drift with alerts to Telegram, Slack or email.
FAQ
Why does the site work but email disappeared after the transfer?
Most likely the MX records and TXT for SPF/DKIM were not migrated. The site depends on the A record, email on MX, and the latter are easy to forget.
How long does DNS propagation take?
With a lowered TTL (300s), usually minutes to hours. With a high TTL, old records can live in caches for up to a day.
Should I renew the domain before transferring?
Yes, if less than 2–3 weeks remain. Many registrars block transfers right at expiry.
How do I know the transfer is complete?
When all public resolvers (8.8.8.8, 1.1.1.1) return the new records and whois shows the new registrar.
Check the domain and registration expiry on the WHOIS lookup page. Useful: domain expiry monitoring, SSL control, the online SSL checker and site diagnostics.