Part of SPF couldn't be read
Your SPF record was read, but a name it points to didn't answer, its nameservers gave different answers, or the check ran out of time following the chain. The check can't count all the DNS lookups your record needs, so it can't tell whether you're under the limit of 10.
On the result:
Part of SPF couldn't be read
A record your SPF includes didn't answer, so we can't tell whether SPF stays within 10 DNS lookups.
An include: or redirect= names another domain's SPF record, usually a sending service's. The check follows each one, and every record those name in turn, so it can count the lookups the way SPF goes over its lookup limit explains. When one of them fails to answer, or takes too long, the count stops there.
When a name times out or returns an error, receivers meet the same failure. RFC 7208 section 5: when a query "returns an error (RCODE other than 0 or 3) or the query times out, the mechanism stops and the topmost check_host() returns "temperror"". Mail that reaches that name before a match is delayed or refused while it lasts. When nameservers return different records instead, a receiver gets one of them and may count a different total from the check.
Find the name
- Read your record: open Details → on your result.
- Look up each
include:andredirect=target in it, for exampledig TXT _spf.example-service.com, and the ones inside those. On Windows, usenslookup -type=TXT _spf.example-service.com. - Read
status:in each answer's header.SERVFAIL,REFUSEDor a timeout is the one that failed;nslookupsaysServer failed,Query refusedortimed out. If every answer looks clear, SPF couldn't be read shows how to ask each nameserver of a name in turn. Compare the records they return, not only the status: nameservers that return different SPF records cause this finding too.
What to do
One failure can be a short outage, or a slow chain the check ran out of time on: run the check again in a minute. If it repeats, look at whose name failed:
- A service you use: tell the service its SPF record isn't answering. Its setup page or support names the current include.
- A service you no longer use: remove its entry from your record. Its domain may have expired, and a record nobody runs is a risk.
- A name of your own: ask your DNS provider, giving the name and the status.
Last updated .