The signature was made with an RSA key shorter than 1,024 bits, which receivers are not allowed to accept. The signature counts as failed. The fix is a new, longer key — 2,048 bits — published under a new selector.
dkim=policy reason="signing key too small" (512-bit key) header.d=example.com
How other mail servers write it
Exim (common on cPanel)
dkim=fail (public key too short: 512 bits) header.d=example.com header.s=s1
| Result | dkim=policy (signing key too small) |
| Usually fixed by | The sending domain’s owner |
| Minimum | 1,024 bits; 2,048 recommended (RFC 8301) |
| Yahoo | Requires DKIM keys of at least 1,024 bits |
| Also refused | rsa-sha1 signatures (RFC 8301) |
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
RFC 8301 says verifiers must not consider RSA keys under 1,024 bits valid, and that rsa-sha1 must not be used to sign or verify. Old installations still sign with 512- or 768-bit keys; to a modern receiver those messages are effectively unsigned.
Why it happens
- A key generated years ago with a short length.
- Old signing software, or a server whose defaults were never changed.
How to fix it
- Generate a new 2,048-bit key and publish it under a new selector.
- Switch signing to the new selector, then remove the old one once mail signed with it is delivered.
- If the DNS host cannot take a 2,048-bit key in one string, split it into several strings in one record — they are joined without spaces.
See it for yourself
dig TXT s1._domainkey.example.com +short
The DKIM check above reports the key’s length.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- RFC 8301 — rfc-editor.org
- RFC 6376 — rfc-editor.org
- Sender Best Practices — senders.yahooinc.com
- Troubleshoot DKIM issues — knowledge.workspace.google.com