DKIM Checker — Validate DKIM Keys & Selectors
Enter a domain and selector to validate its DKIM public key — or leave the selector blank and we’ll try the selectors used by Google, Microsoft 365, Zoho, SendGrid, Mailgun and others.
What is DKIM?
DKIM (DomainKeys Identified Mail) adds a cryptographic signature to every message you send. The receiving server fetches your public key from DNS and verifies that the message really came from your domain and was not altered in transit.
The key lives in a TXT record at <selector>._domainkey.<domain>. The selector is a name chosen by your email provider, so one domain can have several keys — one per sending service.
google._domainkey.example.com TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqh..."
How to find your DKIM selector
- From a sent email: open the message source and find the
DKIM-Signatureheader. Thes=value is the selector,d=is the signing domain. Our email header analyzer extracts it for you. - Common selectors: Google Workspace uses
google, Microsoft 365 usesselector1andselector2, SendGrid usess1/s2, Mailchimp usesk1, Zoho useszohoorzmail. Leave the selector empty above and we’ll try these automatically.
What makes a good DKIM key
- 2048-bit RSA (or Ed25519) — 1024-bit keys still work but are considered weak; keys under 1024 bits are ignored by many receivers.
- Not revoked — an empty
p=means the key has been withdrawn and signatures with it will fail. - Out of testing mode —
t=yasks receivers to be lenient; remove it once signing works. - Aligned — for DMARC, the signing domain (
d=) must match your From domain. Check that with our DMARC checker.
DKIM record not found?
Make sure DKIM is enabled in your provider’s admin panel (Google Workspace and Microsoft 365 both require you to switch it on after publishing the record), that the record was added at the exact hostname given, and that your DNS host has not split or quoted the long key incorrectly.
Frequently asked questions
Enter your domain and the selector your provider gave you. If you don’t know the selector, leave it empty and the checker will try over 35 common selectors, or find s= in the DKIM-Signature header of an email you sent.
Use 2048-bit RSA. 1024-bit is still accepted but weak, and some receivers ignore anything shorter. If your DNS host limits TXT length, split the key into multiple quoted strings — they are joined automatically.
Common causes: signing is not enabled in the email platform, the message was modified in transit (mailing lists, footers added by a gateway), the key in DNS does not match the private key in use, or the record was pasted with extra spaces or quotes.
Yes — each sending service uses its own selector, so a domain commonly has several DKIM keys at different selector names. That is normal and encouraged.