Glossary · Authentication
What is a DKIM selector?
The short answer
A DKIM selector is a short name, such as google or selector1, that tells a receiving mail server which DKIM key to look up for your domain. A domain can have several DKIM keys, and the DKIM selector is the label that picks the right one.
Also called: DKIM selector name, DKIM s= tag
By Ali Tahir Sajjad · Updated · 3 min read
DKIM selector: what to remember
- A DKIM selector is a label for a DKIM key. It tells mail servers where to find the key in your DNS.
- You can find the DKIM selector in any email you have sent: it is the s= value in the DKIM-Signature line of the email header.
- Google Workspace uses the DKIM selector google by default. Microsoft 365 uses selector1 and selector2.
- Selectors let one domain use several services, each with its own DKIM key.
What does DKIM selector mean?
To understand a DKIM selector, start with DKIM itself.
DKIM is a way of signing your emails so the receiver can check they really came from your domain and were not changed on the way. It uses a pair of keys. One key is secret and signs each email. The other key is public and sits in your domain’s DNS, where anyone can read it and use it to check the signature.
Here is the catch: a domain can have more than one DKIM key. So when an email arrives, the receiving mail server needs to know which key to use.
That is the job of the DKIM selector. It is a short name that says “use this key”.
Think of a row of lockers in a gym. All the lockers belong to you, but each one has a number on the door. The DKIM selector is the locker number. It tells the mail server exactly which locker holds the key for this email.
How a DKIM selector works
- Your mail server signs the email and adds a line called
DKIM-Signatureto the email header. - That line contains the DKIM selector, written as
s=, and your domain, written asd=. - The receiving mail server puts them together to build an address:
selector._domainkey.yourdomain.com. - It looks up that address in DNS and finds the public key.
- It uses the key to check the signature. If it matches, DKIM passes.
A DKIM selector example
Here is part of a real-looking DKIM signature line:
DKIM-Signature: v=1; a=rsa-sha256; d=example.com; s=google; ...
d=example.comis the domain.s=googleis the DKIM selector.
So the mail server looks for the key at:
google._domainkey.example.com
If you changed the DKIM selector to mail2026, the key would live at mail2026._domainkey.example.com instead.
DKIM selectors for Google Workspace and Microsoft 365
| Provider | Default DKIM selector | Record type | Where the key is found |
|---|---|---|---|
| Google Workspace | google |
TXT | google._domainkey.yourdomain.com |
| Microsoft 365 | selector1 and selector2 |
CNAME | selector1._domainkey.yourdomain.com and selector2._domainkey.yourdomain.com |
Microsoft 365 uses two DKIM selectors so it can replace the key from time to time without any break. It signs with one, and the other is ready as the next one.
How to find your DKIM selector
- Send an email from the mailbox to yourself.
- Open the email and view its header. In Gmail, open the three-dot menu and choose Show original.
- Search the header for
DKIM-Signature. - Find
s=inside that line. The word after it is your DKIM selector.
If there is no DKIM-Signature line at all, DKIM is not switched on for that mailbox yet.
You can also test a DKIM selector without opening a header. A DKIM checker such as MXToolbox looks up the record for the selector you type in.
Why DKIM selectors matter for cold email
For cold email, DKIM is not optional. Gmail and Outlook expect every sender to sign their email, and an unsigned email is far more likely to land in spam.
The DKIM selector is where DKIM setups usually go wrong. If the selector in your emails does not match a record in your DNS, the mail server looks in the wrong locker, finds nothing, and DKIM fails, even though you “set up DKIM”.
When you send cold email from many domains, every domain needs its own DKIM record under the correct selector. That is a lot of careful copying. PureMail’s team adds the DKIM records for each of your domains when it sets up your Google Workspace inboxes or Microsoft 365 inboxes.
Common DKIM selector mistakes
- The wrong selector in DNS. The record is saved as
default._domainkeybut the emails are signed withs=google. - Adding the domain twice. Some DNS panels add your domain for you, so typing the full name gives
google._domainkey.example.com.example.com. - Only adding one of the two Microsoft 365 selectors. Both
selector1andselector2are needed. - Forgetting to switch DKIM on. Adding the DNS record is step one. You still have to turn on signing in Google or Microsoft. Our guide to setting up SPF, DKIM and DMARC walks through the whole setup.
- Reusing one selector for two services. Give each sending service its own DKIM selector.