Free tool · DKIM checker

Check your DKIM record

Enter a domain and, if you know it, the selector from one of your emails. The checker looks up the public key in DNS and says whether it is published or revoked. SPF, DMARC and MX are checked too.

01What it checks

A public key, at a name only the sender knows.

Your provider signs each email with a private key. Receivers fetch the matching public key from DNS and check the signature. To find that key, you need its selector.

s=

The selector

Every DKIM-Signature header carries s= (the selector) and d= (the signing domain). Together they name the key. A domain can publish many keys, one per provider or per rotation, each under its own selector.

_domainkey

Where the key lives

The public key is a TXT record at <selector>._domainkey.<domain>, or a CNAME to your provider's copy. It reads v=DKIM1; k=rsa; p=<key>. An empty p= means the key is revoked and mail signed with it fails.

Key size

1024 or 2048-bit RSA

1024-bit RSA keys still validate, but 2048 bits is the current recommendation and Google Workspace's default. A 2048-bit key is too long for one 255-character TXT string, so DNS splits it into several; that is normal.

Selectors

Why some have to be typed in

DNS cannot list the selectors a domain uses. The checker tries the common ones (google, selector1, selector2, k1, s1, mail, ovh and more). Amazon SES, Resend and many platforms use their own or random selectors: enter the s= value from one of your emails.

Read more: SPF, DKIM and DMARC explained · DKIM key rotation

02Questions

What people ask.

How do I find my DKIM selector?
Open an email you sent and look at its headers. In Gmail: the three-dot menu, then “Show original”. In Outlook: File, then Properties, or “View message source” on the web. Find the DKIM-Signature line; the selector is the value after s=, and the signing domain is the value after d=.
What selectors do the common providers use?
Google Workspace uses google by default. Microsoft 365 uses selector1 and selector2. OVH mail hosting typically uses ovh-prefixed selectors. Amazon SES Easy DKIM publishes three random tokens per domain, and Resend uses resend. When in doubt, read s= in a sent message.
Why does DKIM say “unknown”?
None of the common selectors answered, and DKIM keys can't be listed from DNS. That does not mean DKIM is missing: enter the selector from one of your emails and the checker looks it up directly.
The key is published but DKIM still fails. Why?
Common causes: the key in DNS doesn't match the one your provider signs with (an old key after a rotation), the record was pasted with extra quotes or line breaks, or something modified the message after signing, like a mailing list footer or a gateway rewriting links.
Should I use a 1024-bit or a 2048-bit key?
2048-bit, if your DNS host accepts long TXT records (almost all do, by splitting the value into strings). 1024-bit keys still pass today, but they are the weaker option and some providers already default to 2048.
03Go further

Related pages.

04Free tools

More free tools.

Deliverability, handled

Records right. Domain warmed. Then send.

Mailbase writes SPF, DKIM, DMARC and the reply MX when you add or buy a domain, then raises its volume only while real bounces and complaints stay low.