Why is DKIM failing? Selectors, alignment and key length
When DKIM fails, it is almost always one of three things. Here is how to tell which, and how to fix each.
1. The selector is not published
Each signing service uses a named selector at selector._domainkey.yourdomain. If the message is signed but the public key is not published at that exact host, verification fails. Check the selector named in the message’s DKIM-Signature header against your DNS.
2. The signature is not aligned
DKIM can pass on the vendor domain yet fail DMARC because the d= domain in the signature does not match your From domain. Complete each provider’s domain-authentication flow so it signs with d=yourdomain, not theirs.
3. The key is weak, expired, or rotated
1024-bit keys are increasingly rejected. A published key that was rotated away no longer matches signed mail. Forgotten selectors silently expire. Any of these breaks verification.
DKIM breaks because keys are managed by hand across many providers. ClearDKIM hosts every selector through one NS delegation and surfaces each one’s key age and signing volume, so stale, weak, or unaligned selectors are obvious before they break.
How to diagnose quickly
- Use the DKIM lookup tool to fetch and validate the published key for a selector.
- In ClearDMARC, open the failing source and read its DKIM alignment result.
- Compare the
d=ands=values in the message header against what is in DNS.