Find and check the DKIM keys of a domain - enter a selector or let the tool try the common ones.
Last updated:
Lookups use Google Public DNS. Nothing is stored.
| Sender | Selector(s) | Where to turn it on |
|---|---|---|
| Google Workspace | Admin console → Gmail → Authenticate email | |
| Microsoft 365 | selector1, selector2 (CNAME) | Defender portal → Email authentication → DKIM |
| Mailchimp | k1, k2, k3 | Domains → Authenticate |
| SendGrid | s1, s2 (CNAME) | Settings → Sender Authentication |
| Zoho Mail | Your chosen name, often zmail | Admin Console → Domains → Email Configuration |
| Problem | Fix |
|---|---|
| No key found | Turn on DKIM in your email provider and add the record it gives |
| Empty p= | Key revoked: generate a new one |
| Record split wrongly | Paste the full value; quotes and spaces matter |
| CNAME not added | Microsoft 365 and SendGrid need CNAMEs, not TXT |
| DKIM passes but DMARC fails | The d= domain must match your From domain |
Enter your domain and selector and press Check DKIM. Without a selector, we try 26 common ones.
Open the headers of an email you sent and find s= in the DKIM-Signature line. That value is the selector.
DKIM is not turned on, or your sender uses a selector name we did not try. Enter the selector from your email headers.
Use 2048-bit if your DNS provider supports it. 1024-bit still works but is weaker.
Yes. Each sender can have its own selector and key.
No. DMARC uses DKIM and SPF results to decide what to do with spoofed mail.