Topic · Authentication
DKIM signature header
The DKIM-Signature header carries the signing-domain identity, selector, signature and canonicalization information for a message.
How it works
Receivers use its d= and s= fields to locate a DNS public key and cryptographically verify selected headers and body content.
What can go wrong
Misreading a DKIM-Signature as proof of visible From ownership ignores DMARC domain alignment.
What to check or do
Check signature validation status and whether d= aligns with the Header From organizational domain.
How to investigate DKIM signature header
- Signal to investigate
- A DKIM-Signature header exists but recipients still report dkim=fail.
- Evidence to collect
- Inspect d=, s=, a=, h=, bh= and b=; retrieve the DNS selector key and compare the original signed content.
- Common wrong conclusion
- Presence of a signature header does not prove the cryptographic check succeeded.
How to interpret the evidence
Signature validation depends on the published public key, the selected signed fields and body canonicalization. Gateways that append footers or rewrite signed headers can invalidate a previously valid signature.
What to change and how to verify it
Verify at the first recipient hop, check selector publication and rotation, and trace transformations that occur after signing.
Put this into practice
Run a focused check, then explore protection if your domain needs it.