The message was signed, but the receiver could not find the public key to check the signature: nothing is published at the selector named in it (s=) under the signing domain (d=), or the DNS lookup failed. Usually a DKIM record was never added, was added under the wrong name, or was removed.
dkim=temperror (no key for signature) header.i=@example.com header.s=s1 header.b=AbCdEf12
How other mail servers write it
Microsoft 365 and Outlook.com
dkim=fail (no key for signature) header.d=example.com
Older Gmail headers
dkim=neutral (no key for signature) header.i=@example.com header.s=s1
Exim (common on cPanel)
dkim=tmperror (pubkey unavailable) header.d=example.com header.s=s1
Amavis
dkim=neutral (2048-bit key) reason="invalid (public key: not available)" header.d=example.com
| Result | dkim=temperror (no key for signature) |
| Usually fixed by | The sending domain’s owner |
| Looked up at | selector._domainkey.domain — from s= and d= in the signature |
| Gmail writes it as | dkim=temperror |
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
To verify a signature the receiver fetches the key from DNS at the selector and domain the signature names. When nothing is there, RFC 6376 makes the signature fail permanently; when the lookup errors, temporarily. Gmail reports both as temperror. Either way the message counts as unsigned.
Why it happens
- The DKIM record was never published — a sending service set up without adding its records.
- The record is under the wrong name: the domain typed twice (selector1._domainkey.example.com.example.com), or a TXT record where the service asked for a CNAME.
- The selector was removed or rotated while mail signed with it was still being delivered.
- The domain’s DNS failing (for a temporary error).
How to fix it
- Read s= (selector) and d= (domain) from the result or the DKIM-Signature, and check that exact name with the tool above.
- Publish the record exactly as the sending service gives it — name and type (CNAME or TXT).
- At most DNS hosts, type only selector._domainkey in the name field, not the full domain.
- When rotating keys, keep the old selector published until mail signed with it has been delivered.
See it for yourself
dig TXT s1._domainkey.example.com +short
No answer means no key. A CNAME answer should lead to a TXT record starting v=DKIM1.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- RFC 6376 — rfc-editor.org
- Anti-spam message headers — learn.microsoft.com
- Troubleshoot email authentication in Microsoft 365 — learn.microsoft.com
- How to use DKIM for email in your custom domain — learn.microsoft.com
- Troubleshoot DKIM issues — knowledge.workspace.google.com