Type a domain to look for its DKIM keys at the selectors mail services use most, or type selector._domainkey.yourdomain.com to check one selector. You see each key’s type and length, and what to fix.
Free, no account needed.
How to use it
DKIM (DomainKeys Identified Mail) adds a digital signature to each email you send. The receiving server finds your public key in DNS and checks that the message was signed for your domain and not changed on the way.
A valid signature for your own domain is what lets DMARC pass when a message is forwarded, which often breaks SPF. That makes DKIM the more dependable half of email authentication.
Keys live at selector._domainkey.yourdomain.com, where the selector is a name the sending service picks, such as google, selector1 or s1. DNS has no way to list every selector, so the checker tries the names mail services use most.
If yours uses its own name, find it in the service’s DKIM settings, or in the DKIM-Signature header of an email you sent (the s= tag). Then type selector._domainkey.yourdomain.com with that name to check it.
Each key the checker finds shows its type and length, and whether it is in test mode or revoked:
The name in front of ._domainkey in the DNS record, chosen by the service that signs your mail. One domain can have many selectors, at least one for each service that sends for it.
Either the domain does not sign its mail, or it uses a selector the checker did not try. Look for s= in the DKIM-Signature header of an email from the domain, then check that selector.
Type it as selector._domainkey.domain, for example google._domainkey.github.com, and press Check DKIM.
2048-bit, where your DNS host allows it. 1024-bit keys still pass but are weaker, and most mail services let you rotate to a longer key in their settings.
Yes. The email authentication check API returns every DKIM key it finds with its type and length, takes extra selectors to try, and adds the SPF, DMARC and MX results.
Get a key and make your first call in minutes.