Skip to main content

SPF, DKIM and DMARC

How to Find Your DKIM Selector (and Fix 'No DKIM Record Found')

By Tom Sather•Updated October 11, 2026•7 min read

Your DKIM selector is the s= value in the DKIM-Signature header of a message you sent. Here's how to find it, look up the key, and fix 'no DKIM record found.'

On this page

Your DKIM selector is the s= value in the DKIM-Signature header of a message you sent. Open the original of any message from that platform, find the signature, and read off s= (the selector) and d= (the domain). Your public key lives at selector._domainkey.domain in DNS, so with those two values you can look it up directly.

"No DKIM record found" usually means one of two things: the checker you used guessed the wrong selector, or the record isn't where DNS expects it. Both are quick to sort out once you know the selector.

Why you need the selector at all

DKIM lets one domain publish many public keys at once, one per selector. The DKIM spec uses selectors so a domain can run several keys at the same time: one for Google Workspace, one for your newsletter platform, one for your helpdesk, plus spares for rotation.

The receiver never has to guess, because every signed message names its selector. A DKIM checker you run yourself has no message to look at, though. DNS has no way to list every name under _domainkey, so the checker either tries a handful of common selectors or asks you to type one in. If it guesses wrong, it reports "no DKIM record found" even when everything is fine.

Find the selector in a message

This is the reliable method, because it shows the selector that's actually in use.

  1. Send a message from the platform you're checking to a mailbox you control. Gmail and Outlook both work.
  2. Open the full headers. In Gmail, use Show original. In Outlook, open the message properties or View message source.
  3. Find the line that starts with DKIM-Signature:. It looks like this:
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=example.com; s=google;
        h=from:to:subject:date:message-id; bh=...; b=...
  1. Read off s= and d=. Here the selector is google and the domain is example.com.

If there are several DKIM-Signature headers, the message was signed more than once, often once by your platform's own domain and once by yours. The one that matters for DMARC is the one whose d= matches your From domain (see alignment explained).

The Authentication-Results header that the receiving server adds will also show dkim=pass or dkim=fail and the domain it checked (header.d=). Many receivers include the selector there too, as header.s=. Paste the headers into the header analyzer to pull all of this out at once, or see how to read an email header.

Find the selector in your provider's settings

If you can't send a test message, the selector is in the platform's domain authentication screen: it's the first part of the hostname they told you to publish.

PlatformSelectorWhere to find it
Google Workspacegoogle by defaultAdmin console, Apps, Google Workspace, Gmail, Authenticate email
Microsoft 365 (custom domain)selector1 and selector2Defender portal DKIM settings, or Get-DkimSigningConfig in PowerShell

Google's docs say the default prefix is google and that you only need to change it if your domain already has a key with that prefix.

Microsoft 365 uses two CNAME records, selector1._domainkey and selector2._domainkey, pointing at keys Microsoft hosts. Only one is active at a time; the other is used after a key rotation. Microsoft changed the format of the CNAME target for new custom domains in May 2025:

Old: selector1-example-com._domainkey.contoso.onmicrosoft.com
New: selector1-example-com._domainkey.contoso.r-v1.dkim.mail.microsoft

(The r is a character Microsoft generates per tenant.) Don't copy either of these: run Get-DkimSigningConfig -Identity example.com | Format-List Selector1CNAME,Selector2CNAME to get your exact values.

Other platforms use their own naming, from short fixed names to long random strings. Their DNS setup page will show it.

Look up the key

With the selector and domain, query DNS:

dig +short TXT google._domainkey.example.com

A working record looks something like "v=DKIM1; k=rsa; p=MIIBIjANBgkqh...". If the platform uses CNAMEs, the query follows the CNAME to the vendor's key, which is expected. You can also enter the selector in the SPF, DKIM and DMARC checker.

Why you're seeing "no DKIM record found"

Most likely first:

  1. The checker guessed the wrong selector. Get the real one from a message header and check again. If it passes with the right selector, nothing is wrong.
  2. The hostname was doubled. Many DNS consoles append your domain automatically. If you typed google._domainkey.example.com into the host field, the record may now live at google._domainkey.example.com.example.com. Enter just google._domainkey and check what the console shows as the full name.
  3. The record was never published, or the platform step wasn't finished. Some platforms need you to click a final button (Google's is Start Authentication, Microsoft's is enabling DKIM signing for the domain) after DNS is in place. Until then, they don't sign with your domain.
  4. The record type is wrong. The platform asked for a CNAME and you created a TXT, or the reverse.
  5. The key was split or mangled. A 2048-bit key is longer than the 255 characters a single TXT string can hold, so it has to be split into several quoted strings inside one record. Some consoles do this for you; others truncate the key, add stray quotes or insert spaces. A key with a typo is published but useless, and verification fails.
  6. DNS hasn't caught up. New records can take time to appear everywhere, depending on your TTLs. Query your DNS host's authoritative nameserver directly to see whether the record exists yet.
  7. The key was revoked. An empty p= value means the key has been revoked, per the DKIM spec. Any mail still signed with that selector fails. This sometimes happens when someone "cleans up" a selector that is still in use.

If the record is there and DKIM still fails on real messages, the problem is the signature, not the DNS record. See DKIM fail: body hash did not verify and other causes.

How to confirm it's fixed

Send a fresh message from each platform and check the Authentication-Results header for dkim=pass with header.d= showing your domain. If you have DMARC set up, your aggregate reports will show DKIM results per sending source over the following days.

How to keep it from coming back

  • Keep a short list of every platform that sends as your domain, its selector, and who owns it.
  • Before deleting any _domainkey record, check recent DMARC reports or headers to make sure nothing signs with it.
  • When a platform rotates keys (Microsoft 365's two-selector setup is built for this), confirm both selector records stay in DNS.

For background on keys and rotation, see what DKIM is.

When to get help

If DKIM passes in your tests but DMARC reports show failures from sources you can't identify, or you're juggling selectors across several platforms and domains, it's worth getting help before you tighten your DMARC policy.

FAQ

Can I find all DKIM selectors for a domain?

Not from DNS alone. DNS doesn't let anyone list the names under _domainkey, so tools can only test guesses. The reliable sources are message headers and each sending platform's settings.

Can a domain have more than one DKIM selector?

Yes, and most do. Each platform that signs for your domain should have its own selector and key, and the DKIM spec is built for running several at once.

Is the selector secret?

No. It's in the header of every message you sign, and the public key it points to is meant to be public. The private key is the one to protect.

What does "no DKIM record found" mean if my mail is passing DKIM?

It almost always means the tool tried the wrong selector. Look up the selector from a real message header and check that one.

Sources

Related guides

Still stuck?

Some deliverability problems take an experienced eye to untangle. Tell me what you're seeing and I'll tell you what I'd check first. The first 30-minute call is free.