Rotating a signing key
Check publication for the new selector while preserving the old selector as required by your mail service.
Enter a domain and DKIM selector to look up the public key record at selector._domainkey.domain.
DKIM records are stored beneath a selector-specific DNS name. For example, a selector named google on example.com is published at google._domainkey.example.com. The selector is normally visible in the DKIM-Signature header of a signed email.
EmailValidly performs a DNS TXT lookup for the exact selector and domain you provide. It reports the published record if one is available. It does not infer or brute-force selectors.
A DKIM public record is published under a selector-specific DNS name. You need both the signing domain and selector. The lookup checks publication, not the cryptographic signature on a message.

Read the signing domain and selector from a DKIM-Signature header or your provider’s setup page.
The queried name is selector._domainkey.domain. A guessed selector can return nothing even when another selector works.
An empty public-key tag can indicate revocation. Validate a real message separately.
Illustrative scenarios, not live results for the addresses or records shown. Open a scenario to see the next action.
The lookup name is mail2026._domainkey.example.com.
Next action Enter mail2026 and example.com separately.
The published record has no public key material.
Next action Confirm whether the selector was retired.
The domain may use a different selector.
Next action Copy the selector from an actual signature.
Check publication for the new selector while preserving the old selector as required by your mail service.
Rule out an incorrect selector or missing record before investigating message modification.
No. DNS does not offer a general list of all DKIM selectors.
No. Signature verification also needs the message, signature fields and canonicalisation rules.
No. This form only needs a domain and selector.