How Often Should You Rotate DKIM Keys, and How Do You Do It Safely?
Published 2026-11-14 · Reviewed 2026-11-14 · 6 min read · By the Ingenious AI team
Is someone impersonating your domain right now?
Run the free DomainGuard scan: lookalike registrations, MX-armed variants, certificate-transparency and CAA checks for your domain, in one report.
Run my free DomainGuard scanThe short answer
Rotate DKIM keys at least once a year — every six months for high-value domains — using the selector system that exists precisely to make rotation safe. Generate a new key pair under a new selector, publish the public key in DNS, wait for propagation, switch your sender to sign with the new selector, leave the old key published for at least a week while in-flight mail clears, then remove it. Done in that order, rotation causes zero failed signatures. Done in the wrong order — signer switched before DNS — it breaks authentication for every message until DNS catches up.
Why keys need replacing at all
A DKIM private key is a long-lived secret held by your sending platform. The longer it lives, the more systems, backups, vendor migrations, and former administrators have had the opportunity to touch it — and a leaked DKIM key is a quiet catastrophe, because mail signed with it passes authentication perfectly from anywhere. Rotation bounds that exposure: whatever the history of the old key, its authority ends on a date you chose. Rotation also upgrades cryptography over time, retiring 1024-bit keys for 2048-bit ones as receiver expectations rise.
The other reason is operational hygiene. Domains accumulate selectors the way they accumulate SPF includes — one per tool, per era, per migration — until nobody knows which keys are live. A rotation cycle forces the register to be reconciled: which selectors exist, which services sign with them, and which can be deleted. The deletion step matters as much as the new key; an orphaned selector whose private key sits in a decommissioned vendor's backups is a standing invitation nobody is watching.
Selectors are the rotation mechanism
DKIM was designed for this. The selector — the label before _domainkey in the DNS lookup — lets many keys coexist for one domain, with each signature naming the selector it used. Rotation is therefore never a flag day: you add the new key alongside the old, move signing across, and remove the old at leisure. Every sending platform supports multiple selectors precisely because rotation and multi-vendor sending both depend on it.
Naming discipline makes this painless. Use selectors that encode the service and the period — crm-2026a, billing-2026h2 — rather than the s1, s2 defaults whose meaning evaporates. When a receiver's report shows a selector you cannot identify, that is a finding, not a nuisance: either the register is incomplete or something is signing as you that should not be able to. Both possibilities deserve the same afternoon of investigation.
The safe rotation sequence
Step one: generate the new key pair in your sending platform, or generate it yourself and install the private half there, under a new selector name. Step two: publish the public key TXT record in DNS and verify it resolves from a public resolver, not just your DNS console. Step three: wait — at least the record's TTL, and a day if you can spare it — so every receiver's cache holds the new key before any signature references it. Step four: switch the platform to sign with the new selector, and send test messages confirming dkim=pass.
Step five: leave the old selector published for a week or more. Mail signed before the switch sits in queues and gets re-verified on delivery attempts and forwards; retiring the old key instantly can turn those stragglers into failures. Step six: remove the old DNS record and update your register. Then calendar the next rotation before you close the ticket — rotation that depends on someone remembering is rotation that happens once.
Multi-vendor estates: rotate the fleet, not the message
Most domains sign through several platforms, each with its own selector and its own rotation interface. Rotate them on a staggered schedule rather than all at once: one vendor per week across a month keeps any single mistake small and attributable. Your sender register is the control panel for this — service, selector, key size, date rotated, next due. If a platform cannot rotate keys or caps key size below current practice, that limitation belongs in your vendor-risk notes; email authentication is part of what you are buying.
Cloud mailbox suites handle much of this inside their admin consoles, generating keys and asking you only to publish DNS records. Third-party senders vary: some delegate signing to CNAMEs under their control, in which case their rotation happens on their side and your record never changes — confirm which model each vendor uses, because the CNAME model means their key hygiene is part of your security posture whether you discuss it or not.
Proving rotation worked
Verification is header-deep. After each vendor's switch, collect a real message from that platform and read its Authentication-Results: dkim=pass with your domain and the new selector. Then watch the next days' DMARC aggregate reports for that source: pass rates should be indistinguishable from before the rotation. Any dip names the platform whose DNS or signer is out of step, while the old key — still published during the overlap — keeps most mail passing, which is exactly the safety the sequence was designed to buy.
Close the loop in the register: old selector removed on this date, new selector live, next rotation due. Over years, that register becomes an audit artefact in its own right — evidence, for enterprise customers and insurers, that your email keys are managed rather than merely present. In a field full of set-and-forget, managed is the differentiator.
Five actions to take today
- Maintain a register of every DKIM selector: service, key size, date issued, rotation due.
- For each rotation, publish the new selector's public key in DNS and verify it on a public resolver before switching.
- Wait at least one TTL — ideally a day — after publishing, then switch the platform's signing selector.
- Keep the old selector published for at least a week, then remove it and update the register.
- Verify with real messages and a week of DMARC reports that pass rates did not move, and calendar the next rotation.
Worked example: Brightpath Tutoring rotates five selectors in a month
Brightpath Tutoring, a fictional company monitoring 3 domains, inventoried its DKIM and found 7 selectors, of which 2 belonged to services it no longer used and 1 was a 1024-bit key from its founding setup. Across four weeks it rotated the 5 live selectors — mailbox suite, CRM, booking platform, receipts, and support desk — one or two at a time, with zero dips in DMARC pass rates across 48,000 messages that month. The 2 orphaned selectors were deleted after confirming no platform signed with them, closing a hole nobody had known was open: keys for a departed vendor, valid indefinitely, sitting in that vendor's old backups.
FAQ
What happens if I remove the old key too early?
Messages signed with it that are still in transit or being re-processed will fail DKIM verification. With aligned SPF they may still pass DMARC, but you have spent your safety margin for no benefit — wait the week.
Is 1024-bit DKIM actually unsafe?
It is below current best practice and some receivers treat it as weak. Rotation is the natural moment to move to 2048-bit keys, which every major platform now supports.
My vendor manages DKIM by CNAME delegation. Do I rotate anything?
Your DNS does not change, but ask the vendor about their rotation policy and key sizes — their answers are part of your security posture, and 'we never rotate' is information worth having in writing.
How do I find selectors I have forgotten?
Query your DNS for known service selectors, read DMARC reports for signing domains and selectors in use, and brute-check common selector names with a DNS tool. The reports are definitive for anything still sending.
Should rotation be calendar-driven or event-driven?
Both. Calendar rotation (six to twelve months) handles ageing; event rotation is immediate on vendor incidents, staff departures with DNS access, or any suspicion a key was exposed.