Cloudflare Email Routing forwards a domain’s mail to the addresses you choose through three MX hosts, route1, route2 and route3.mx.cloudflare.net, which Cloudflare adds and locks, with priorities it assigns itself.
| What it is | Forwarding service |
| MX records | 0 route1.mx.cloudflare.net0 route2.mx.cloudflare.net0 route3.mx.cloudflare.net |
| SPF | include:_spf.mx.cloudflare.net |
Does your domain use Cloudflare Email Routing?
Enter a domain: we read its MX records as a sending server does, name whose each host is, and say whether Cloudflare Email Routing’s are all there — and what else is.
The MX records
What Cloudflare Email Routing asks for:
example.com. MX 0 route1.mx.cloudflare.net.
example.com. MX 0 route2.mx.cloudflare.net.
example.com. MX 0 route3.mx.cloudflare.net.
Worth knowing
The same hosts on a cf-bounce subdomain belong to Cloudflare’s email sending, which uses them for bounces — not to Email Routing. Cloudflare’s own domain uses Cloudflare Email Security, a different product.
Common mistakes
- Another mail server’s MX beside Cloudflare’s: Email Routing needs its own.
- Turning Email Routing off before adding the new provider’s records — it removes its MX, SPF and DKIM.
Sources
Checked on 27 September 2026 against these official sources:
- Domain configuration — developers.cloudflare.com
- Troubleshooting — developers.cloudflare.com