Cloudflare Email Security — formerly Area 1 — filters a domain’s mail at mxa and mxb.global.inbound.cf-emailsecurity.net, both at 10. Older and location-specific setups use mailstream hosts under mxrecord.io. It is a different product from Cloudflare Email Routing.
| What it is | Email security gateway |
| MX records | 10 mxa.global.inbound.cf-emailsecurity.net10 mxb.global.inbound.cf-emailsecurity.net |
| TTL | 300 seconds |
Does your domain use Cloudflare Email Security?
Enter a domain: we read its MX records as a sending server does, name whose each host is, and say whether Cloudflare Email Security’s are all there — and what else is.
The MX records
What Cloudflare Email Security asks for:
example.com. MX 10 mxa.global.inbound.cf-emailsecurity.net.
example.com. MX 10 mxb.global.inbound.cf-emailsecurity.net.
Older names
These still receive mail, though Cloudflare Email Security now documents the records above:
mailstream-central.mxrecord.mxmailstream-east.mxrecord.iomailstream-west.mxrecord.iomailstream-eu1.mxrecord.io
Common mistakes
- Locking Microsoft 365 down to Cloudflare’s addresses before the new MX has spread: Cloudflare says to wait 72 hours after every domain is onboarded.
What changed
- 11 September 2025 — Processing in Germany, India or Australia can be chosen.
- 6 April 2026 — DANE published for the regional MX hosts.
Sources
Checked on 27 September 2026 against these official sources:
- Microsoft 365 as MX Record — developers.cloudflare.com
- Regional processing — developers.cloudflare.com
- Email security changelog — developers.cloudflare.com