Opens in a new tab

dkim=none: the message was not signed

The message carried no DKIM signature the receiver could use. Without DKIM, DMARC depends entirely on SPF — which forwarding breaks — and bulk senders now fail Gmail’s, Yahoo’s and Microsoft’s requirements. Every service that sends as the domain should sign with it.

dkim=none (message not signed) header.d=none
How other mail servers write it

Yahoo’s older headers

dkim=neutral (no sig)
Resultdkim=none (message not signed)
Usually fixed byThe sending domain’s owner
GmailWrites no dkim= at all for an unsigned message
Required byGmail and Yahoo for bulk senders; Microsoft for 5,000+ messages a day to Outlook.com

Check the DKIM key

Enter the domain from header.d and the selector from header.s (or the DKIM-Signature’s d= and s=): we fetch the published key and check it.

What it means

DKIM is what lets a message keep its authentication through forwarding, and it is the stronger half of DMARC. Since 2024 Gmail and Yahoo require it of bulk senders, and since May 2025 Microsoft of anyone sending 5,000 or more messages a day to Outlook.com addresses.

Why it happens

  • Signing was never turned on at the sending service or mail server.
  • A service signs only with its own domain, and the receiver discarded that signature.
  • A server in between removed the signature.

How to fix it

  1. Turn on DKIM at every service that sends as the domain, signing with your own domain (d=).
  2. Publish the records each service gives you, then check them with the tool above.
  3. Send a test message to confirm it arrives signed.

Sources

Error text and meaning checked on 25 September 2026 against these official sources:

See every receiver’s verdict on your mail

Add your domain and collect its DMARC reports: what Gmail, Microsoft, Yahoo and the rest decided about every message sent as you — SPF, DKIM and DMARC, pass or fail — and who is sending it. Free for your first domain.

Create a free account