Opens in a new tab

dmarc=permerror and temperror: the DMARC record could not be used

The receiver found the domain’s DMARC record but could not use it. permerror means the record itself is the problem — usually two records, or a syntax error. temperror means DNS failed during the check and a retry may work. Either way the policy is not applied.

dmarc=permerror action=none header.from=example.com
How other mail servers write it

Microsoft, a DNS failure

dmarc=temperror action=none header.from=example.com

OpenDMARC

dmarc=permerror header.from=example.com
Resultdmarc=permerror
Usually fixed byThe sending domain’s owner
Two recordsBoth are discarded — as if there were none (RFC 9989)
EffectThe policy cannot be applied

Check the DMARC record

Enter the domain from header.from: we find its DMARC record, walking up from a subdomain, and explain every tag.

What it means

When the DMARC record cannot be read, there is no policy to apply and the result is neither a pass nor a fail. Under RFC 9989, a name with more than one DMARC record has all of them discarded.

Why it happens

  • Two TXT records at _dmarc — often one added by a new service beside the old one.
  • A syntax error: the record not starting v=DMARC1, a missing semicolon, a misspelt tag.
  • The domain’s DNS failing (temperror).

How to fix it

  1. Keep exactly one record at _dmarc, starting v=DMARC1.
  2. Check it with the tool above, which reads it the way receivers do.
  3. For temperror, check the domain’s nameservers.

See it for yourself

dig TXT _dmarc.example.com +short

Two lines starting v=DMARC1 is the most common cause.

Sources

Error text and meaning checked on 25 September 2026 against these official sources:

See every receiver’s verdict on your mail

Add your domain and collect its DMARC reports: what Gmail, Microsoft, Yahoo and the rest decided about every message sent as you — SPF, DKIM and DMARC, pass or fail — and who is sending it. Free for your first domain.

Create a free account