How to fix: DKIM selector published with an empty (revoked) key
A DKIM selector record has an empty p= tag, which RFC 6376 defines as a revoked key. Every signature made with that selector therefore fails verification.
Why it matters
Any mail still signed with this selector fails DKIM verification at every receiver. Under a DMARC policy of quarantine or reject, with SPF not aligned, that mail is discarded rather than delivered. Because the selector is chosen by the signing system rather than by DNS, the symptom is unexplained delivery failure from one particular sending path.
Revoking a selector by emptying p= is the correct way to retire a key, and a revoked selector left in place is normally harmless. It is worth checking because both routes to this state look identical in DNS: a deliberate retirement, and a signing service still using a selector it was supposed to stop using. The DKIM-Signature header's s= tag on a received message tells you which selector is actually in use.
How to fix it
- 1Confirm nothing still signs with this selector, then delete the record rather than leaving an empty key published.
- 2If mail is still being signed with it, publish the current public key or repoint the signer at an active selector.
- 3Check the s= tag in a recent message's DKIM-Signature header to see which selector the signer is really using.
Code examples
Find the selector in use
# In a received message's headers:
# DKIM-Signature: v=1; a=rsa-sha256; d=example.com; s=selector1; ...
dig +short TXT selector1._domainkey.example.comReferences
Detected automatically by VulnRadar. The check id is email-dkim-revoked-key, stable across every scan so you can filter or diff on it.
More email checks
- LowDMARC Forensic Report URI (ruf=) Missing
- MediumDMARC Aggregate Report URI (rua=) Missing
- MediumMTA-STS (SMTP Strict Transport Security)
- LowTLS-RPT Record Missing rua= Reporting URI
- HighSPF Exceeds 10 DNS Lookup Limit
- HighSPF Redirect Loop
- LowDMARC pct= Below 100
- MediumDMARC Policy Set to Monitor-Only (p=none)
Questions
- How severe is DKIM selector published with an empty (revoked) key?
- VulnRadar rates this low severity in the email category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id email-dkim-revoked-key, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does DKIM selector published with an empty (revoked) key map to?
- It maps to CWE-16. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.