DKIM signature not found or body hash did not verify
Quick fix
Signature not found: turn on DKIM signing with your own domain in every service that sends for you, and publish the key it gives you. Body hash did not verify: move the footer, disclaimer or link rewriting before the signing step.
How to fix it
- Signature not found: turn on DKIM signing with your own domain in every service that sends for you, and publish the key or CNAME it gives you at
selector._domainkey.example.com. - Body hash did not verify: send a test message directly from the signing service to an outside mailbox. If it passes there, a hop after signing changes the body.
- Move the footer, disclaimer or link rewriting before the signing step, or have the last server that changes the message sign it.
- Sign with
c=relaxed/relaxedwhere the service lets you choose, so whitespace changes do not break the signature. - Keep SPF aligned as well, so DMARC still passes when a DKIM signature breaks.
Learn more: DKIM explained: selectors, keys and rotation
How to check
Open a message that failed and look at its headers ("Show original" in Gmail). The DKIM-Signature header names the signing domain in d= and the selector in s=; Authentication-Results shows the result. Then check which DKIM keys your domain publishes with the DKIM selector finder.
The DKIM selector finder opens with your domain filled in; it runs when you press Check.
Tools to check it
What the error means
These are two different DKIM results from the receiving server. Signature not found (dkim=none in the Authentication-Results header) means the message arrived without a DKIM-Signature header: nobody signed it for your domain. Body hash did not verify means there is a signature and the key was found, but the body the receiver hashed is not the body that was signed, so something changed the message on the way.
A DKIM signature carries a hash of the message body in its bh= tag (RFC 6376, section 3.5). The receiver canonicalizes the body it got, hashes it, and compares. If the hashes differ, RFC 6376 section 6.1.3 tells it to ignore the signature with the reason "body hash did not verify". Receivers show this as dkim=fail or dkim=neutral followed by that reason. A message with no signature at all gets dkim=none, "the message was not signed" (RFC 8601, section 2.7.1).
Common causes of a missing signature: DKIM is not turned on in the sending service, the service signs with its own domain instead of yours, or the message was sent by a system you did not set up (a web form, a printer, a server cron job). Common causes of a body hash failure: a gateway or mailing list adds a footer or disclaimer after signing, a security product rewrites links, or a relay changes line endings or the transfer encoding. With c=simple body canonicalization even a change in trailing whitespace breaks the hash.
A signature whose selector has no key in DNS is a third case, a key lookup failure; see DKIM_NOT_FOUND.
Sources
- RFC 6376: DKIM Signatures (checked 2026-11-15)
- RFC 8601: Authentication-Results header field (checked 2026-11-15)