Glossary

DKIM

DomainKeys Identified Mail

Definition

DomainKeys Identified Mail (DKIM) uses a digital signature to associate email with a domain and detect changes to signed content.

The receiver verifies the signature using a key published by the signing domain. DKIM does not encrypt the message or necessarily identify its human author.

A customer may include “DKIM” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.

DomainKeys Identified Mail (DKIM) attaches a digital signature to an email. The receiving system uses a public key published by the signing domain to check that signature. A successful check associates the signed message with the domain and detects changes to the portions covered by the signature.

The signing domain and the author shown to the reader are separate identities. A service provider may sign on a customer's behalf, or an attacker may sign mail using their own domain. DKIM does not encrypt email, prove a person's identity or make a payment instruction trustworthy.

Hypothetical example: a consultancy moves its newsletter to a new provider. The provider needs the correct signing setup so receivers can validate messages sent for the consultancy. A signature from only the provider's unrelated domain may not align with the newsletter's visible From domain for DMARC.

Record who controls the signing keys, which services sign your mail and how key changes are managed. Some legitimate forwarding survives DKIM, but changes to signed content can break the signature. Treat DKIM as one part of email authentication alongside SPF and DMARC. A valid signature is useful evidence about delivery and integrity, not a verdict on the message's intent.

Sources: IETF RFC 6376: DKIM signatures.