Fix the SPF include that has no SPF record

Why it matters

An include in the SPF record points at a domain that publishes no SPF record, which is a permanent error and breaks SPF for the whole domain. The cause is usually a typo or a service that was shut down.

The fix

1. The finding names the include target. Compare it with your provider's setup page for the exact include domain; a typo or an old name is the common cause.
2. Correct the name, or delete the include if you no longer use that service.
3. Check the target again with a TXT lookup; it must return exactly one record starting with v=spf1.

example.com.  IN TXT  "v=spf1 include:_spf.CORRECT-PROVIDER-DOMAIN.example ~all"

The examples use example.com. Replace it with your own domain.

Read the documentation ↗(opens in a new tab)

Related

• Reported by the SPF record check
• Publish an SPF record
• Merge the SPF records into one
• Fix the syntax error in the SPF record
• Replace +all in the SPF record with ~all
• Narrow the very large address range in the SPF record
• Change ?all in the SPF record to ~all
• Choose the right SPF ending for this domain
• End the SPF record with ~all or -all
• Bring the SPF record under 10 DNS lookups
• Leave room under the SPF lookup limit
• Remove SPF terms that point at names that no longer exist
• Break the loop in the SPF includes
• Replace the include that has several SPF records
• Replace the ptr mechanism in the SPF record
• Check the SPF terms that use macros
• Re-run the scan if part of the SPF record could not be read