The receiver found the DKIM key but the signature did not check out against it. Either a signed header was changed after signing — a subject tag, a rewritten header — or the key in DNS is not the one the message was signed with: a wrong key published, a key rotated too soon, or one cut short when it was pasted.
dkim=fail (signature did not verify) header.d=example.com
How other mail servers write it
Gmail
dkim=fail header.i=@example.com header.s=selector2 header.b=aRRIv5Z9
OpenDKIM
dkim=fail reason="signature verification failed" (2048-bit key) header.d=example.com header.i=@example.com header.b=AbCdEf12
Exim (common on cPanel)
dkim=fail (signature did not verify; headers probably modified in transit) header.d=example.com header.s=s1
Microsoft, a malformed signature
dkim=fail (signature syntax error) header.d=none
| Result | dkim=fail (signature did not verify) |
| Usually fixed by | The sender, or whoever forwarded it |
| Checked | The b= tag: a signature over the listed headers (h=) |
| OpenDKIM | Uses this wording for a body change too |
Check the DKIM key
Enter the domain from header.d and the selector from header.s (or the DKIM-Signature’s d= and s=): we fetch the published key and check it.
What it means
A DKIM signature covers the headers named in h= and the body hash. When the key is found but the signature does not validate, the signed data changed or the key does not match. OpenDKIM reports a changed body the same way, so a mailing list footer can also show up as this result.
Why it happens
- A signed header changed after signing — a mailing list tagging the subject, a server re-folding headers.
- The public key in DNS does not match the private key used to sign: a copy error, or the wrong key published.
- A key rotated before mail signed with the old one was delivered.
- A long key truncated or mis-quoted when it was split into strings in DNS.
How to fix it
- Check the key with the tool above, and compare it with what the signing service shows.
- Re-publish the key exactly — for long keys, split into strings without adding spaces or quotes inside the value.
- Keep old selectors live until mail signed with them has drained.
- If only mail through a list or gateway fails, the change happens there: see the body hash page.
See it for yourself
dig TXT s1._domainkey.example.com +short
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- RFC 6376 — rfc-editor.org
- Anti-spam message headers — learn.microsoft.com
- Troubleshoot email authentication in Microsoft 365 — learn.microsoft.com
- Troubleshoot DKIM issues — knowledge.workspace.google.com