Warning

Your SPF record ends in ?all, which protects nothing

The short version

Change ?all to ~all, then to -all once your senders pass.

What it means

Your SPF record ends in ?all, the neutral qualifier. It tells receivers that you make no statement about servers that aren't on your list. In practice that is the same as having no rule for unknown senders at all.

Why it matters

A neutral result doesn't help receivers spot forged mail, and DMARC doesn't count it as a pass for anyone else either, so it gives you the effort of maintaining SPF without most of the protection. Some guides suggest ?all while testing, and it is easy to forget to change it later.

How to fix it

  1. Check that every service that sends as your domain is in the record. The SPF builder can list them and count the lookups.
  2. Change ?all to ~all. Unknown senders are then marked as suspicious.
  3. Watch your DMARC reports for a few weeks. When all your real mail passes, change ~all to -all.
  4. Update the TXT record at your DNS host each time.

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 or -all.