DKIM Checker
Type a domain, and its selector if you know it, to see its DKIM public keys: the TXT records at <selector>._domainkey.<domain> that receivers use to verify the signature on its mail. DNS cannot list a domain's selectors, so with none given the checker tries 22 common ones at once (google for Google Workspace, selector1 and selector2 for Microsoft 365, s1 and s2 for SendGrid, k1 for Mailchimp, fm1 to fm3 for Fastmail, protonmail for Proton and more) and reads every key it finds: RSA or Ed25519, its size in bits, and whether it is revoked (an empty p=). On 6 November 2026 it found 6 keys on github.com and none of the 22 on amazon.com: a miss only means a domain's selectors are not common ones.
The selector is optional: leave it empty to try 22 common ones. Free, no sign-in, 20 lookups a minute. Answers are cached for 5 minutes. Also: DNS lookup, MX lookup, Nameserver lookup, TXT record lookup, SPF record checker, DMARC checker, CNAME lookup, DNS propagation checker, reverse DNS lookup, MTA-STS checker, BIMI checker, email deliverability checker.
DKIM keys on well-known domains
Looked up on November 6, 2026 through Cloudflare's resolver, the same one this tool asks. Click a domain to run it live.
| Domain | Keys found (selector, size) | Findings |
|---|---|---|
| github.com | google 2048, selector1 1024, k1 1024, k2 2048, s1 2048, s2 2048 | 1024-bit key |
| stripe.com | google 1024, s1 1024, s2 1024, mandrill 1024 | 1024-bit key |
| microsoft.com | selector2 1024 | 1024-bit key |
| fastmail.com | fm1 revoked, fm2 revoked, fm3 2048 | revoked key |
| proton.me | protonmail 2048, protonmail2 2048 | none |
| amazon.com | none of 22 | none of 22 common |
22 common selectors tried for each domain. github.com signs through Google Workspace, Microsoft 365, Mailchimp (k1, k2) and SendGrid (s1, s2); Microsoft only had selector2 live. A miss, like amazon.com's, means its selectors are not common ones, not that it lacks DKIM.
DKIM Checker questions
How do I find a domain's DKIM selector?
Open a message it sent and view the original (Show original in Gmail): the DKIM-Signature header carries s=, the selector, and d=, the signing domain, so s=google; d=example.com means the key lives at google._domainkey.example.com. No DNS query lists a domain's selectors, which is why a checker can only try common ones. Each sending service uses its own, so a domain on Google Workspace, SendGrid and Mailchimp has at least three.
Is a 1024-bit DKIM key still safe?
It is still accepted. RFC 8301 (2018) tells receivers to verify RSA keys from 1024 to 4096 bits and to treat anything smaller as invalid, and tells signers to use at least 2048. On 6 November 2026 all four keys found on stripe.com and the one on microsoft.com were 1024-bit, while proton.me's were 2048. Use 2048 for a new key; if your DNS host limits a TXT string to 255 characters, split the key into several strings in the same record.
What does an empty p= in a DKIM record mean?
The key is revoked (RFC 6376 3.6.1): every signature made with that selector now fails. Providers leave revoked selectors in place while they rotate keys, so mail signed with a retired key fails cleanly instead of verifying. On 6 November 2026 fastmail.com's fm1 and fm2 were revoked and fm3 held its live 2048-bit key.
Why is my DKIM selector a CNAME?
So the email provider can rotate the key without you editing DNS. Microsoft 365 has you point selector1._domainkey and selector2._domainkey at records under your onmicrosoft.com domain and switches between them; SendGrid, Mailchimp, Fastmail and Proton work the same way. github.com's s1 and s2 were CNAMEs to sendgrid.net and its k1 and k2 to Mailchimp's mcsv.net on 6 November 2026. The checker follows the CNAME and shows where each key really lives.
More free domain tools
The DNS lookup shows every record a domain publishes. The MX lookup shows which servers take a domain's email and who runs them. The Nameserver lookup shows a domain's nameservers and which company hosts its DNS. The TXT record lookup reads a domain's SPF and DMARC records. The SPF record checker validates a domain's SPF record and counts its DNS lookups against the limit of 10. The DMARC checker reads a domain's DMARC policy, reports and alignment, and flags what weakens it. The CNAME lookup follows a hostname's CNAME chain to its final address and spots dangling records. The DNS propagation checker shows whether 15 resolvers around the world return the same answer after a change. The reverse DNS lookup finds the hostname (PTR record) behind an IP address and checks that it resolves back. The MTA-STS checker fetches a domain's MTA-STS policy and checks that it covers every mail server. The BIMI checker checks a domain's BIMI record, SVG Tiny PS logo, mark certificate and whether DMARC lets the logo show. The email deliverability checker runs every DNS check that decides whether a domain's mail is trusted, with the failures first. For the website itself, the redirect checker follows a URL through every 301, 302, 307 and 308 to the page that answers, the HTTP header checker shows the response headers a URL sends and grades its six security headers and the website down checker checks from outside your network whether a site answers, and how fast. For who registered a name and when, use the WHOIS lookup, Domain age checker or Domain expiration checker. See which extensions a name is still free in with the domain availability checker, or price one in the domain value calculator.