DomainKeys Identified Mail
Also called DKIM.
A cryptographic signature proving an email wasn't altered in transit.
What it is
An email-authentication standard in which the sending domain signs selected headers and the body with a private key; receivers verify the signature using a public key published in DNS. A valid signature ties the message to the signing domain.
Why it matters
DKIM survives forwarding better than SPF and provides integrity, so a failed or missing signature on a 'trusted' sender is a meaningful red flag during email investigation.
In practice
A forwarded newsletter still verifying because its DKIM signature over the body remained intact.
What to look for
- dkim=pass with the signing domain in d=.
- Signatures from a domain unrelated to the From.
- Weak or old keys that were never rotated.
Common mistake
Treating any DKIM pass as trustworthy. The signing domain must align with the From for DMARC.
Use it in CyberKit
- Email Header Analyzer
Walk the Received chain, and read the SPF, DKIM and DMARC verdicts.
- Phishing Case
A reported invoice email: pull the deciding values out of its raw headers, and say what they establish.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Microsoft Defender for Office 365 Commercial
Filters phishing and malicious attachments in Microsoft 365 and lets you investigate messages.
-
Proofpoint Email Protection Commercial
A mail gateway that scores, rewrites and quarantines suspicious mail.
-
VirusTotal Commercial
A quick second opinion on a suspicious attachment or link.
Read next
- Sender Policy Framework: DNS record listing which servers may send mail for a domain.
- Domain-based Message Authentication, Reporting and Conformance: A policy tying SPF and DKIM to the visible From and reporting failures.
- Email Header Analysis: Reading an email's full headers to trace origin and authentication.