How to fix: DMARC pct= Below 100
The DMARC record specifies pct= less than 100, meaning the declared policy (quarantine or reject) is only applied to a percentage of failing messages. The remainder are delivered as if no DMARC policy exists.
Why it matters
Spoofed messages that fail DMARC have a (100 - pct)% chance of being delivered to recipients, bypassing the protection DMARC is supposed to provide.
pct= is intended as a gradual rollout mechanism. Set it to 100 once you are confident that all legitimate mail passes SPF and DKIM. Leaving it below 100 indefinitely creates a partial protection gap.
How to fix it
- 1Review DMARC aggregate reports (rua=) to ensure all legitimate mail sources pass authentication.
- 2Increment pct= toward 100 as you fix any failing legitimate mail sources.
- 3Set pct=100 once you are confident no legitimate mail is failing.
Code examples
DNS TXT
_dmarc.example.com. IN TXT "v=DMARC1; p=reject; pct=100; rua=mailto:[email protected]; adkim=s; aspf=s"References
Detected automatically by VulnRadar. The check id is email-dmarc-pct-not-100, 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
- MediumDMARC Policy Set to Monitor-Only (p=none)
- MediumMTA-STS Policy File Missing
Questions
- How severe is DMARC pct= Below 100?
- 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-pct-not-100, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does DMARC pct= Below 100 map to?
- It maps to CWE-290. In the OWASP Top 10 it falls under A07: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.