How to fix: DMARC Policy Set to Monitor-Only (p=none)
A DMARC record exists for this domain, but its p= tag is set to "none". Receivers apply no enforcement action to mail that fails DMARC; failing messages are delivered exactly as if no DMARC record existed at all, with reports (if configured) as the only effect.
Why it matters
Spoofed mail that fails SPF and DKIM alignment is still delivered to recipients unchanged. p=none is the single most common DMARC misconfiguration: teams publish a record to start collecting reports, then never progress past it, leaving the domain with the appearance of DMARC protection but none of its enforcement.
RFC 7489 defines three policy values for the p= tag: none (monitor only, no enforcement), quarantine (deliver to spam), and reject (block delivery). p=none is intended as a temporary first step while aggregate reports (rua=) are reviewed to confirm legitimate mail sources are correctly authenticated. Left in place indefinitely, it provides visibility but no actual protection against spoofing.
How to fix it
- 1Review DMARC aggregate reports (rua=) for at least one to two weeks to confirm all legitimate mail sources pass SPF or DKIM alignment.
- 2Move to p=quarantine once legitimate senders are confirmed, then to p=reject once quarantine produces no false positives.
- 3Use pct= to ramp up enforcement gradually (e.g. pct=10, then 50, then 100) rather than jumping straight to full enforcement.
Code examples
DNS TXT: still monitor-only
_dmarc.example.com. IN TXT "v=DMARC1; p=none; rua=mailto:[email protected]"
# No enforcement -- failing mail is delivered normallyDNS TXT: enforcing
_dmarc.example.com. IN TXT "v=DMARC1; p=quarantine; pct=100; rua=mailto:[email protected]"
# Failing mail is now sent to spam instead of the inboxReferences
Detected automatically by VulnRadar. The check id is email-dmarc-p-none, stable across every scan so you can filter or diff on it.
More email checks
Questions
- How severe is DMARC Policy Set to Monitor-Only (p=none)?
- 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-p-none, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does DMARC Policy Set to Monitor-Only (p=none) 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.