Check that your mail provider is listed in the SPF record on Cloudflare

Why it matters

The MX records show that Google Workspace or Microsoft 365 hosts your mail, but the SPF record does not include that provider's sending servers, so mail it sends for you can fail SPF and depend on DKIM alone. The scan cannot see who sends for you, so this is a prompt to check, not a proven fault.

Staged change. Do this in stages and check each one before the next, so a mistake does not break your site or your mail.

The fix

1. In the Cloudflare dashboard open DNS > Records and edit your existing SPF TXT record (do not add a second one). Add the provider include before the final all and save.
2. Check the result with the scan: the record must still be a single v=spf1 record with at most 10 lookups.

Type:     TXT
Name:     example.com
Content:  v=spf1 include:_spf.google.com ~all

The examples use example.com. Replace it with your own domain.

Read the documentation ↗(opens in a new tab)

Related

• Reported by the SPF record check
• Publish an SPF record
• Merge the SPF records into one
• Fix the syntax error in the SPF record
• Replace +all in the SPF record with ~all
• Narrow the very large address range in the SPF record
• Change ?all in the SPF record to ~all
• Choose the right SPF ending for this domain
• End the SPF record with ~all or -all
• Bring the SPF record under 10 DNS lookups
• Leave room under the SPF lookup limit
• Remove SPF terms that point at names that no longer exist
• Fix the SPF include that has no SPF record
• Break the loop in the SPF includes
• Replace the include that has several SPF records
• Replace the ptr mechanism in the SPF record
• Check the SPF terms that use macros
• Re-run the scan if part of the SPF record could not be read