What it means
Your domain publishes more than one TXT record that starts with v=spf1. The SPF standard allows exactly one. This usually happens when a new service's setup guide says "add this SPF record" and the old record stays in place.
Why it matters
When a receiving server finds two SPF records it stops and returns a permanent error instead of checking either one. To DMARC that counts as SPF failing, so mail that should pass can be sent to spam or rejected, even though each record on its own looks right.
How to fix it
- Copy both records somewhere you can compare them.
- Build one record that keeps every
include:,ip4:,ip6:,aandmxpart from both, listed once, with a single ending such as~all. The SPF builder can check the merged record for you before you publish it. - Replace one of the records with the merged version and delete the other.
- Make sure the merged record still needs 10 DNS lookups or fewer.
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. Only one record should be listed.