To let Cloudflare Email Routing and Email Service send as you, add include:_spf.mx.cloudflare.net to your SPF.
On the root for Email Routing; for sending, Cloudflare puts it on a cf-bounce subdomain. Cloudflare adds these records for you when the domain’s DNS is on Cloudflare. Measured on 5 Nov 2026, the include costs 1 of your 10 SPF lookups, leaving 9 for everything else.
- Include
- _spf.mx.cloudflare.net
- Vendor’s record
- v=spf1 include:_spf.mx.cloudflare.net ~all
- Where it goes
- Your domain’s SPF record (@)
- Needed on your root?
- Yes, if you send through it from your domain
- Lookups (measured)
- 1 of 10
- Ranges published
- 1 ip4 · 1 ip6
- Category
- Forwarding
What include:_spf.mx.cloudflare.net expands to live, 5 Nov 2026
v=spf1 ip4:104.30.0.0/19 ip6:2405:8100:c000::/38 ~all
Counted as RFC 7208 §4.6.4 does: the include itself plus every nested include, a, mx, ptr, exists and redirect. Includes can change at any time; this page re-measures daily.
Adding it next to another service
A domain has exactly one SPF record, so add the include to the record you already have. With Google Workspace, for example:
v=spf1 include:_spf.google.com include:_spf.mx.cloudflare.net ~all
How it affects DMARC
DMARC passes when SPF or DKIM passes for a domain aligned with your From address. With Cloudflare Email Routing and Email Service sending from your domain, its include lets SPF pass and align; DKIM signing with your domain gives you a second, forwarding-proof way to pass.
Other forwarding services
Sources
- Cloudflare: Email Service domain configuration · checked 5 Oct 2026
- RFC 7208 §4.6.4: DNS lookup limits · checked 5 Oct 2026
peekip isn’t affiliated with Cloudflare Email Routing and Email Service; follow the vendor’s own setup page, which shows the exact values for your account.