Topic · Authentication
DKIM selector
A DKIM selector identifies the DNS public key used to validate a particular signature.
How it works
The s= value in the signature selects selector._domainkey under the d= signing domain.
What can go wrong
An absent or mismatched selector makes verification fail even if another selector exists.
What to check or do
Check the exact d=/s= combination and rotate keys without disrupting senders.
Practical scenario
A company uses one selector for its marketing platform and another for support. During migration, the old TXT key is removed before queued messages have been delivered, and late arrivals fail DKIM verification.
Verification checklist
- Confirm the selector in the signed message matches the queried DNS name.
- Publish a new selector before moving active signers.
- Allow planned overlap for queued and delayed mail.
- Remove retired keys only after delivery risk has been considered.
How to investigate DKIM selector
- Signal to investigate
- One sender works while another fails DKIM because each service signs with a different selector.
- Evidence to collect
- Extract d= and s= from the actual DKIM-Signature header and query that selector's DNS name.
- Common wrong conclusion
- Guessing common selector names is only discovery, not verification of the selector on the failing message.
How to interpret the evidence
The selector is taken from the message's DKIM-Signature s= value and combined with d= to build the DNS public-key lookup name. Different services, accounts and rotation generations may use different selectors at the same domain. Checking one familiar key therefore does not establish that every live sender is correctly configured.
What to change and how to verify it
Collect examples from each sending service, enumerate live d=/s= pairs and verify their DNS keys. Maintain old selectors during expected queue and cache windows. Decommission only after no production stream depends on the previous private key.
dig +short TXT selector1._domainkey.example.comEducational example; not validated against your live infrastructure.Put this into practice
Run a focused check, then explore protection if your domain needs it.