How to Transfer a Domain Without Disrupting Email

The most common fear about transferring a domain is losing email. The good news is that a registrar transfer, done correctly, does not touch your email at all. The bad news is that “done correctly” has a specific sequence, and skipping a step — especially the DNS backup — is how inboxes go silent.

This guide gives you that sequence: what to prepare, what to back up, and how to verify mail is flowing before, during, and after the move.

Why email breaks during a domain move

Email delivery depends on DNS records, not on the registrar. When someone sends mail to [email protected], their mail server looks up your domain’s MX records, finds the mail server those records point to, and delivers the message there.

A transfer can break that chain in three ways:

1. The nameservers change. If the new registrar replaces your nameservers with its own defaults, your DNS zone is rebuilt from scratch — and unless the new zone contains your MX records, mail has nowhere to go.
2. The MX records are lost. Some registrars do not copy DNS records during a transfer. If your MX records only existed at the old registrar’s DNS, they vanish when you leave.
3. DNS propagation delay. Even a correct change takes time to spread. If you change nameservers and MX records at the same moment, some mail servers will use the old records and some the new ones, and messages can bounce in the gap.

Every step in this guide exists to prevent one of those three failures.

The golden rule: separate the transfer from the DNS change

A registrar transfer moves the registration. Your DNS — the nameservers and the records they serve — is a separate thing. The safest approach is to keep them separate:

• Transfer the registration, but keep the same nameservers. If your DNS is hosted by a third party (for example, Cloudflare, your hosting provider, or a dedicated DNS service), the transfer does not touch it at all. Your website and email keep working throughout, because nothing about DNS changes.
• If your DNS is hosted by the losing registrar, move DNS before the transfer, or make sure the gaining registrar will import your existing zone. Do not let the transfer be the moment your DNS changes hands.

If you follow only one rule in this guide, follow this one: never change registrar and nameservers at the same time.

Before you start: the preparation checklist

1. Back up your entire DNS zone

Export or screenshot every DNS record for the domain: A, AAAA, CNAME, MX, TXT (including SPF, DKIM, and DMARC), NS, and SRV. Most registrars and DNS providers have an export function; if yours does not, copy the records into a document by hand. Pay special attention to:

• MX records and their priorities. Note the exact hostnames and priority numbers. A missing or reordered MX record is the most common cause of lost mail.
• SPF, DKIM, and DMARC TXT records. These authenticate your outgoing mail. Losing them does not stop incoming mail, but it can send your outgoing mail to spam.
• The mail hostname’s A record. If your MX points to mail.example.com, that hostname needs its own A (or AAAA) record pointing at the mail server’s IP.

2. Confirm who actually hosts your email

Email might live in any of these places: your hosting provider, Google Workspace, Microsoft 365, or a dedicated mail provider. Find out which one, and get the correct MX records from that provider’s documentation — do not guess them from memory. If you are unsure, check your current MX records with a DNS lookup tool and match them against your provider’s published values.

3. Check the 60-day locks

A domain cannot be transferred within 60 days of registration or of its last inter-registrar transfer, and a change of registrant can trigger a further 60-day lock unless you opted out beforehand. Check these before you start, so you do not begin a migration you cannot complete. The full rules are in How Domain Registration, Renewal and Transfer Work.

4. Lower the TTL

TTL (time to live) is how long DNS resolvers cache a record, in seconds. A TTL of 86400 means a change can take up to 24 hours to propagate. A day or two before any DNS change, lower the TTL on your MX and A records to 300 seconds (5 minutes). Then, when you do make a change, it spreads in minutes rather than a day. Remember to raise the TTL back to a normal value afterwards — a very low TTL increases DNS query load permanently if you forget it.

5. Make sure you can receive transfer emails

Transfer confirmations go to the registrant email address. If that address is on the very domain you are transferring, and something goes wrong with DNS, you may not receive the confirmation. Before starting, set the registrant email to an address on a different domain (for example, a personal Gmail address) if it is not already, or at least confirm you can access it.

The transfer, step by step

1. Unlock the domain at the current registrar and request the authorisation (EPP) code. Keep it private.
2. Start the transfer at the new registrar, entering the domain and the code.
3. Do not change the nameservers yet. If the new registrar asks whether to use its nameservers, choose to keep your existing ones. If it does not ask, check the nameserver setting immediately after the transfer is initiated.
4. Approve the transfer via the confirmation email sent to the registrant address.
5. Wait for completion — typically five to seven days. During this time, your website and email continue working exactly as before, because DNS has not changed.
6. Verify DNS at the new registrar. Once the transfer completes, confirm that the nameservers are still the ones you expect, and that the DNS zone (if the new registrar now hosts it) contains your MX, SPF, DKIM, and DMARC records. If anything is missing, add it from your backup before you change anything else.
7. Only now, if you intend to move DNS, change the nameservers — with the TTL already lowered, and with the full zone already in place at the new provider.

Testing email before and after

Do not assume mail works. Test it.

Before the transfer: send a test email from an external account (not from your own domain) to your domain address, and reply to it. Confirm both directions work. Note the time it takes to arrive.

During the transfer: send another test email each day. If mail stops, you have caught the problem early, while the old registrar can still help.

After the transfer and any DNS change: repeat the test in both directions, and check:

• MX records resolve correctly from a public DNS lookup tool.
• SPF, DKIM, and DMARC are published and valid — use your mail provider’s checker or a public DNS lookup for the TXT records.
• Mail arrives promptly. A delay of more than a few minutes after a DNS change usually means a stale cache or a wrong record, not a transfer problem.

If mail stops after a nameserver change, the most likely causes, in order, are: the MX records are missing at the new DNS provider; the MX records point to a hostname with no A record; or the TTL was high and resolvers are still serving the old zone. Check those three before anything else.

Common mistakes

• Changing nameservers and registrar on the same day. The two changes compound, and when mail breaks you cannot tell which one caused it.
• Assuming the new registrar copies your DNS. Many do not. Always have a backup of the zone.
• Forgetting the mail subdomain’s A record. An MX record pointing to mail.example.com is useless if mail.example.com has no A record at the new provider.
• Leaving the TTL at 300 forever. It works, but it increases DNS load and can slow lookups slightly. Raise it back after the migration settles.
• Transferring with an expired or inaccessible registrant email. You will not receive the confirmation, and the transfer will stall.

The bottom line

A domain transfer does not have to touch your email — and if you keep the nameservers unchanged, it will not. The work is in the preparation: back up the DNS zone, confirm who hosts your mail, lower the TTL, and test in both directions. Do those four things and the transfer becomes a quiet administrative change instead of an outage.

Related reading: How Domain Registration, Renewal and Transfer Work, DNS Records Explained with Practical Examples, and What Happens When a Domain Expires. See our domain services.

---

Reviewed 25 October 2026. Prices, fees, and availability for Offshore Hosting domain services are [TO BE CONFIRMED] — this article does not state them.

Sources

• ICANN — Domain Name Transfers: https://www.icann.org/en/contracted-parties/accredited-registrars/resources/domain-name-transfers
• ICANN — 5 Things Every Registrant Should Know About the Transfer Policy: https://www.icann.org/resources/pages/about-transfer-policy-2017-10-10-en
• Cloudflare — Onboard a domain (DNS and email records): https://developers.cloudflare.com/fundamentals/manage-domains/add-site/
• Cloudflare — Domain configuration, Email Service docs: http://developers.cloudflare.com/email-service/configuration/domains/

← All guides · Knowledge Base