BELIKO Talk to Nico
The objection nobody raises until it is too late

Will my email break if I move my website?

It should not, because email does not live in your website. It lives in DNS records. Copy every record across unchanged and mail keeps arriving. Miss one and it stops, quietly.

“Moving hosting is a weekend. Moving a mailbox that his enquiries land in is where people lose two days of leads.” — a reply on r/smallbusiness, 7 August 2026. Right instinct, slightly wrong fear. Here is what actually happens.

Your website and your email are two different things

A domain name points at several places at once. One record sends visitors to your website. Different records send mail to your mailbox. Changing the first does not touch the second unless someone is careless.

When you type a domain into a browser, DNS answers with a web address. When someone emails that same domain, DNS answers with a completely different set of records — the mail exchangers. They live side by side and are independent. This is why a website can move host on a Tuesday and no one in the company notices anything about their inbox.

The risk is not the move. The risk is the copy. Moving a domain to a new DNS provider means recreating every record it had, and the ones that go missing are almost never the obvious ones.

The five records that carry your mail

MX delivers it. SPF, DKIM and DMARC prove it is really from you. Lose the last three and mail still sends — it just starts landing in spam, which is far harder to notice.

MX
Where mail is deliveredUsually several, with priorities. If these are wrong, mail bounces immediately and you find out within the hour.
SPF
Which servers may send as youA TXT record starting v=spf1. Missing, and receiving servers have no reason to trust your mail.
DKIM
The signing keyA TXT record on a subdomain such as mx._domainkey or google._domainkey. Almost never visible without asking for it by name.
DMARC
What to do with mail that failsA TXT record at _dmarc. Also where you find out you are being impersonated.
Provider CNAMEs
Webmail and client accessRecords like mail, imap, pop, smtp. Your phone's mail app connects through these.

Two traps that break mail, both real

One registrar hid three email records on a second page of its DNS list. One DNS import silently routed mail clients through a proxy that does not carry mail. Both were caught by reading, not by assuming.

The dashboard that hides records

On one migration the registrar's DNS list showed the ordinary records on page one and put SPF, DKIM and DMARC on page two. Anyone copying what was on screen would have moved the domain without its authentication and never seen an error — just a slow drift into other people's spam folders.

Fix: records are read from live DNS with dig, every type, including the ones you have to ask for by name. What the internet resolves is the truth; the dashboard is a rendering of it.

The proxy that only carries web traffic

Cloudflare's proxy handles HTTP and HTTPS. Nothing else. On a clinic migration its automatic import set mail, smtp, imap and pop to proxied — which would have stopped every desktop and phone mail client connecting, while webmail carried on working and hid the problem.

Fix: web records proxied, every mail-related record set to DNS only, checked by hand after the import rather than trusted from it.

What happens on the day

Records are captured before anything changes, recreated exactly, and verified afterwards by sending and receiving real mail. Nothing is cancelled at the old provider until that passes.

  1. CaptureEvery record for the domain, read from live DNS and written into a file that stays with the project. This file is also the rollback: it is what the zone looked like before anyone touched it.
  2. RecreateEach record entered as captured. Web records proxied. MX, TXT and mail CNAMEs set to DNS only. Compared line by line against the capture before the nameservers move.
  3. Switch and verifyAfter propagation: mail sent to the domain and received, mail sent from the domain and checked for a pass on SPF and DKIM, and your phone's mail app opened to confirm it still connects.
  4. Only then, cancelThe old plan is cancelled after all of that, never before. Until it is cancelled, going back is one change at the registrar.
What this is not

Preserving your email is not improving it. If your domain has no SPF or DMARC policy today, it will not have one tomorrow unless you ask, and I will tell you it is missing rather than let you assume the move fixed it. Setting those up properly is a separate, small piece of work.

Questions about email

Does moving a website affect email?

Only if the DNS records that route mail are changed or dropped. Email is delivered by MX records, and authenticated by SPF, DKIM and DMARC records. Copy all of them across unchanged and mail keeps working.

Which record is lost most often?

The authentication records. On one migration the registrar's DNS list showed the main records on page one and hid SPF, DKIM and DMARC on page two. Copying only what is visible silently breaks deliverability.

Why not read the records from the registrar dashboard?

Because dashboards paginate, hide and sometimes lie. Records are read from live DNS with dig, which returns what the internet actually resolves.

What breaks mail on Cloudflare specifically?

Proxying a mail record. Cloudflare's proxy carries HTTP and HTTPS only, so a proxied mail, imap, pop or smtp record stops mail clients connecting. Those records must be set to DNS only. Cloudflare's automatic import has set them to proxied.

Do I have to move my mailbox provider?

No. If you use Google Workspace, Microsoft 365, Mailgun or anything else, you keep it. Only the records that point at it are recreated. Cloudflare can forward mail for free but it does not host mailboxes, so it is not a replacement for a real provider.

The free audit tells you if your mail is already at risk.

Send me your domain. I will read its live records and tell you what is there, what is missing, and whether anyone could currently send mail pretending to be you — regardless of whether you ever move.

WhatsApp +1 617 800 3406 How everything is verified