Alignment vs. authentication: how the difference shapes your results
Passing SPF or DKIM is not enough on its own. DMARC adds one extra requirement (alignment), and that distinction is what actually stops spoofing.
What authentication means
Authentication is the raw pass/fail result of an SPF or DKIM check. It is completely independent of what domain appears in the visible From: header the recipient sees.
- SPF pass: the sending IP is listed in the SPF record of the envelope-from domain (the SMTP MAIL FROM, often invisible to the end user).
- DKIM pass: the signature in the
DKIM-Signatureheader is valid, but that header can reference any signing domain.
An email can pass both checks and still be a spoof of your brand, because the authenticated domain might be completely different from your visible From: address.
What alignment means
Alignment requires that the domain in the authentication mechanism matches the domain in the visible From: header, the one your recipients actually see.
Envelope-from domain matches the From: domain (or a registered parent domain in relaxed mode).
The d= domain in the DKIM signature matches the From: domain (or a registered parent).
DMARC passes if at least one mechanism (SPF or DKIM) both authenticates and aligns. If both fail alignment, DMARC fails, even if both individually pass authentication.
Strict vs. relaxed alignment
The DMARC record lets you choose the alignment mode for each mechanism independently.
| Mode | Tag | Requirement |
|---|---|---|
| Relaxed | aspf=r · adkim=r | Organisational domain match (default) |
| Strict | aspf=s · adkim=s | Exact domain match required |
Most organisations use relaxed mode, which allows subdomain senders (for example mail.xmpl.example signing for xmpl.example) to pass. Strict mode is only advisable once you have complete DKIM coverage on every sender.
Why this matters for your results
When ClearDMARC reports on a sending source, it shows you authentication results and alignment results separately. A source marked Auth pass / Align fail is a common early finding. It means a legitimate source is signing mail (good) but with the wrong domain (needs fixing before you can advance your policy).
Authentication tells you an email was signed by or sent from an authorised server. Alignment tells you that server is authorised for your specific domain. You need both to reach p=reject safely.
Common alignment failures and fixes
- Third-party sender using its own DKIM domain: configure the sender to sign with your domain’s key, or use ClearDKIM to delegate and let ClearDMARC manage alignment automatically.
- Mailing list rewriting the envelope-from: SPF alignment will break on forwarded mail. DKIM alignment survives if the body is unchanged. Ensure DKIM is set up on these sources first.
- Subdomain mismatch in strict mode: switch to relaxed mode, or ensure the subdomain’s SPF and DKIM records explicitly cover that subdomain.