How to fix: DKIM selector published in testing mode
A DKIM selector record carries the t=y flag, which marks the domain as still testing DKIM. It tells receivers not to treat a verification failure any differently from unsigned mail.
Why it matters
t=y asks receivers to disregard DKIM failures for this selector, so a forged message that fails signature verification is handled exactly like one that was never signed. Where DMARC alignment depends on DKIM, that removes the DKIM half of the policy for every message signed with this selector, and it does so silently, because the record otherwise looks fully configured.
The flag exists for the deployment window, while you confirm signing works end to end without risking legitimate mail. It is meant to be removed once that is confirmed, and very often is not, because nothing breaks when it stays. RFC 6376 defines t=y for exactly this purpose and expects it to be temporary.
How to fix it
- 1Confirm signatures are verifying, using DMARC aggregate reports or a test send to a verifying receiver.
- 2Remove the t=y flag from the selector record once that is confirmed.
- 3Check every selector, not just the one reported: providers commonly publish two for rotation.
Code examples
Record with the testing flag removed
default._domainkey.example.com. IN TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A..."Check a selector
dig +short TXT default._domainkey.example.comReferences
Detected automatically by VulnRadar. The check id is email-dkim-testing-mode, 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 in testing mode?
- 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-testing-mode, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does DKIM selector published in testing mode 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.