Re-run the scan if part of the SPF record could not be read
Why it matters
A DNS query for part of the SPF record failed during the scan, so the lookup count is a minimum rather than an exact number. This is usually a temporary problem at the DNS provider of an included service.
The fix
- Run the scan again in a few minutes. If the same name fails every time, look up its TXT record yourself; if it has no working DNS servers, that include is broken and receivers will fail SPF too.
- If the failing name belongs to a service you no longer use, remove its include from your SPF record.
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
- Fix the SPF include that has no SPF record
- 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
Scan your domain to see whether this applies to you.