DKIM checker
Sweeps the common DKIM selectors on your domain, shows every key it finds and flags keys shorter than 2048 bits.
What the DKIM checker does
DKIM signs each outgoing message with a private key. The receiver fetches the public key from DNS at selector._domainkey.yourdomain.com and verifies the signature. If the message changed in transit or someone else signed it, the check fails.
Enter a domain and, if you know it, the selector. Without one, the checker tries about 20 common selectors, including google, selector1, selector2, k1, s1, s2, default, dkim and mail. For every key it finds it reports the key type, the key length and the tags in the record.
Finding your selector
DNS has no way to list selectors, so a sweep can only find the common ones. The reliable source is a message you sent. Open it, view the original or the source, and find the DKIM-Signature header. The s= tag is the selector and d= is the signing domain.
Google Workspace uses google by default. Microsoft 365 uses selector1 and selector2, published as CNAME records that point to Microsoft. Many sending tools use short names like k1 or s1.
If the sweep finds nothing, that doesn't prove DKIM is missing. Check a real message before you change anything.
How to read the key
- v=DKIM1 is the version. It's optional, but if present it must come first.
- k= is the key type. rsa is the default. ed25519 is defined in RFC 8463, but not every receiver verifies it.
- p= is the public key. An empty p= means the key was revoked.
- t=y marks testing mode, and RFC 6376 tells receivers to treat such mail as unsigned. Remove it once signing works.
RFC 8301 requires RSA keys of at least 1024 bits and says signers should use 2048. The checker flags 1024-bit keys. They still verify, but 2048 is the baseline today and every major provider offers it.
Why DKIM matters for cold email
DKIM survives forwarding when the message isn't changed, which SPF doesn't, and it's the authentication most sending tools can align with your domain. Gmail requires it from anyone sending around 5,000 or more messages a day to personal Gmail accounts.
For DMARC, the d= domain in the signature must match your From domain or share its organizational domain. If a tool signs with its own domain, DKIM passes and does nothing for your DMARC. Set up custom DKIM for every sending tool on every sending domain.