Topic · Authentication
DMARC strict alignment
Strict DMARC alignment requires an exact domain match between the visible From address and the SPF or DKIM authenticated domain.
How it works
The DMARC adkim=s and aspf=s tags apply strict matching to their respective authentication identifiers.
What can go wrong
Strict settings can break legitimate messages using vendor-owned bounce domains or signing subdomains.
What to check or do
Inventory all providers and run representative message-header tests before changing alignment tags to strict.
How to investigate DMARC strict alignment
- Signal to investigate
- A message signed by news.example.com fails a strict DMARC check for From: example.com.
- Evidence to collect
- Inspect adkim and aspf in the effective policy, and compare the exact DKIM d= and MAIL FROM domain strings with Header From.
- Common wrong conclusion
- A shared organizational domain does not satisfy strict alignment when the hostnames differ.
How to interpret the evidence
Strict DKIM or SPF alignment requires exact domain identity; relaxed alignment can compare organizational domains determined under the applicable DMARC rules.
What to change and how to verify it
Use the alignment mode that fits the sending architecture; if strict is required, configure matching branded signing or envelope domains.
Put this into practice
Run a focused check, then explore protection if your domain needs it.