What it means
Your SPF record contains something receivers can't parse: a misspelled mechanism, an IP address with a typo, a range like /33, a missing colon after include, or text pasted from a setup guide with curly quotes. The finding's detail shows the exact part that failed.
Why it matters
A receiver that meets a syntax error stops evaluating the record and returns a permanent error. For DMARC that means SPF failed, so your real mail loses SPF protection completely until the record is fixed. One stray character is enough to cause this.
How to fix it
- Read the finding's detail to find the broken part.
- Compare it with the setup guide of the service it belongs to. Common mistakes are
include=instead ofinclude:, a space after the colon,ip4:with an IPv6 address, and quotes typed into the value. - Paste the corrected record into the SPF builder in check mode; it shows any remaining problems before you publish.
- Update the TXT record at your DNS host with the corrected value.
Cloudflare
Open the domain, go to DNS then Records, and edit the TXT record whose content starts with v=spf1. Save, and keep the proxy setting off; TXT records are never proxied.
Other DNS hosts
Open the DNS settings for the domain, find the TXT record for the root of the domain (shown as @ or left blank), and edit its value. Don't add a second TXT record that starts with v=spf1.
Check it worked
Run the SPF checker or the full email check on your domain. Changes show up once the old record's TTL has passed, usually within an hour. The finding should be gone and the SPF section should show your new record with its lookup count.