DMARC couldn't be read
The check asked your domain's own nameservers for the DMARC record at _dmarc. in front of your domain and got no usable answer. It doesn't know whether a record exists, so it says nothing either way.
The result shows:
DMARC couldn't be read
The lookup failed, so DMARC isn't marked missing.
Two things cause it:
- The lookup returned an error, such as SERVFAIL, or no answer in time.
_dmarcis an alias (CNAME) to another name, often at a DMARC service, 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 9989 section 4.10.1 leaves each receiver to decide: some deliver the mail, others ask the sender to try again later. Gmail asks again later:
451 4.7.26 Unauthenticated email from domain-name is not accepted due to domain's DMARC policy, but temporary DNS failures prevent authentication.
That line is from Gmail SMTP errors, updated 10 Nov 2026.
Find the failing nameserver
- List your nameservers, with your domain in place of
example.com:dig +short NS example.com - Ask each one in turn:
dig TXT _dmarc.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.
Send the failing nameserver and its status to your DNS provider. A broken DNSSEC signature and a nameserver that no longer serves your domain are the usual causes. If _dmarc is an alias to a service you no longer use, replace it with your own TXT record.
Last updated .