SPF couldn't be read
The check asked your domain's own nameservers for its TXT records and got no usable answer. It doesn't know whether an SPF record exists, so it doesn't mark SPF missing.
The result shows:
SPF couldn't be read
The lookup failed, so SPF isn't marked missing.
It happens when:
- The lookup returned an error, such as SERVFAIL, or no answer in time.
- Your domain's name is an alias (CNAME) to another name, and that name couldn't be read.
One failure can be a short outage: run the check again in a minute. A failure that repeats is a fault in your DNS, and receivers meet it too. RFC 7208 section 4.4: on a server failure or timeout, "check_host() terminates immediately with the result "temperror"". Most receivers then ask the sender to try again later, so your mail arrives late or not at all.
Find the failing nameserver
- List your nameservers, with your domain in place of
example.com:dig +short NS example.com. For a subdomain such asmail.example.comthat prints nothing, list the nameservers ofexample.cominstead. - Ask each one in turn:
dig TXT example.com @ns1.your-dns-host.example - Read
status:in the header.NOERRORwith an answer, orNXDOMAIN, is a clear answer.SERVFAIL,REFUSEDor a timeout is the fault. - If the answer is a
CNAME, look up the name it points to the same way, starting at step 1 with that name.
On Windows, use nslookup -type=NS example.com for step 1 and nslookup -type=TXT example.com ns1.your-dns-host.example for step 2. Server failed, Query refused or timed out in its answer is the fault.
If every nameserver answers clearly but the check still fails, the fault may be a broken DNSSEC signature, which direct answers don't show. Look up your domain on DNSViz and send its result to your DNS provider.
Otherwise, send the failing nameserver and its status to your DNS provider. A nameserver that no longer serves your domain is the usual cause.
Last updated .