How to fix: DMARC Subdomain Policy Weaker Than Domain Policy
The DMARC record includes an sp= tag whose policy (none/quarantine/reject) is weaker than the p= tag governing the organizational domain itself. Subdomains fall back to the weaker sp= policy instead of inheriting the stronger domain-wide policy.
Why it matters
An attacker can spoof mail from an arbitrary, even nonexistent, subdomain of this domain and have it evaluated against the weaker sp= policy instead of the stronger p= policy, bypassing the protection the organizational domain otherwise enforces.
RFC 7489 S6.3 defines sp= as the policy applied to subdomains that do not publish their own DMARC record. When sp= is set to a weaker value than p= (for example p=reject; sp=none), mail claiming to be from any subdomain is only held to the weaker policy, undermining the organizational domain's own protection.
How to fix it
- 1Remove the sp= tag entirely so subdomains inherit the same policy as p=, or
- 2Set sp= to the same value as p= (or stronger) if subdomains genuinely need independent handling.
- 3Only use a weaker sp= deliberately, for example for a domain with many unused subdomains that never send mail, where you want it reported rather than rejected.
Code examples
DNS TXT record
_dmarc.example.com. IN TXT "v=DMARC1; p=reject; sp=reject; rua=mailto:[email protected]; adkim=s; aspf=s"References
Detected automatically by VulnRadar. The check id is email-dmarc-subdomain-policy-weaker, 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 Subdomain Policy Weaker Than Domain Policy?
- 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-subdomain-policy-weaker, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does DMARC Subdomain Policy Weaker Than Domain Policy 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.