Removing a revoked DKIM selector
If we flagged a DKIM selector as revoked, it means the TXT record at that selector exists but its `p=` field is empty. RFC 6376 §3.6.1 treats that as 'this key has been revoked, do not validate against it.' Receivers see the record, see the empty key, and fail signatures. Here's what to do.
What revocation actually signals
DKIM TXT records carry a public key in the p= tag. The full record looks something like v=DKIM1; k=rsa; p=MIGfMA0.... When the p= value is empty (just p= with nothing after it, or p=;), RFC 6376 says this is the operator declaring the selector retired, and receivers should not verify against it.
The intent is to make rotations cleanly observable. Old selectors don't just vanish from cache; they get explicitly marked dead so receivers know.
Why this is a problem if it's still published
A revoked selector that's still in DNS isn't just informational: receivers will actively fail signatures from it. If you rotated DKIM keys but left the old selector behind in revoked state, AND your sender is somehow still signing with the old selector (cached configs, stale ESP setup), every message ends up DKIM-fail. Your alignment % drops without a clear cause.
Even if your sender isn't using the old selector, a revoked record is noise. It suggests "this domain doesn't keep its DKIM tidy" to receivers and to anyone auditing your DNS.
How to fix it
The fix is one of two things:
- If the rotation is complete: the new selector is signing your mail and the old one is no longer used, so delete the old TXT record entirely. Don't leave a revoked stub. Find the record at
<old-selector>._domainkey.<your-domain>in your DNS provider and remove it. - If the rotation is in progress: you intended to revoke but the new selector isn't fully published yet, so republish the old key temporarily so signatures from in-flight mail still verify. You probably have the public key in your ESP's DKIM settings panel; copy it back into the TXT value as
p=<the-base64-string>.
Verifying the fix
After you change the DNS record, run a fresh DKIM scan from the DKIM tab. The check will re-resolve the record and clear the warning. Allow a couple of minutes for DNS propagation if you're behind a slow resolver chain.
If it still reports the selector as revoked after the TTL has passed, confirm the record is actually gone with dig +short TXT old-selector._domainkey.yourdomain.com. An empty answer means DNS is right and the finding is stale, so scan once more. A returned p= means the delete did not take, or it removed a different selector than the one your mail signs with.
Why we don't auto-fix this
We don't currently offer one-click revocation cleanup because deleting the TXT record is a destructive op. If the record was revoked deliberately as part of a rotation, we'd be undoing that signal. Better to surface the warning and let you delete via your DNS provider with full context.
For DKIM rotations going forward, see Why 1024-bit DKIM keys are being phased out for the recommended rotation playbook.
Fix DNS issues with one click. See the exact change before it goes live.
Click the fix. We email you the exact record, wait five minutes, write it to Cloudflare or AWS Route 53, and read it back from public DNS. On any other DNS host, you get the record and a link to the right page. Included on every plan.
Was this page helpful?
Keep reading.
- Counting your SPF lookups (and why you might be at 11)What counts toward the 10, what does not, and how to come back under.
- Merging multiple SPF records into oneWhy two SPF records fail every sender, and how to merge them into one.
- Why 1024-bit DKIM keys are being phased outWhy 2048-bit keys, and the selector rotation that breaks no mail.