DKIM Not Configured
Outgoing email is not signed with DKIM for the organisation's domain, so receivers cannot verify that messages came from it and were not altered.
| Severity | Low |
| CVSS 3.1 | 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N Open in the calculator |
| CVSS 4.0 | 2.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-353: Missing Support for Integrity Check |
| OWASP Top 10 | A08:2025 Software or Data Integrity Failures |
| Category | Security Misconfiguration |
Description
DomainKeys Identified Mail (DKIM, RFC 6376) lets a sending mail system add a digital signature to each message, covering the body and selected headers, and publish the matching public key in DNS under a selector name below _domainkey in the domain. Receiving servers check the signature against the published key to confirm that the message was sent by a system holding the domain's private key and was not altered on the way. A valid DKIM signature for the From domain also satisfies DMARC, and unlike SPF it normally survives forwarding.
Without DKIM, receivers have no such confirmation and DMARC has to rely on SPF alone. Because SPF fails when mail is forwarded, organisations without DKIM often cannot move DMARC to an enforced policy without losing legitimate mail, which leaves the domain open to spoofing for longer, and missing DKIM can also reduce deliverability, as large mailbox providers expect senders to authenticate their mail. On its own, however, the absence of DKIM does not let an attacker forge mail that passes an enforced DMARC policy, which is why it is rated low.
The weakness is reported when messages sent from the domain carry no DKIM signature, or are signed only for the email provider's own default domain rather than the organisation's, so that the signature is not aligned with the From address. Related forms are signing keys shorter than 1024 bits, which current standards say receivers must not treat as valid, and selectors left published for keys that are no longer used. It is identified by examining the headers of messages sent from the domain (DKIM-Signature and Authentication-Results) and by querying the selector records named in them, as selector names cannot be listed from DNS.
Remediation
Sign all outgoing mail with a DKIM key for the organisation's own domain:
- Enable DKIM signing for the organisation's domain on every system that sends mail as it. In Microsoft 365, publish the two selector CNAME records shown for the domain in the Microsoft Defender portal and then enable signing; in Google Workspace, generate a key in the Admin console, publish the TXT record it provides and start authentication; for on-premises servers and third-party senders, follow the product's DKIM instructions.
- Use RSA keys of 2048 bits where the platform and DNS provider support them, and never shorter than 1024 bits.
- Rotate keys periodically using a new selector, and remove the records of retired selectors once mail signed with them is no longer in transit.
- Check that third-party services sign with the organisation's domain rather than their own, so that the signature aligns with the From address.
- Once DKIM is in place, use DMARC reports to confirm that all legitimate mail passes, and move DMARC to an enforced policy.
Confirm the fix by sending a message through each sending service to an external mailbox and checking that the Authentication-Results header shows dkim=pass for the organisation's domain.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.