Looking up a DKIM key
Pick how to find the selector
Presets cover Google Workspace (google), Microsoft 365 (selector1 and selector2), a sweep of 28 common selectors, and From an email header.
Enter the domain
Type the signing domain, usually the domain in your From address. For the header option, paste the headers or just the DKIM-Signature line instead.
Run the check
Your browser asks the chosen DNS resolver for a TXT record at
selector._domainkey.domainfor each selector, six at a time.Read the figures and each key
Keys found, selectors tried, the strongest key size and the number of problems sit at the top. Each key found has a verdict, its type, size, hash and flag tags, and the raw record.
Export or keep the log
Results download as CSV or JSON, and the list of DNS requests your browser sent is shown under the result.
Example: an older Microsoft 365 key
Kilnworks (fictional) set up Microsoft 365 several years ago. The check on selector1 finds a key straight away, published directly as TXT rather than through a CNAME.
The key works, so mail still passes DKIM, but it is 1024-bit RSA. The verdict is a warning, and the fix is to rotate to a 2048-bit key in the Microsoft 365 admin centre.
Domain: kilnworks.example Selector: selector1
Keys found: 1 Selectors tried: 1 Strongest key: 1024 bits Problems: 1 selector1._domainkey.kilnworks.example Warning 1024-bit RSA. It still verifies, but 2048 bits is the current advice (M3AAWG, NIST). Key type: RSA Size: 1024 bits Hashes (h=): any Flags (t=): none
Verdicts and what to do about them
| Verdict | Meaning | Action |
|---|---|---|
| Pass | An RSA key of 2048 bits or more, or an Ed25519 key, is published | Nothing; keep the selector in your records |
| Warning: 1024-bit RSA | Verifies, but below current advice | Generate a 2048-bit key in the sending service and switch over |
| Fail: under 1024 bits | Major mailbox providers refuse it | Replace the key before sending more mail |
| Warning: revoked | The record has an empty p=, so signatures fail | Remove the selector from the sending service or publish the current key |
| Fail: unreadable key | p= is not a valid RSA public key | Check the record was not cut short or split wrongly when pasted into DNS |
| No record | Nothing published at that selector | Find the real selector in a sent message header |
Why a missing key is not proof that DKIM is missing
DNS has no way to list every name under _domainkey, so any checker can only ask about selectors it knows. Services choose their own names, often with dates or random strings in them. If the common-selector sweep finds nothing, the reliable route is the header option: send yourself a message from the service in question, open the original source and paste the headers. The tool reads every DKIM-Signature line, takes each d= domain and s= selector and looks those up exactly.
That header check also shows whether a service signs with your domain or its own. If d= is the vendor's domain, DKIM passes but does not align with your From address, so it will not help DMARC. Most sending services offer a custom domain setting that fixes this with two or three CNAME records.
Questions people ask
How do I find my DKIM selector?
Open an email you sent through the service, view the original or the message source, and find the DKIM-Signature header. The value after s= is the selector and the value after d= is the signing domain. Paste that header into this checker using the From an email header option and it will look up exactly that key.
What DKIM key length should I use?
Use 2048-bit RSA where the service allows it. 1024-bit keys still verify at most receivers, but they are below current advice and this checker marks them as a warning. Keys under 1024 bits are refused by major providers. Some DNS hosts need a 2048-bit key split into two quoted strings in one TXT record.
What does it mean when a DKIM key is published through a CNAME?
It means your DNS points the selector name at a record hosted by your sending service, for example a newsletter platform. The service holds the key and can rotate it without you editing DNS. The checker follows the CNAME and shows the final record, noting where it points.
Why does DKIM pass but DMARC still fail?
DMARC needs a DKIM pass for a domain that matches the From address, either exactly or at the organisational level. If a service signs with its own domain, DKIM passes for that domain but is not aligned with yours. Check the d= value in the header and set up the service's custom domain signing.
Where your data goes
Lookups go from your browser to Cloudflare or Google public DNS over HTTPS, and contain only selector and domain names. Pasted headers are read on the page; only the selector and domain extracted from them are queried, and the request log under the result shows each one.
Checked against the tool on