Topic · Troubleshooting

DKIM body hash mismatch

A DKIM body hash mismatch means the received body does not match the canonicalized content digest in the signature.

Email Security Glossary·Practical guidance
Share this definition LinkedIn X WhatsApp Email
01 / How it works

How it works

Receivers recompute the digest after the declared body canonicalization and compare it with bh=.

02 / What can go wrong

What can go wrong

Disclaimer insertion, line-ending transformations or footer rewriting can break signatures in transit.

03 / What to check or do

What to check or do

Compare raw content before and after forwarding and identify the first modifying intermediary.

Practical scenario

Practical scenario

A mailing-list system appends a legal footer to a message after the original sender signs it. The final body differs from the signed content, so the recipient reports a DKIM body hash mismatch even though delivery through the list was expected.

Verification checklist

  1. Capture original and forwarded raw MIME messages.
  2. Review c= canonicalization and bh= digest scope.
  3. Compare modifications introduced at each trusted relay.
  4. Consider authenticated ARC handling or routing changes rather than disabling DKIM entirely.
Practical diagnosis

How to investigate DKIM body hash mismatch

Signal to investigate
A server-added disclaimer can break DKIM on messages that were valid when sent.
Evidence to collect
Compare copies of the message before and after gateways and inspect body canonicalization.
Common wrong conclusion
Avoid regenerating a new signing key as the first fix when the body was modified in transit.
NEXT STEP

Put this into practice

Run a focused check, then explore protection if your domain needs it.

Authoritative reference ↗