Turning off Cloudflare Email Routing deletes your MX, SPF and DKIM records
You unlocked Email Routing’s MX record, pointed it at your new provider, then disabled Email Routing. Cloudflare deleted that record along with the rest, because it still counts the record as its own [1]. Your domain was left with no MX records.
The short answer
Disabling Email Routing removes every MX, SPF and DKIM record it added to your root domain, including records you unlocked and edited [1]. To leave without a gap, unlock them, add the new provider’s records as new records, wait until they verify, delete Cloudflare’s records, and only then disable Email Routing [1].
What it looks like
If you edited Cloudflare’s MX record instead of adding a new one, an MX query for your domain comes back empty once you disable Email Routing:
dig +short MX example.com
Going the other way also fails. If your domain still has another provider’s MX records, Email Routing onboarding stops with error 2008 [1]:
Once your MX records point to Cloudflare, mail to an address that has no routing rule is rejected, and the sender does not retry [1]:
What Email Routing adds to your domain
When you onboard a domain onto Email Routing, Cloudflare adds these records to the root domain [1]:
| Type | Name | Content |
|---|---|---|
| MX | example.com |
route1.mx.cloudflare.net, route2.mx.cloudflare.net, route3.mx.cloudflare.net, with priorities Cloudflare assigns |
| TXT (SPF) | example.com |
v=spf1 include:_spf.mx.cloudflare.net ~all |
| TXT (DKIM) | cf2024-1._domainkey.example.com |
v=DKIM1; h=sha256; k=rsa; p= followed by Cloudflare’s public key |
If the domain already has an SPF record, Cloudflare does not add a second one. You add include:_spf.mx.cloudflare.net to your record yourself [1].
Cloudflare locks the records it manages. A locked record cannot be edited or deleted from DNS > Records until you unlock it, and only the Email Routing records on the root domain can be unlocked [1].
Email Routing does not let you send or reply from your domain. When you reply to a forwarded message, the reply goes out from the destination address, such as your Gmail account [2]. To get forwarded mail past SPF, Cloudflare rewrites the envelope sender to a Cloudflare domain and leaves the From: header as it was [2].
What Email Sending adds, and the DMARC record it may write
Email Sending is a separate product with its own records, on the cf-bounce subdomain [1]:
| Type | Name | Content |
|---|---|---|
| MX | cf-bounce.example.com |
route1.mx.cloudflare.net, route2.mx.cloudflare.net, route3.mx.cloudflare.net |
| TXT (SPF) | cf-bounce.example.com |
v=spf1 include:_spf.mx.cloudflare.net ~all |
| TXT (DKIM) | cf-bounce._domainkey.example.com |
v=DKIM1; h=sha256; k=rsa; p= followed by Cloudflare’s public key |
| TXT (DMARC) | _dmarc.example.com |
v=DMARC1; p=reject; |
Cloudflare adds the DMARC record only if the domain has none, and leaves an existing one unchanged [1]. That record is not locked, and Cloudflare keeps your edits [1]. The cf-bounce records stay managed by Cloudflare for as long as the domain is set up for sending [1].
Two things to watch here:
- The automatic policy is
p=reject. That DMARC policy tells receivers the domain owner sees every failing message as a clear sign that the use of the domain is not valid [6]. Cloudflare itself says to change it top=noneif other services send mail for the domain, until their mail passes SPF or DKIM alignment [1]. The steps are in from p=none to p=reject. - Removing the domain from Email Sending deletes records. In Cloudflare’s words, it “deletes the
cf-bounceMX, SPF, DKIM, and DMARC records that Email Service created on the domain” [1]. If Cloudflare wrote your_dmarcrecord, copy it before you remove Email Sending and add it back if it is gone.
Disabling Email Routing does not touch Email Sending, and removing Email Sending does not touch Email Routing [1].
Leave Email Routing without losing mail
This is the order Cloudflare documents [1], with the SPF step spelled out. The example moves to Fastmail, as in change email provider without losing a single message.
1. Unlock the routing records
Go to Compute > Email Service > Email Routing, select the domain, open Settings, and select Unlock on the MX, SPF and DKIM records [1].
2. Add the new provider’s MX records as new records
Create new MX records with the values from your new provider. Leave Cloudflare’s records as they are. Cloudflare’s documentation is explicit: a record it created and you edited “will still be treated as managed by Email Service and will be deleted when you disable Email Routing” [1].
3. Merge SPF into one record that you own
A domain can have only one SPF record: two TXT records that start with v=spf1 give permerror [4], and Cloudflare’s own troubleshooting page says to keep only one [3]. If Cloudflare created your SPF record when you onboarded, it deletes that record when you disable Email Routing [1], so the merged record has to be one you created. Delete Cloudflare’s SPF record and, in the same sitting, add this, with the include Fastmail documents [7]:
example.com. TXT "v=spf1 include:_spf.mx.cloudflare.net include:spf.messagingengine.com ~all"
Then confirm that exactly one record starts with v=spf1:
dig +short TXT example.com
If your SPF record existed before Email Routing, Cloudflare did not add one, and disabling Email Routing removes only the records it added [1]. Add the new provider’s include to your record instead.
4. Add the new provider’s DKIM records
Cloudflare’s routing key lives at cf2024-1._domainkey. Your new provider uses its own selector names, so the two do not conflict [1]. Keys from providers you left earlier are covered in DKIM records still pointing at your old provider.
5. Wait for the new setup to verify, then delete Cloudflare’s records
When your new provider shows the domain as verified, delete Cloudflare’s three MX records and its cf2024-1._domainkey record [1]. From now on, senders that fetch your MX records get only the new provider’s.
6. Disable Email Routing
Open Settings for the domain and select Disable Email Routing [1]. Then query your MX and TXT records again and check that the new ones are still there. Once Email Routing is off, remove include:_spf.mx.cloudflare.net from your SPF record. Email Sending, if you use it, keeps its own SPF record on cf-bounce [1].
Move onto Email Routing from another provider
Email Routing will not start while another provider’s MX records exist [1]. Cloudflare’s order:
- Add and verify the destination addresses first. They belong to the account and can be added before onboarding [1].
- Delete your current provider’s MX records and enable Email Routing right away. Between those two actions your domain has no MX records. Cloudflare says most senders retry and succeed once its records propagate, and that resolvers which cached the missing MX may take up to 30 minutes to retry [1]. During that window, RFC 5321’s implicit MX rule sends mail to the address of
example.comitself [5]. - Fix SPF. Cloudflare adds an SPF record only if none exists. If you have one, add
include:_spf.mx.cloudflare.netto it [1]. If you still send through your current provider, keep its include and DKIM records [1]. - Create the routing rules at once. Without a rule, mail is rejected with “Address does not exist” and not retried [1].
- Keep the old account open until Email Routing is active. Mail sent to cached old MX records arrives there instead of getting lost [1].
Mistakes to avoid
- Editing Cloudflare’s MX record to point at the new provider. Cloudflare still treats it as its own and deletes it when you disable Email Routing [1].
- Disabling Email Routing before the new records exist. It removes every routing MX, SPF and DKIM record from the root domain [1].
- Adding a second SPF record next to Cloudflare’s. That is a permerror for all your mail [4]. Merge them, as in two SPF records on one domain.
- Switching MX to Cloudflare before the routing rules exist. Senders get “Address does not exist” and do not retry [1].
- Keeping Email Sending’s
p=rejectwhile other services send for the domain. Their mail fails DMARC until it passes aligned SPF or DKIM [1][6].
More on moving between providers: email provider DNS records.
Check your MX records
The checker shows which MX records your domain publishes right now, from your browser, and names the provider they point to.
Runs in your browser. Your domain is not sent to this site or stored.
Related guides
Change email provider without losing a single message
Move your domain to a new email provider without bounces. Set up the new SPF and DKIM first, lower the TTL, switch MX in one edit, then clean up the old ones.
Two SPF records on one domain: why both stop working, and how to merge them
Two SPF records on one domain make SPF fail for both providers. Receivers return permerror. Find the duplicate and merge them into one valid TXT record.
DKIM records still pointing at your old provider: what to keep and what to remove
Old DKIM keys keep validating mail signed for your domain. Find the selectors an old provider left, remove or revoke them safely, and fix dangling CNAMEs.
