What it means
Your SPF record lists senders but doesn't end with an all mechanism or a redirect. Without one, the record says nothing about servers that aren't on the list, and receivers treat their mail as neutral.
Why it matters
The list of allowed senders only protects you if the record also says what happens to everyone else. Without ~all or -all, forged mail gets the same neutral result as mail from an unknown but harmless server, so SPF does little to stop someone sending as your domain.
How to fix it
- Check the record lists every real sender. The SPF builder helps you list them.
- Add
~allas the last term of the record. Unknown senders are then marked as suspicious. - Once DMARC reports show all your real mail passes, change it to
-all. - If your domain should use another domain's SPF policy, use
redirect=instead of anallmechanism. - Update the TXT record at your DNS host.
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. The record should end in ~all, -all or a redirect.