What happens to email and DNS when a domain changes hands.

Three separate things, often at three companies

A working domain involves three layers, and they are frequently held at different companies:

• The registration — who holds the name, at which registrar, and until when. This is what a transfer moves.
• DNS — the records that say where the website, email and other services live. They are hosted by whoever runs the domain’s nameservers: often the registrar, sometimes a separate DNS provider or the web host.
• The services — the web host, the email provider, any apps. They keep running wherever they are; DNS just points to them.

A registrar transfer moves the first layer. Whether the second layer survives depends on where it is hosted.

When DNS survives a transfer, and when it does not

If the domain uses nameservers at an independent DNS provider or web host, a registrar transfer normally leaves them in place and nothing visible changes.

If it uses the old registrar’s free DNS, the records live in the old registrar’s account. Depending on that registrar, they may be removed once the domain leaves — and the website and email go dark until the records are recreated somewhere else.

The fix is boring and reliable: copy every DNS record before the transfer, recreate them at the new DNS host, confirm they match, then switch nameservers. Lowering the record TTLs a day ahead makes any change take effect faster.

Email is the part that bites

Email depends on a handful of DNS records: MX records that say which server accepts mail, plus TXT records for SPF, DKIM and DMARC that tell other mail systems which senders are legitimate. Miss one and mail bounces or lands in spam.

When you buy a domain that had email on it, the previous owner’s addresses stop working for them the moment DNS points elsewhere — and mail sent to those addresses may start arriving at whatever you set up. Do not set up a catch-all inbox on a name you just bought, and do not read mail that was clearly meant for the previous owner.

When you sell a domain, change the login email on every account that uses an address at that domain before you hand it over. Whoever controls the domain’s email can request password resets.

The website and its security certificate

A website keeps running on its host, but the HTTPS certificate is tied to proof of control of the domain. After a change of owner or DNS, expect the new owner’s host to issue a fresh certificate. Most hosts do this automatically once DNS points at them.

Buying a developed name with a live site? Agree in writing what moves with it: hosting account, files, content, analytics and email — they are separate from the domain registration.

A safe order of operations

1. Export or screenshot every DNS record (A, AAAA, CNAME, MX, TXT, SRV).
2. Set up the new DNS host and recreate the records; lower TTLs a day ahead.
3. Seller unlocks the domain and sends the authorization code privately.
4. Buyer starts the transfer at their registrar; it completes when the old registrar releases it.
5. Point nameservers to the new DNS host if they are not already there.
6. Test: website over HTTPS, send and receive email, check SPF/DKIM/DMARC.
7. Turn on the registrar lock, auto-renew and two-factor login.

Want the transfer mechanics — auth codes, escrow and the 60-day rules — in depth? Read how a domain transfer actually works. Need a website built on your new name? Eye To Ad Media builds custom-coded sites and handles the SEO side.

Sources, none of them ours: ICANN Lookup · ICANN Transfer Policy