How to fix: DMARC aggregate report address is not a valid URI
The rua tag on the DMARC record contains an entry that is not a usable reporting URI. RFC 7489 requires each entry to be a URI, in practice mailto: or https:.
Why it matters
A reporting address a receiver cannot parse is one that receives nothing. Aggregate reports are the only feedback channel showing which senders fail authentication, so without them there is no way to distinguish a spoofing campaign from a misconfigured legitimate sender, and no safe basis for moving the policy from none to quarantine or reject.
The most common mistake is a bare email address with no mailto: scheme, which looks right at a glance and is silently ignored by every receiver. Reports go only to the addresses that parse, and some receivers drop the whole tag if any entry fails, so one malformed entry can cost you the working ones beside it.
How to fix it
- 1Prefix every mail address with mailto: and separate multiple destinations with commas and no spaces.
- 2Confirm reports are actually arriving, either through a DMARC report processor or by watching the destination mailbox.
- 3Keep at least one destination on a domain you control, so reporting does not depend entirely on a third party.
Code examples
Correct rua syntax
_dmarc.example.com. IN TXT "v=DMARC1; p=none; rua=mailto:[email protected],mailto:[email protected]"References
Detected automatically by VulnRadar. The check id is email-dmarc-rua-invalid-uri, 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 DMARC aggregate report address is not a valid URI?
- VulnRadar rates this low 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-rua-invalid-uri, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does DMARC aggregate report address is not a valid URI map to?
- It maps to CWE-16. In the OWASP Top 10 it falls under A09: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.