DKIM selector finder

Find a domain's DKIM keys by trying 31 common selectors from Google, Microsoft 365, mailbox.org and the large email services, with the key type and size of each.

Free, no account. The domain is kept only in a short cache.

Run the full email security check DMARC, SPF, DKIM, MX and MTA-STS in one free report.

How it works

A DKIM public key lives in DNS at SELECTOR._domainkey.DOMAIN, and you have to know the selector to find it. DNS has no way to list the names under _domainkey, so the finder tries a fixed list of 31 selectors that mail providers and mail software commonly use, one passive DNS lookup each:

  • Google Workspace: google.
  • Microsoft 365: selector1 and selector2.
  • Mailchimp and Mandrill: k1, k2, k3 and mandrill.
  • SendGrid: s1, s2 and smtpapi.
  • Mailgun: mailo and mg.
  • Zoho: zoho and zmail.
  • Proton: protonmail, protonmail2 and protonmail3.
  • Fastmail: fm1, fm2 and fm3.
  • mailbox.org: mbo0001, mbo0002, mbo0003 and mbo0004.
  • Mailjet: mailjet. Amazon SES: the older fixed name amazonses.
  • Generic names: default, dkim, mail, smtp and sig1.

This is the same discovery the email security check runs. Every key that is found is checked with the same rules as the DKIM record check: the tags of the record, the key type, the RSA key size read from the key itself, a revoked key with an empty p= tag, testing mode (t=y) and more than one record under a selector. The result lists each selector that has a key, with its key type and size, and the findings for it.

A hint, not a verdict

The result is a hint about which providers sign for the domain. Finding no key is information, never a warning, because a domain can sign with selectors that are not on the list. Amazon SES Easy DKIM, for example, uses random selector names. Finding a key also does not prove that current mail is signed with it: old keys are often left in DNS.

To find the selector a sender really uses, open a message from the domain and read the s= tag in its DKIM-Signature header. The d= tag next to it is the signing domain.

Common mistakes

  • Short keys left in place. A key under 1024 bits is not accepted at all, and a 1024-bit key from years ago is the bare minimum. Rotate to 2048 bits.
  • Testing mode forgotten. t=y tells receivers to treat failures as if the message were unsigned. Remove it once signing works.
  • Two records under one selector. Receivers cannot tell which key is meant, and verification fails.
  • A key published but never used. DKIM only helps when the provider actually signs with your domain in d=. Check that the signature aligns with the From domain, or DMARC will not count it.
  • Old keys kept after a provider change. Remove keys for services you no longer use, or revoke them with an empty p=.

The DKIM guide explains selectors, key rotation and alignment.

Limitations

  • Only the 31 listed selectors are tried. Selectors outside the list are never found.
  • Signatures in messages are not verified.
  • When you know the selector, the DKIM record check checks exactly that one.

Use it from code

The same check is available as an API: $0.02 per check. See the API reference.

curl -i "https://api.lookproof.dev/v1/mail/dkim-discover?domain=example.com"

A request without payment is answered with 402 Payment Required and the exact price.

Frequently asked questions

Why can't the tool list all DKIM selectors of a domain?

DNS has no way to list the names under _domainkey. A key can only be found if you ask for its exact name, and the selector part of that name is chosen freely by whoever signs the mail. The tool can only try names that are commonly used.

No selectors were found. Does my domain lack DKIM?

Not necessarily. The result DKIM_NO_COMMON_SELECTORS only says that none of the names on the list has a key. Many providers use selectors with random or customer-specific names, which this tool cannot guess. Look at the s= tag in the DKIM-Signature header of a message from the domain to find the real selector.

Which selectors are tried?

A fixed list of 31: default, dkim, mail, smtp, sig1, s1, s2, k1, k2, k3, google, selector1, selector2, mandrill, smtpapi, mailo, mg, zoho, zmail, protonmail, protonmail2, protonmail3, fm1, fm2, fm3, mbo0001, mbo0002, mbo0003, mbo0004, mailjet and amazonses. The same list is used every time, so results can be compared.

What is checked for a key that is found?

The same as in the DKIM record check: the tags of the record, the key type, the RSA key size read from the key itself, a revoked key with an empty p tag, testing mode and multiple records under one selector.

How long should a DKIM key be?

Use RSA with 2048 bits, or Ed25519 next to an RSA key. RFC 8301 says verifiers must not accept RSA keys shorter than 1024 bits, and the full check reports those as DKIM_WEAK_KEY. A 1024-bit key still verifies, but it is the minimum, and most providers now offer 2048 bits. The finder reads the size from the key itself, not from a tag.

Is the domain stored?

No. Results are kept in memory for up to ten minutes so repeated lookups are fast, and are then gone. The domain is not written to logs and no account is needed.