Skip to content
DMARC Pulse

DKIM record check

DKIM Checker: Find Your DKIM Selector

Enter a domain and your DKIM selector to validate the key. If you don’t know the selector, leave it empty and we scan the ones common providers use.

Example result

Sample data, not a live check. Run the tool above to see your own result.

Result for

acme.example

Looks good

google · 2048 s1 · 2048

google._domainkey.acme.example

Key type
rsa
Key size
2048 bits
Likely provider
Google Workspace
google._domainkeyTXT
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsGh8DshKeDeJEMzPyHjexRYwoSykX2cPrzUsRassgV6Vi9Iyr+8Q4a13/z1Z/L+ztRSiJjNNejxwPZrmaagTC8AFtFbtTAvmolCSyHtcVv77IdrBI8+qUED7YJTtwf5Npvm3idj/WhxukUOxT8ykIAo6atogY/5cp745YUZJ+fsFzWRQU7Sj+YB/WLZoE6XTxFp7XwVfvPM2sERB2iMxk/5iFUuzkKr1SU6apTgQKbxAUsVU9MHEI6ukk4Oe1ql4Lkgsfztx9xn3qviaZRMGZ5ny14ecU/FYvyOzjLRHDf0d8uCT5ceogKd0UIvNodi+WFHeqLBrtiIZKaGJh0PVpwIDAQAB
  • 2048-bit RSA key (google)

    Strong key length.

s1._domainkey.acme.example

Key type
rsa
Key size
2048 bits
Likely provider
SendGrid
s1._domainkeyTXT
k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsGh8DshKeDeJEMzPyHjexRYwoSykX2cPrzUsRassgV6Vi9Iyr+8Q4a13/z1Z/L+ztRSiJjNNejxwPZrmaagTC8AFtFbtTAvmolCSyHtcVv77IdrBI8+qUED7YJTtwf5Npvm3idj/WhxukUOxT8ykIAo6atogY/5cp745YUZJ+fsFzWRQU7Sj+YB/WLZoE6XTxFp7XwVfvPM2sERB2iMxk/5iFUuzkKr1SU6apTgQKbxAUsVU9MHEI6ukk4Oe1ql4Lkgsfztx9xn3qviaZRMGZ5ny14ecU/FYvyOzjLRHDf0d8uCT5ceogKd0UIvNodi+WFHeqLBrtiIZKaGJh0PVpwIDAQAB
  • 2048-bit RSA key (s1)

    Strong key length.

Selectors tested (94)
google selector1 selector2 default dkim mail k1 k2 s1 s2 smtp mandrill mxvault zoho pm mailjet sig1 fm1 protonmail everlytickey1 hs1 kl scph0123 dk zendesk1 shopify locaweb fm2 fm3 protonmail2 protonmail3 secureserver1 secureserver2 hostingermail-a hostingermail-b hostingermail-c emkt mte1 mte2 brevo1 brevo2 m1 pdk1 pdk2 acdkim1 acdkim2 hs2 sf1 sf2 zendesk2 fd fd2 shopify2 km1 km2 km3 km4 kt1 kt2 ks1 ks2 kl1 kl2 mtd rdstation rd aweber_key_a aweber_key_b aweber_key_c cm cf-bounce cf2024-1 ctct1 ctct2 cio api gor gor2 strong1 strong2 intercom s1-ionos s2-ionos s42582890 cka litesrv ms1 ms2 privateemail pem perfit resend squarespace pro

What to do with the result

The key is RSA with 2048 bits or more, or Ed25519

The public key is in DNS and readable. This check reads DNS only, so it cannot confirm that your mail uses this key. Send a test message to a mailbox on another service and open its full headers. Use the receiving provider’s dkim=pass result and read d= in the corresponding DKIM-Signature. header.i= may help identify the signature, but DMARC aligns its signing domain, not that identity. DMARC counts DKIM only when the signing domain aligns with your From domain. If DMARC is on p=none (monitoring only), stay there until reports show every legitimate sender passing.

The likely provider is a guess based on the selector, the name that identifies this key. With Ed25519, also sign with RSA under a second selector.

The key has between 1024 and 2047 bits

Receivers can still verify this key. RFC 8301 requires at least 1024 bits and recommends 2048 or more, so plan a rotation, which means replacing the key. Create a 2048-bit key under a new selector, publish it, and switch signing only after this tool finds it. Keep the old record for several days, because a sending server may retry a message for four or five days. Overwriting the key on the same selector makes those messages fail. In Microsoft 365, run Rotate-DkimSigningConfig -Identity example.com -KeySize 2048 and allow four days (96 hours). This upgrades only the selector that becomes active, so run the command again after that rotation to upgrade the other selector. A 2048-bit key exceeds 255 characters, so it may need several strings in one TXT record.

The scan found no key on the common selectors

This result is inconclusive. DNS cannot list a domain’s selectors, so the tool only tries common names, and your provider may use another. Take the s= value from a real signed message and test it here.

If the message has no DKIM-Signature header, or its d= shows your provider’s domain, set up DKIM for your own domain in that service. Publish the record it gives you first, then turn signing on. A temporary DNS failure shows this same result, and results are reused for 15 minutes, so wait and repeat the check before you change anything.

No key exists at the selector you entered

No TXT record answered at selector._domainkey.example.com. A receiver that gets this answer must fail any signature that uses the selector. Copy the name exactly as your provider shows it. Some DNS hosts add your domain to the end automatically, which creates selector._domainkey.example.com.example.com, so enter only the part they ask for. Microsoft 365 uses CNAME records here, so follow the record type your provider gives. A new record can take time to appear, and a temporary DNS failure shows this same result. Results are reused for 15 minutes, so wait and check again before you change anything.

The record exists, but the tool flags a problem

Read the message under the record and apply the matching fix.

  • Under 1024 bits: RFC 8301 forbids accepting these signatures. Move to a 2048-bit key under a new selector.
  • Unreadable key, wrong v= or unknown k=: compare the record with your provider’s value and publish it again exactly.
  • Empty p=: the key is revoked and its signatures fail. If you retired this selector on purpose, leave it. If a service still signs with it, move that service to a new selector.
  • t=y: testing mode. Remove it once headers show dkim=pass.
  • h=sha1 alone: RFC 8301 forbids SHA-1, and this tag makes rsa-sha256 signatures fail. Remove the tag first, because a record without h= accepts any hash. Then confirm that a= in your signatures ends in sha256.

Explained

How DKIM works

Your email service signs each message with a private key. Receivers fetch the matching public key from DNS at <selector>._domainkey.<domain> and verify the signature. If the signing domain (d=) matches your From domain, DKIM counts towards DMARC.

How to find your DKIM selector

The DKIM selector is the value of the s= tag in the DKIM-Signature header (RFC 6376). A domain can have several selectors, one per key, and receivers use it to know which public key to fetch. To read yours from a received message:

  1. Send an email from your domain to a mailbox on another service, because the copy in your Sent folder may not carry the signature.
  2. Open the message where it arrived and show its full headers (in Gmail: ⋮ → Show original).
  3. Find DKIM-Signature. The value after s= is the selector and the value after d= is the signing domain. If there are several signatures, use the one whose d= is your domain.

For example, d=example.com; s=google means the public key is at google._domainkey.example.com. If the message has no DKIM-Signature header, it arrived unsigned. Typical selectors: google (Google Workspace), selector1/selector2 (Microsoft 365), k1 (Mailchimp), s1/s2 (SendGrid).

Frequently asked questions

How do I check my DKIM record?
Enter your domain and selector above. Without a selector we test the most common ones, but only the selector your provider uses can confirm DKIM is set up.
What key length should I use?
2048-bit RSA. 1024 bits is still accepted but considered weak; keys under 1024 bits are rejected by major providers.
Why does DKIM fail even though the record exists?
Common causes: the key in DNS doesn’t match the one used to sign, the record is truncated, or the message was modified in transit (for example by a mailing list adding a footer).
Can I have several DKIM keys?
Yes. Each service uses its own selector, so you can have one key per sending service and rotate them independently.

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.

Related tools