How to find your DKIM selector and check your DKIM record
TL;DR: A DKIM selector is a short label that tells receiving servers where to find your public signing key in DNS, at selector._domainkey.yourdomain.com. You cannot check or fix a DKIM record without it. The most reliable way to find it is to open the raw source of an email you sent and read the s= value in the DKIM-Signature header. Common defaults are google for Google Workspace and selector1 and selector2 for Microsoft 365. Once you have it, query the DNS record and confirm a valid public key is published.
What a DKIM selector is
DKIM adds a digital signature to every email you send. The receiving server needs your public key to verify it, and it finds the key in DNS. A selector is the label that says which key to fetch.
If your domain is example.com and the selector is google, the key lives at:
google._domainkey.example.com
One domain can have many selectors, because each sending service uses its own. Your office email, a newsletter tool and a billing system might each sign with a different selector. That is normal and healthy. For the broader picture of how DKIM works with SPF and DMARC, read our guide on why business emails go to spam.
The selector is public information. Finding it does not weaken your security. Only the private key, which stays with the sending service, must be secret.
Method 1: read it from an email header
This is the most reliable method because it shows what your mail is actually signed with.
- Send an email from your domain to a Gmail address you control.
- Open the message, click the three-dot menu and choose Show original.
- Find the line starting with
DKIM-Signature. - Read the
s=value, which is the selector, and thed=value, which is the signing domain.
A header looks like this:
DKIM-Signature: v=1; a=rsa-sha256; d=example.com; s=google; ...
Here the selector is google and the signing domain is example.com. One email can carry more than one DKIM-Signature. Pick the one where d= matches your domain, because a signature from a different domain, such as your sending service's, is not your domain's DKIM.
Method 2: find it in your email provider's admin console
Google Workspace and Microsoft 365 show DKIM details in their admin panels. If you manage the account, this is the quickest route, and it also shows whether DKIM signing is switched on.
- Google Workspace: Admin console, then Apps, Google Workspace, Gmail, Authenticate email. It shows the selector and the DNS record to publish.
- Microsoft 365: In the Defender portal, open email authentication settings and DKIM for your domain. It shows the two selector CNAME records.
- Other services, such as newsletter or transactional senders, show the records they want you to add in their domain authentication settings.
Method 3: query DNS directly
If you already suspect a selector, test it with a DNS lookup.
dig TXT google._domainkey.example.com +short
nslookup -type=TXT google._domainkey.example.com
A real DKIM record returns a value starting with v=DKIM1; and containing p= followed by a long public key. If the selector does not exist, you get no answer. For Microsoft 365, the selectors are published as CNAME records, so query selector1._domainkey.example.com as CNAME instead.
This method confirms a guess but cannot discover an unknown selector, because there is no way to list every record under _domainkey. If you are not sure how DNS record types differ, see DNS record types explained.
Method 4: use a selector discovery tool
Online tools identify your mail provider from your MX records and then test a list of well-known selectors. They are quick for a first look. They have a limit: they cannot find custom or randomly generated selectors, so a tool saying "none found" does not prove DKIM is missing. Fall back to Method 1, an email header, when a tool finds nothing.
Default selectors by provider
These are common defaults. Your provider may use a different one, so confirm with a real header.
| Sending service | Typical selector |
|---|---|
| Google Workspace | google |
| Microsoft 365 | selector1, selector2 (CNAME records) |
| Zoho Mail | zoho, zmail |
| SendGrid | s1, s2 |
| Mailchimp | k1, k2, k3 |
| Amazon SES | Generated per domain, so read the console |
| Postmark | pm |
| HubSpot | hs1, hs2 |
| Brevo | brevo1, brevo2 |
If you use your hosting provider's mail server, the selector is often default, but this varies, so check a header. Our guide on setting up business email on your own domain explains the records involved.
How to check the record
Once you have the selector, confirm three things.
- The record exists at
selector._domainkey.domainand starts withv=DKIM1. - A public key is present. The
p=tag must not be empty. An emptyp=means the key was revoked. - Real mail passes. Send a test message to Gmail, open Show original and look for
DKIM: PASSand the correctd=domain.
For a DMARC pass, the DKIM signing domain must also align with your From domain. A message signed by sendingservice.com can pass DKIM yet still fail DMARC alignment for example.com. If DMARC reports show failures, see our guides on DMARC and email forwarding and on SPF lookup limits.
Common DKIM problems
- Record split across lines or truncated. Long keys sometimes break when pasted into a DNS panel. Some panels need the value in quotes, others add them for you.
- Wrong record type. Publishing a TXT where a CNAME is required, or the reverse.
- Domain name duplicated. A DNS panel that appends your domain automatically turns
google._domainkey.example.comintogoogle._domainkey.example.com.example.com. Enter only the host part,google._domainkey, when the panel adds the domain. - Signing not enabled. The record exists but the provider is not signing mail yet.
- Old selectors left behind. Remove records for services you no longer use.
- Key too short. Use a 2048-bit key where your provider supports it.
FAQs
What is a DKIM selector?
A label in the DKIM signature that tells the receiver which public key to fetch from DNS, at selector._domainkey.yourdomain.com.
How do I find my DKIM selector in Gmail?
Send an email from your domain to a Gmail address, open it, choose Show original and read the s= value on the DKIM-Signature line.
What is the default DKIM selector for Google Workspace?
Usually google, but confirm it in the admin console or an email header.
Can a domain have more than one DKIM selector?
Yes. Each sending service typically has its own, and many domains have several active at once.
Is the DKIM selector secret?
No. It is public by design. Only the private key must stay secret.
Why does my DKIM check say record not found?
Either the selector is wrong, the record was not published correctly, or DNS has not updated yet. Confirm the selector from an email header first.
Does DKIM pass mean my email will reach the inbox?
No. DKIM proves the message was signed and not altered. Inbox placement also depends on SPF, DMARC, reputation and content.
How often should I rotate DKIM keys?
Many organisations rotate once or twice a year. Follow your email provider's guidance and publish the new selector before switching.
Conclusion
Finding your DKIM selector takes one email and one header. Read the s= value, query the record at selector._domainkey.yourdomain.com, confirm a public key is published and check that real mail shows DKIM pass. With the selector in hand, every other DKIM test and fix becomes straightforward.
HostCloud's business email and DNS tools make it easier to keep your authentication records correct. See https://hostcloud.in.
Sources: