Topic · Authentication
DKIM 2048-bit key
A 2048-bit RSA DKIM key is a commonly recommended key size for secure signing where supported by senders and DNS infrastructure.
How it works
The signing system stores the private key while the public key is placed in DNS under the chosen selector.
What can go wrong
Weak legacy keys increase cryptographic risk, while very large DNS TXT responses can be mishandled by bad tooling.
What to check or do
Review current provider requirements, migrate legacy keys and check that public key TXT records are valid.
How to investigate DKIM 2048-bit key
- Signal to investigate
- A sender is moving from older DKIM RSA keys but must avoid a signing outage.
- Evidence to collect
- Inventory active selectors, DNS public-key lengths, ESP support and messages still signed with each selector.
- Common wrong conclusion
- Deleting the old DNS selector immediately can cause delayed messages to fail verification.
How to interpret the evidence
Longer RSA keys improve resistance against key recovery but may be difficult to publish in some DNS panels if TXT splitting is handled incorrectly. DNS concatenation remains part of verification.
What to change and how to verify it
Create and test a new selector, migrate signing, allow old mail to age out, then retire the earlier selector.
Put this into practice
Run a focused check, then explore protection if your domain needs it.