Skip to content

DKIM Selector: How to Find Yours and Check the DNS Record

A DKIM selector tells receivers which public key to use. Here is how to find yours in a message header and confirm the DNS record exists.

Abedrahim B Nov 12, 2026 5 min read 1,128 words
DKIM Selector: How to Find Yours and Check the DNS Record

Your DKIM selector is the label that tells a receiving server which public key to use when it checks a signed message. You need it to publish the key in DNS, to troubleshoot a dkim=fail result and to rotate keys safely. This guide shows how to find your DKIM selector in a message header, how to check the DNS record it points to and what to do when something does not match.

DKIM selector guide cover
DKIM selector guide cover

TL;DR#

  • The selector is the s= value in the DKIM-Signature header of a sent message.
  • The public key lives in a TXT record at selector._domainkey.yourdomain.com.
  • DNS has no way to list all selectors, so read a real message header to find yours.
  • Each sending service usually has its own selector, which makes key rotation easier.

What is a DKIM selector?#

DKIM signs outgoing mail with a private key. The receiver looks up the matching public key in DNS to confirm the signature. The standard, RFC 6376, uses two tags in the signature to find that key: d= for the signing domain and s= for the selector.

The key sits at a name built from both:

<selector>._domainkey.<domain>

So a message signed with d=example.com and s=mail1 makes the receiver query mail1._domainkey.example.com for a TXT record. The selector lets one domain publish many keys at once. That is how a company can sign mail from its mailbox provider, its marketing platform and its sales tool, each with a different key.

How to find your DKIM selector from a message header#

This is the most reliable method, because it shows the selector that was actually used.

  1. Send a message from the address you want to check to a mailbox you control, such as a Gmail account.
  2. Open the received message and view the original source. In Gmail, use the three-dot menu and choose "Show original".
  3. Search the header for DKIM-Signature.
  4. Read the s= tag. Next to it you will see d=, the signing domain.

A signature may look like this:

DKIM-Signature: v=1; a=rsa-sha256; d=example.com; s=selector1; ...

Here the DKIM selector is selector1. If the header has two signatures, each with its own selector, one belongs to your domain and the other may belong to the sending service. Check that d= matches your domain.

Common default selectors by provider#

Providers pick their own selector names, and they can change, so treat these as hints and confirm with a real header:

  • Google Workspace: the admin console shows the selector when you generate the key, and google is the usual default.
  • Microsoft 365: uses selector1 and selector2, published as CNAME records.
  • Other platforms: many email platforms generate a selector for you and show the exact DNS record to add.

Always copy the host name from your provider's setup screen. Do not guess it.

How to check the DKIM DNS record#

Once you know the selector, query the record directly. On a command line:

dig TXT selector1._domainkey.example.com +short

A healthy answer starts with v=DKIM1 and contains a p= tag holding the public key:

"v=DKIM1; k=rsa; p=MIIBIjANBgkq..."

If the answer is empty, the record is missing or the name is wrong. If the provider uses a CNAME, you will see the target host instead and the key is behind it. An online lookup works as well as dig, if you prefer a web form.

Why you cannot list every selector in DNS#

People often ask for a tool that shows all selectors for a domain. DNS does not offer one. A resolver answers questions about a specific name, and it will not list the labels under _domainkey. You can try common names like default, google, selector1 or k1, but a miss does not prove no key exists.

The dependable approach is to read the header of a real message, or to ask the admin of each sending service.

Fixing common DKIM selector problems#

  • Selector not found: the s= value in the header does not match a DNS record. Check for typos, a missing ._domainkey, or a record added to the wrong domain.
  • Key published at the wrong host: some DNS panels append the domain automatically. Enter only selector1._domainkey, not the full name, if your panel adds the domain.
  • Truncated key: long RSA keys can be split into several quoted strings. Make sure your DNS provider joins them correctly.
  • Old key still in use: after rotation, the sending service must use the new selector. Keep the old record in DNS until mail signed with it is gone.
  • Signature domain differs from your From domain: DKIM can pass while DMARC alignment fails. Make sure d= matches your visible From domain.

Rotate keys with selectors#

Selectors make rotation easy. Publish a new key under a new selector, switch your sending service to it, then remove the old record after a safe period. At no point is a key missing, so mail keeps passing. Plan a regular review so old selectors do not pile up in DNS.

DKIM works with SPF and DMARC#

DKIM proves a message was not changed and that the signing domain approved it. SPF checks the sending server. DMARC ties both to the From address and sets a policy. A correct DKIM selector is one piece of that set, so check all three when mail lands in spam.

Clean data helps too. Bounces from bad addresses hurt your reputation no matter how good your authentication is, so verify your list with an email verifier before you send, and use the bulk tool for large files.

Frequently asked questions#

What is a DKIM selector?#

It is a name used to find the public key for a DKIM signature. It appears as the s= tag in the DKIM-Signature header and forms part of the DNS name selector._domainkey.domain.

How do I find my DKIM selector?#

Send yourself an email, open the original message source and read the s= tag in the DKIM-Signature header.

Can I have more than one DKIM selector?#

Yes. A domain can publish many selectors at once, one per sending service or one per key in a rotation.

Why does my DKIM lookup return nothing?#

Either the selector is wrong or the record is not published at that exact name. Check the header for the real selector and confirm the DNS host name.

Do I need to change my selector often?#

Not necessarily, but rotating keys on a schedule is good practice. A new selector lets you do it without downtime.

Next step#

Once DKIM passes, protect your reputation at the list level. The Tomba Email Verifier checks whether an address can receive mail, so you send to fewer dead mailboxes.

// start free

See who Tomba finds at any company

Type a company's domain to see its people, their roles and verified work emails, each with the pages it was found on. Free account, no card.

Free plan · No credit card required · GDPR & CCPA

Share
0 clapsEnjoyed it? Give a clap.
Abedrahim B

// about the author

Abedrahim B

CEO

Was this helpful?