This free DKIM checker finds your key without you knowing the selector.

We try 51 common selectors, read the key length and tell you if the key is missing, switched off or too short. Type your selector if you use a custom one.

Works with a domain or a full email address. Leave the selector empty and we try the common ones; your selector is the s= value in the DKIM-Signature header of an email you sent.

Example report for trynorthpeak.example, a made-up new cold email domain

3 of 5 checks pass. Fix SPF first: until SPF passes, this domain falls short of the rules Gmail, Yahoo and Outlook set for bulk senders.

Found after trying 51 selectors. A receiving server uses this key to confirm that a message was signed by trynorthpeak.example and was not changed on the way.

What we found
google._domainkey.trynorthpeak.example
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzKOft5vv4mpU+bydtDHpqr/LqGEOqrochaCIpas8jTYkTibVj9ggftl4plPyRGihx0mb+Ny7mwpDLNZYiA4Lkofm+m5mSVul9IdnRBUvhrVvHwVT7S3zuy6CpyNOtp0XoKM12269bkW9uQ0gVQ6F2gs76dq/b3jY4hbAPAupkxfFw3jWnoIHMdTepTsEmTVhiR/1AzrYzrbCq471oFDX7v1QKNdE2Pl9YEANGzOM4GYSsn2S4cvJXsjERBr1RnnEBxHEmtThHCRow66FXx7PkUVPeOBqCGgW3S6mlfJ65jSeL3Q+T4+cPYto9mzkEGncaL8nLptCDH2NF2/nd1++ewIDAQAB
Keys found after trying 51 selectors
SelectorKeyUsually set by
google._domainkey2048-bit RSAGoogle Workspace
Also checked for trynorthpeak.example

Once your records pass, warm up the mailbox and start sending with Emailchaser.

Emailchaser warms up each mailbox on its own, then sends your campaign and its follow-ups from the domain you just checked.

Start my free trial7-day free trial, $0 today

The check runs on our server against live DNS and 16 public blocklists (3 for domains, 13 for mail server IPs). A list that does not answer is never counted as clean. Nothing you type is stored.

Each DKIM result means one thing, and each has one fix.

The checker gives one line for your DKIM key. Find that line below to see what receivers do with it and what to change. When you run a check, the row that matches your result is marked.

What the checker showsWhat it meansWhat to do
A 2048-bit or longer key is publishedYour result in the exampleReceivers can verify your signatures, and the key is as long as Google recommends.Nothing to fix. Rotate the key once a year or so by publishing a new selector first.
A 1024-bit key, shorter than the 2048 bits Google recommendsIt works today, and Gmail and Yahoo accept 1024 bits or more.Generate a 2048-bit key the next time you rotate.
A key shorter than 1024 bitsGmail ignores it, so your mail counts as unsigned.Generate a new 2048-bit key at your email provider and publish it.
The key is empty or switched offA record with nothing after p= tells receivers that mail signed with that selector should fail.Publish the key again from your provider's settings, or stop signing with that selector.
The key is damaged or of a type receivers cannot readMail signed with it fails DKIM. A key cut off while pasting is the usual cause.Copy the record again from your provider, in one piece, and publish it.
No key found at the selector you typedNothing is published under that name, or the name is spelled differently in your DKIM-Signature header.Open an email you sent, show the original, and copy the s= value exactly.
No key found, including your provider's defaultDKIM is off, or it uses a custom selector. Mail signed with your provider's own key does not count for DMARC.Switch DKIM on at your provider, or type your selector next to the domain.

DKIM keys are private to each domain, so here is the DMARC enforcement they make possible at 13,511 listed companies.

DKIM keys sit under selector names that only each domain's owner knows, so a miss in a bulk read could mean no DKIM or a custom name, and the study does not count them. What DKIM exists to enable can be read exactly: DMARC enforcement, which needs a DKIM or SPF pass that matches your From domain. On 18 October 2026, 48.4% of the 13,511 companies enforced it.

How the example domain compares, so you can see what your own result will show.

Your DMARC policy

p=none

24.4% of the 13,511 companies are at p=none, and 48.4% enforce DMARC with quarantine or reject.

SPF record

More than one

0.6% of the 13,511 companies publish two or more, which receivers treat as none.

DMARC on your provider

Google Workspace

44.6% of them enforce DMARC. Across all 13,511 companies it is 48.4%.

DMARC policy of 13,511 company domains, October 2026
  • p=reject: receivers refuse failing mail3,75427.8%
  • p=quarantine: receivers send failing mail to spam2,78220.6%
  • p=none: reports only, delivery unchanged3,30324.4%
  • A record receivers cannot read270.2%
  • No DMARC record3,64527.0%
Share of domains that enforce DMARC, by who handles their mail
  • Microsoft 3654,421 domains57.9%
  • Google WorkspaceYour domain1,302 domains44.6%
  • A security gateway in front of the mailbox2,526 domains74.0%
  • Another host or their own server4,108 domains32.3%

All 13,511 domains: 48.4%

Companies on Microsoft 365 and on Google Workspace set these records differently.

Where the mail is handledDomainsEnforce DMARCAt p=rejectNo DMARC record
Microsoft 3654,42157.9%30.7%16.9%
Google Workspace1,30244.6%23.7%22.0%
A security gateway in front of the mailbox2,52674.0%52.5%4.9%
Another host or their own server4,10832.3%14.3%38.6%

Google Workspace and Microsoft 365 both sign with a key of their own until you switch on DKIM for your domain. Of their companies, 44.6% and 57.9% enforce DMARC, against 74.0% behind a security gateway. These are large listed companies, not cold email domains, so read the numbers as the standard the people you email already meet, not as a target for your own setup.

Source: Emailchaser DMARC adoption study, 13,511 company domains with a stock exchange listing, read from public DNS on 18 October 2026. See the full study and its data.

A receiver checks your DKIM signature in four steps.

DKIM proves that your domain signed the message and that nobody changed it on the way.

  1. Your server signs

    It signs the message with a private key and adds a DKIM-Signature header.

  2. The header names a key

    It carries your domain in d= and the selector in s=, for example google.

  3. The receiver fetches the key

    It looks up the selector under _domainkey on your domain in DNS and reads the public key.

  4. The signature is checked

    If it matches the message, DKIM passes. If the key is missing or wrong, it fails.

Publish a DKIM key as a TXT or CNAME record under your selector.

Your email provider generates the key. You only publish what it shows you, under the selector it names.

  1. Generate the key in your email provider's admin settings, and choose 2048 bits if it asks.
  2. Add the record it shows, at the host selector._domainkey. Google uses the selector google, and Microsoft uses selector1 and selector2.
  3. Wait for DNS to update, then switch signing on in the provider's settings.
  4. Run the check above. A provider's own default selector is tried first when your MX records point at it.

These are the two records most cold email domains publish.

Google WorkspaceType TXT, host google._domainkey
v=DKIM1; k=rsa; p=PASTE_THE_2048_BIT_PUBLIC_KEY_FROM_THE_ADMIN_CONSOLE

In the Admin console, open Apps, Google Workspace, Gmail, Authenticate email, generate the record, publish it, then press Start authentication.

Microsoft 365, first recordType CNAME, host selector1._domainkey
selector1-yourdomain-com._domainkey.yourtenant.onmicrosoft.com

Replace yourdomain-com with your domain, dots turned into dashes, and yourtenant with your Microsoft 365 tenant name.

Microsoft 365, second recordType CNAME, host selector2._domainkey
selector2-yourdomain-com._domainkey.yourtenant.onmicrosoft.com

Publish both records. Microsoft rotates between them.

A DKIM key lives under a name that only your email provider chose.

DKIM proves two things about a message: that your domain signed it, and that nobody changed it on the way. The sending server signs each message with a private key. The matching public key sits in your DNS at selector._domainkey.yourdomain.com, and the receiving server looks it up to check the signature.

The catch is the selector. Nothing in DNS says which one a domain uses, so a checker has to guess, and most checkers make you type it. Ours tries the 51 names providers use by default, the same list the Emailchaser app uses when it checks a sending domain's DNS, and reports every key it finds.

If your provider picked a name nobody could guess (some self-hosted servers use a random string), type it next to the domain. You will find it in the s= value of the DKIM-Signature header of any email you sent: open the message, show the original or the headers, and look for s=.

These are the 51 selectors we try, and who uses each one by default.

ProviderSelectors
Google Workspacegoogle
Microsoft 365selector1, selector2
Shared by many hosts and control panelsdefault, dkim, mail, smtp, mx
Mailchimp and Mailgunk1
Mailchimpk2, k3
SendGrids1, s2
Mandrillmandrill
Mailjetmailjet
Postmarkpm
Resendresend
Zoho Mailzmail, zoho
Fastmailfm1, fm2, fm3
Proton Mailprotonmail, protonmail2, protonmail3
iCloud Mailsig1
IONOSs1-ionos, s2-ionos
Hostingerhostingermail-a, hostingermail-b, hostingermail-c
Titantitan1
Migadukey1, key2, key3
Gandigm1, gm2, gm3
mailbox.orgmbo0001, mbo0002
Purelymailpurelymail1, purelymail2
MXroutex
Brevobrevo1, brevo2
MailerLitelitesrv, ml
Klaviyokl, kl2
Constant Contactctct1, ctct2

The same list as the selector probe in the Emailchaser app's DNS checks, in the same order. A provider's own default is tried first when its MX records point at it.

Gmail and Yahoo accept 1024-bit keys, and Google recommends 2048.

Google's sender guidelines say that sending to personal Gmail accounts requires a DKIM key of 1024 bits or longer, and recommend 2048 bits. Yahoo asks for a minimum of 1024 bits. Our check reads the length from the key itself: 2048 bits or more is a pass, 1024 is a warning that still works, and anything shorter fails, because Gmail ignores it.

What we findResultWhat it means
A 2048-bit or longer RSA key, or an Ed25519 keyPassReceivers can verify your signatures.
A 1024-bit RSA keyWarningIt works today. Generate a 2048-bit key next time you rotate.
A key shorter than 1024 bitsFailGmail ignores it, so your mail counts as unsigned.
v=DKIM1; p= with nothing after p=WarningThe key was switched off on purpose. Mail signed with it fails.
A record that does not decodeFailUsually a key cut off while pasting it into DNS.
No key under any of the 51 namesWarningDKIM is off, or it uses a custom selector.

Google's email sender guidelines and Yahoo Sender Hub best practices, read 6 October 2026.

Google Workspace and Microsoft 365 only sign with your domain after you switch DKIM on.

Both providers sign outgoing mail with a key of their own until you set up yours, so the mail is signed, but not as your domain, and it does not count for DMARC. This is the most common DKIM problem on new cold email domains.

Google Workspace

  1. In the Google Admin console, open Apps, Google Workspace, Gmail, Authenticate email.
  2. Pick the domain and generate a new record with a 2048-bit key. The selector is google unless you change it.
  3. Publish the TXT record it shows at google._domainkey in your DNS.
  4. Wait for DNS, then press Start authentication. Run the check above to see the key.

Microsoft 365

  1. In Microsoft Defender, open Email and collaboration, Policies and rules, Threat policies, Email authentication settings, DKIM.
  2. Pick the domain. It shows two CNAME records, for selector1._domainkey and selector2._domainkey.
  3. Publish both CNAME records, then switch signing on for the domain.
  4. Run the check above: we follow the CNAME and read the key behind it.

A DKIM check fails for one of three reasons, and only one is a missing key.

  1. The key is not where the signature says. The receiver looks up the selector named in the message's s= tag. If DNS has no key there, or a different key, the signature cannot be checked. This is the case the report above can see.
  2. The message changed on the way. A mailing list that adds a footer, or a gateway that rewrites links, changes the signed body, and the signature no longer matches. DNS looks perfect; the failure only shows in the headers of the message that arrived, which the email header analyzer reads.
  3. The wrong domain signed it. The signature verifies, but its d= domain is the sending service's, not yours. DKIM passes and DMARC still fails, because DMARC needs the signing domain to match your From address.

A DKIM record is a short list of tags, and only p= has to be there.

TagExampleWhat it means
vv=DKIM1Marks the record as DKIM. Optional, but if present it must come first.
kk=rsaThe key type: rsa (the default) or ed25519.
pp=MIIBIjANBg...The public key itself, in base64. Empty means the key was revoked.
tt=yTesting mode: receivers are asked not to treat a failure differently from no signature.
hh=sha256The hash algorithms the key may be used with. Rarely set.
ss=emailThe services the key is for. Rarely set; the default is all.

The tags are defined in RFC 6376, and ed25519 keys in RFC 8463.

Rotate a DKIM key by publishing the new one before you remove the old one.

A key can stay in use for years, but changing it now and then limits the damage if the private key ever leaks. The safe way is to publish the new key under a new selector, switch signing to it, and leave the old key in DNS for a few days so mail already on its way still verifies. Then remove the old record, or empty its p= value to revoke it.

If you need a key pair for your own server, the DKIM record generator makes one in your browser. DKIM works together with SPF and DMARC: check the others on the SPF checker and the DMARC checker, or all five at once on the domain health check.

Common questions about DKIM

What is a DKIM selector?

The name a DKIM key is published under: <selector>._domainkey.<your domain>. It lets one domain keep several keys, one per sending service. Your selector is the s= value in the DKIM-Signature header of any email you send.

Why does the checker say no DKIM key was found?

We try the 51 names providers use by default. If none of them holds a key, DKIM is either off or published under a custom name. Type your selector next to the domain and we read that key directly.

Is a 1024-bit DKIM key still OK?

It works: Gmail and Yahoo both accept keys of 1024 bits or longer. Google recommends 2048 bits, so we mark 1024-bit keys as a warning, not a failure.

What does an empty p= value mean?

The key was switched off on purpose. A record like v=DKIM1; p= tells receivers that mail signed with that selector should fail DKIM. If you still sign with it, publish the key again from your provider's settings.

Can I have more than one DKIM key?

Yes, one per selector. Most domains have one for their mailbox provider and one for each service that sends as them, such as a newsletter tool or a help desk. Our check lists every key it finds.

What does d= mean in a DKIM signature?

The domain that signed the message. DMARC only counts a DKIM pass when d= matches the domain in your From address, or its parent. A provider that signs with its own domain gives you a DKIM pass that does nothing for DMARC.

Does a DKIM record work as a CNAME?

Yes. Microsoft 365 and many sending services ask for a CNAME at selector._domainkey that points at a key they host and rotate. Receivers follow the CNAME, and so does our check.

Do I need DKIM if SPF already passes?

Yes. Gmail, Yahoo and Outlook require both from bulk senders, and DKIM is the one that survives forwarding, so DMARC leans on it most.

How do I check my DKIM record?

Type your domain in the checker above. We try 51 common selectors and read every key we find. If you use a custom selector, type it in the selector box. By hand, run dig TXT selector._domainkey.yourdomain.com +short and replace selector with yours.

What is DKIM verification?

The receiving server reads the selector and domain in a message's DKIM-Signature header, fetches the public key from DNS and checks that the signature matches the message. A match proves your domain signed it and that nobody changed it on the way.

How do I check that SPF and DKIM are working?

Send a message from the mailbox to a Gmail address you own, open it, choose the three dots and Show original, and look for PASS next to SPF, DKIM and DMARC. This page checks the DNS side of the same records.

How do I fix a DKIM failure?

The usual causes are a key that is missing or switched off, a key cut off while pasting, a message changed after signing (some forwarders and mailing lists add footers) and a service that signs with its own domain instead of yours. Read the result above, then switch DKIM on at the service.

Check the rest of your setup with these free tools.

Send cold email from domains that pass all five checks.

Every plan includes warm-up, follow-ups and unlimited email accounts.

Start my free trial7-day free trial, $0 today