Runs in your browser
DKIM record checker
Find the DKIM keys a domain publishes and check their length. It tries 40 commonly used selectors, including the defaults of major mail services, plus any you enter, straight from your browser.
Check a domain
How DKIM keys are found
- A DKIM public key is a TXT record at
<selector>._domainkey.<domain>(RFC 6376). The selector is chosen by whoever sends the mail, so no tool can list every key a domain has. - Your selector is in the
s=tag of the DKIM-Signature header of any message the domain sent. Enter it above if the sweep finds nothing. - Gmail and Yahoo require RSA keys of at least 1024 bits (sender requirements); RFC 8301 says signers should use at least 2048. An empty
p=means the key was revoked, which is normal for a retired key. - Lookups go from your browser to Cloudflare’s public DNS-over-HTTPS service; MyIPScan does not see the domain you check.
Reading the result
- Good: an RSA key longer than 1024 bits, or an Ed25519 key.
- Review, 1024-bit RSA: accepted by Gmail and Yahoo, but below the 2048 bits RFC 8301 asks signers to use.
- Review, revoked key: the record has an empty
p=. Fine for a retired selector, a problem if mail is still signed with it. - Problem: an RSA key under 1024 bits. RFC 8301 says receivers must treat its signatures as invalid.
t=yin the note: the domain is testing DKIM, and RFC 6376 tells receivers to treat its mail as unsigned.- Wildcard: a record at
*._domainkeyanswers every selector name. The checker asks a random name first and lists only selectors whose record differs from that answer.
Common mistakes
- Leaving
t=yin the record after signing works: RFC 6376 tells receivers to treat the mail as unsigned. - Revoking the old key before the sending service has moved to the new selector: signatures made with the old key then fail.
- Publishing only an Ed25519 key: a receiver that does not support Ed25519 sees no valid signature. RFC 8463 lets signers add an RSA signature under a second selector for that.
- Typing the full name into a DNS panel that adds the domain itself, which creates
s1._domainkey.example.com.example.com. Enters1._domainkeythere.
What this check cannot tell you
- It reads published keys only. Whether mail is actually signed, and passes, shows in the
Authentication-Resultsheader of a received message (dkim=pass). - Key length is worked out from the size of the published key; a key of an unusual size gets an estimate.
- When some lookups fail, the result says how many and calls itself incomplete. Run it again.
- Answers come through Cloudflare’s resolver, which may hold a cached answer: a key published or changed minutes ago can appear only once that cached answer expires.