LeadHaste

What Is DKIM canonicalization?

DKIM canonicalization defines how selected header fields and the message body are normalized before signing and verification. The simple and relaxed methods tolerate different formatting changes; neither makes a signature survive arbitrary content edits.

By LeadHaste Editorial · AI-assisted editorial review ·

The representation that gets signed

Before a DKIM signature can be checked, the signing and verifying systems need a consistent representation of the selected message material. Canonicalization supplies those rules. DKIM defines simple and relaxed approaches for headers and for the body. A signature's configuration identifies the applicable choices, so the two parts need not use the same method.

The relaxed approach tolerates certain formatting differences, such as specified whitespace changes. It does not make all edits harmless. Rewriting a link, adding substantive text or changing a signed header can still break verification. This distinction matters when a security gateway, tracking system or mailing workflow modifies a message after the original signer has processed it.

An outbound troubleshooting example

A platform signs a message and a downstream component then changes its body. The recipient reports a DKIM failure. Changing DNS keys immediately may be the wrong response if the key is valid and the signed material no longer matches. Compare a controlled message before and after the modifying component, and examine the actual signature and verification evidence before deciding which owner should make a change.

Configuration versus outcome

Record the signing domain, selector, canonicalization setting and trusted receiver's result. Use the raw message rather than an application's rendered view, which can hide whitespace and header details. If a provider manages signing, follow its documented options; do not assume a toggle exists just because the standard defines more than one method.

Canonicalization is a rule for signature input, not a general spam-filter setting. Choosing relaxed behavior does not authorize an unrelated domain, establish DMARC alignment or promise better inbox placement. Treat the operational aim as preserving a verifiable signature through the intended mail path, then test other authentication and delivery requirements separately with real received-message evidence.

Sources

Useful next steps

Related terms

Put the pieces into a system you own.

Explore your ICP and campaign fit on a free discovery call, then decide what your outbound operation needs.

Book your free ICP review →