Topic · Authentication
DMARC policy
A DMARC policy specifies whether mail failing aligned authentication should be monitored, quarantined or rejected.
How it works
The applicable record is discovered under _dmarc using the DNS tree walk defined in RFC 9989, with the p, sp and np policies affecting different domain cases.
What can go wrong
A reject policy deployed without sender discovery can disrupt legitimate traffic.
What to check or do
Use aggregate reporting and phased enforcement with documented exceptions.
Practical scenario
An organization has p=reject at its parent domain but uses an explicit policy override for its notifications subdomain. The effective DMARC request depends on which From domain is being evaluated and the applicable record lookup.
Verification checklist
- Query the exact From-domain DMARC name and the relevant organizational-domain record.
- Review p, sp and alignment settings together.
- Test real subdomain traffic and list explicit overrides.
- Monitor aggregate reports after changing parent or child enforcement.
How to investigate DMARC policy
- Signal to investigate
- A legitimate stream failing DMARC may receive different dispositions across receivers and policies.
- Evidence to collect
- Inspect _dmarc DNS, the applicable policy record, receiver disposition and authentication alignment together.
- Common wrong conclusion
- Do not confuse a domain owner's requested policy with a guarantee of identical enforcement by all receiving systems.
Put this into practice
Run a focused check, then explore protection if your domain needs it.