How to fix: Multiple DMARC records published
The _dmarc subdomain returns more than one TXT record beginning with v=DMARC1. RFC 7489 section 6.6.3 says a receiver that finds more than one must apply no DMARC policy at all.
Why it matters
The domain has no enforced DMARC policy, while any dashboard that only checks for the presence of a record reports it as configured. Spoofed mail failing SPF and DKIM alignment is delivered rather than quarantined or rejected, and no aggregate reports are generated, so the gap is invisible from your side too.
Same root cause as duplicate SPF records: a second tool or vendor was onboarded, its setup guide said to add a TXT record at _dmarc, and one was added beside the existing one. Only one record may exist, and it has to carry every tag, including all reporting addresses, which belong in a single comma-separated rua value rather than in separate records.
How to fix it
- 1Delete all but one record at _dmarc and merge the tags into the survivor.
- 2Put multiple report destinations in one rua= value as a comma-separated list.
- 3Confirm reports start arriving again after the merge, since none were being generated while the duplicate existed.
Code examples
One merged record with two report destinations
_dmarc.example.com. IN TXT "v=DMARC1; p=reject; rua=mailto:[email protected],mailto:[email protected]; adkim=s; aspf=s"Count what is published
dig +short TXT _dmarc.example.com | grep -c 'v=DMARC1'References
Detected automatically by VulnRadar. The check id is email-dmarc-multiple-records, stable across every scan so you can filter or diff on it.
More email checks
- LowDMARC Forensic Report URI (ruf=) Missing
- MediumDMARC Aggregate Report URI (rua=) Missing
- MediumMTA-STS (SMTP Strict Transport Security)
- LowTLS-RPT Record Missing rua= Reporting URI
- HighSPF Exceeds 10 DNS Lookup Limit
- HighSPF Redirect Loop
- LowDMARC pct= Below 100
- MediumDMARC Policy Set to Monitor-Only (p=none)
Questions
- How severe is Multiple DMARC records published?
- VulnRadar rates this medium severity in the email category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id email-dmarc-multiple-records, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Multiple DMARC records published map to?
- It maps to CWE-16. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.