A selector names one DKIM key. The signature in each message says which (s=), and the receiver looks the key up at <selector>._domainkey.<domain>. A domain can have as many as it has services, each with its own.
| Syntax | <selector>._domainkey.<domain> |
| In the message | s= in the DKIM-Signature header |
| In DNS | TXT (or a CNAME to the service) at <selector>._domainkey.<domain> |
| How many | As many as you need |
| Defined in | RFC 6376 §3.1 |
What it does
Selectors let one domain sign with several keys at once — Google Workspace with google, Microsoft 365 with selector1 and selector2, SendGrid with s1 and s2 — and replace a key by publishing a new selector before retiring the old one.
Selectors are chosen by the sender and are not listed anywhere, so a checker can only guess common ones. The reliable way is to open a message you sent, view its headers, and read s= (and d=, the domain) in the DKIM-Signature line.
Examples
DKIM-Signature: v=1; a=rsa-sha256; d=example.com; s=google; …
Selector google: the key is at google._domainkey.example.com.
See what your own DKIM record says
Every term of your published record, read and explained — including this one.
Common mistakes
- Concluding that a domain has no DKIM because a checker found no key — it may use a selector the checker did not try.
What we recommend
Keep a note of every selector each service uses; you will need them when you change providers.
Find the DKIM keys your domain publishes →
Whose each selector is — google, selector1, s1 and more →
Sources
Checked on 25 September 2026 against these official sources:
- RFC 6376: DomainKeys Identified Mail (DKIM) Signatures — rfc-editor.org