Practical security for everyday technology.

A DKIM signature does not make every email request trustworthy

An adult reviewing email on a laptop.
AI-generated photographic illustration; not documentary photography.

An email’s technical details show “DKIM pass.” That is useful information, but it is not an instruction to trust every link, invoice or request in the message. Authentication answers a narrower question than whether a person should act.

RFC 6376 describes DKIM as a way for a signing domain to claim responsibility for a message using a cryptographic signature. It explicitly separates the signer’s identity from the purported author. The signing organisation may be the author’s organisation, a relay or an agent.

Read a pass result at its actual scope

A valid signature can help establish that the signed portions of the message survived in the form checked by the verifier and that the signature relates to the signing domain. It does not establish that the content is truthful, that the domain belongs to the organisation you intended to contact, or that an account has not been misused.

A deceptive sender can operate a domain with correctly configured email authentication. An authentic account can also send an inappropriate or fraudulent request. Those possibilities are why authentication and judgment remain separate steps.

Use an independent route for a consequential request

Imagine a message asking you to change a supplier’s payment details. Even if the authentication checks pass, confirm the change through contact information you already trust. Do not use the new telephone number supplied in the same message as the only confirmation.

Keep the email for your organisation’s review process and report suspicious requests through its established channel. If you are not comfortable reading headers, ask the mail administrator to interpret them rather than guessing from one green label.

Also avoid the reverse mistake: a failed signature does not, by itself, prove who tampered with a message or why. Forwarding and message transformations can complicate interpretation.

DKIM is an important part of email infrastructure. Its value becomes clearer when you let it answer its own technical question and use separate checks for identity, context and the action being requested.