Warning

Your SPF record ends in ~all

The short version

Move to -all once DMARC reports show all your mail passes.

What it means

Your SPF record ends in ~all, the soft fail qualifier. Mail from servers that aren't on your list is marked as suspicious but not rejected. That is the right place to start, and with a DMARC policy of quarantine or reject it is a perfectly sound setting.

Why it matters

On its own, ~all leaves the final decision to each receiver, and many deliver soft-failing mail to the inbox. If your domain has no DMARC policy, or only p=none, forged mail can still get through. That is why we count it against the grade only when DMARC isn't enforcing.

How to fix it

  1. Make sure DMARC is in place with a report address, so you can see who sends as your domain. The DMARC builder writes the record.
  2. Read the reports for a few weeks and add any missing real senders to SPF.
  3. When every real sender passes, change ~all to -all, or move your DMARC policy to quarantine or reject. Either one stops forged mail from riding on the soft fail.
  4. 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. With -all, or with DMARC enforcing, this finding is no longer counted against your grade.