Configuration9 min read · Updated Jun 2026

DKIM key age, signing volume, and why rotation matters

ClearDKIM shows you exactly how old each key is and how much mail it has signed. Here is why those numbers matter, and what compliance standards say about key rotation.

Why key age is a security signal

A DKIM private key that has been in use for years presents a larger attack surface than a recently rotated one. An attacker who obtains an old key can retroactively forge signatures on emails that were sent using that key. That risk grows with both key age and the volume of mail signed. Regular rotation limits both the window of exposure and the value of any compromised key.

Many organisations have DKIM keys that were generated when they first set up a sending service and have never been rotated. ClearDKIM’s key inventory makes these visible for the first time, across all your senders in one place.

What signing volume tells you

Volume data serves two purposes:

  • Prioritisation: a key signing 500,000 emails a month carries more risk than one signing 200. Rotate high-volume keys more frequently.
  • Safe retirement: when you rotate, the old key must remain published until no emails signed with it are still in transit or being re-evaluated. ClearDKIM watches volume on the old selector and retires it automatically once it drops to zero.

Compliance standards and rotation requirements

NIST SP 800-177r1

Section 4.5 recommends rotating DKIM keys at least annually and using keys of 2048 bits or longer. Keys shorter than 1024 bits must not be used. NIST guidance also notes that keys used for high-volume signing should be rotated more frequently than the annual baseline.

DMARC RFC 7489

While RFC 7489 does not mandate a rotation interval, it references DKIM (RFC 6376) for signing requirements. RFC 6376 section 3.3.3 notes that key lengths and rotation schedules should be chosen with deployment lifetime in mind, and that a key should be replaced if there is reason to believe it has been compromised.

CIS Controls v8

Control 9.5 (Email and Web Browser Protections) requires organisations to implement DMARC with enforcement, which implicitly requires maintained DKIM keys. CIS Benchmark guidance for email gateways explicitly calls for 2048-bit DKIM keys and periodic rotation as part of a baseline configuration.

Google and Yahoo (2024 requirements)

Bulk senders must use DKIM keys of 1024 bits or longer. Google’s postmaster guidelines additionally recommend 2048-bit keys and state that domains sending at scale should rotate keys periodically to maintain deliverability trust scores.

PCI DSS v4.0

Requirement 12.3.3 mandates that cryptographic keys used in cardholder data environments are subject to documented key management procedures, including rotation schedules. For organisations in scope, DKIM keys used on transactional domains fall under this requirement.

Recommended rotation schedule

ScenarioRotation intervalKey length
Low volume (< 10k/month)Annually2048-bit RSA minimum
Medium volumeEvery 6 months2048-bit RSA or Ed25519
High volume (> 1M/month)Quarterly2048-bit RSA or Ed25519
1024-bit keys (any volume)Rotate immediatelyReplace with 2048-bit or Ed25519

How ClearDKIM automates rotation

ClearDKIM alerts you when a key reaches its rotation threshold based on the schedule you configure (or the defaults above). You approve the rotation from the dashboard, and ClearDKIM handles the rest: publishing the new key, monitoring for signing migration, and retiring the old key, with a full audit trail for compliance review.

Was this guide helpful?