Topic · Authentication
DMARC relaxed alignment
Relaxed DMARC alignment accepts an authenticated organizational domain that matches the organizational domain of the visible From address.
How it works
The applicable organizational domain is determined under DMARC policy discovery; SPF and DKIM alignment then compare that organizational domain with the visible From domain under relaxed policy.
What can go wrong
Organizations may wrongly assume that every exact hostname must match, or accidentally authorize broad delegated senders.
What to check or do
Examine Header From, MAIL FROM and DKIM d= values and confirm the organizational-domain relationship against policy.
How to investigate DMARC relaxed alignment
- Signal to investigate
- A sender expects mail.news.example.com and example.com to align but the receiving implementation disagrees.
- Evidence to collect
- Capture the effective DMARC record, the author domain, and every authenticated identifier; test organizational-domain discovery, including DNS tree walk.
- Common wrong conclusion
- Relaxed alignment is not a blanket license for an unrelated third-party domain.
How to interpret the evidence
The organizational domain is not always derived by simply deleting the first DNS label; public suffix and policy-discovery boundaries matter. Receiver implementation versions can also differ.
What to change and how to verify it
Publish explicit DMARC policies where appropriate and align branded identities; document receiver differences before changing enforcement.
Put this into practice
Run a focused check, then explore protection if your domain needs it.