Topic · Troubleshooting
DMARC permerror
DMARC permerror indicates an irrecoverable problem in policy discovery or record interpretation.
How it works
Malformed or conflicting DMARC records may prevent the receiver from applying a valid policy.
What can go wrong
Publishing a broken record can undermine intended domain protection across receivers.
What to check or do
Inspect record count, syntax, tag order and RFC 9989 processing requirements using authoritative DNS.
How to investigate DMARC permerror
- Signal to investigate
- A receiver reports DMARC permerror and cannot interpret the applicable policy.
- Evidence to collect
- Inspect the published record for parse errors, duplicate records and unsupported or invalid required tag values.
- Common wrong conclusion
- SPF permerror and DMARC permerror are separate evaluation outcomes with different causes.
How to interpret the evidence
Permanent errors reflect a record or evaluation problem unlikely to resolve with immediate retry. Receiver implementations can vary; compare against the current RFC rather than an outdated online wizard.
What to change and how to verify it
Correct the authoritative DMARC policy, verify from multiple resolvers and retest aligned mail without adding duplicate records.
Put this into practice
Run a focused check, then explore protection if your domain needs it.