The problem: checking DKIM without knowing the selector
Traditional DKIM tools ask for a domain and a selector. But most users don't know their DKIM selector. Result: they can't verify their configuration.
The DKIM Selector Finder solves this problem. Enter a domain, and the tool automatically discovers all configured DKIM selectors.
How does the discovery work?
1. Email provider detection (Smart mode)
The tool queries your domain's MX records to identify your email providers:
*.google.com→ Google Workspace → selectorgoogle*.outlook.com→ Microsoft 365 → selectorsselector1,selector2*.mcsv.net→ Mailchimp → selectorsk1,k2,k3
2. Smart DNS brute-force
The tool tests known selectors in parallel by querying:
<selector>._domainkey.<your-domain>
For each selector, a DNS TXT query is sent. If a DKIM record exists, it is analyzed.
3. In-depth analysis
Each selector found is analyzed using the same engine as our DKIM Checker:
- Key type: RSA or Ed25519
- Key length: 1024, 2048, 4096 bits
- Record validity
- Security alerts (weak key, invalid format)
- CNAME detection (delegation to provider)
When should you use this tool?
| Situation | This tool is for you |
|---|---|
| You don't know your DKIM selector | Automatic discovery |
| Security audit of a third-party domain | Complete view of the DKIM configuration |
| Email provider migration | Check which selectors are still active |
| DMARC deployment in reject mode | Ensure all email flows are DKIM-signed |
| Deliverability debugging | Identify invalid selectors or weak keys |
DKIM selectors for major providers
| Provider | DKIM Selectors | MX Pattern |
|---|---|---|
| Google Workspace | google | *.google.com |
| Microsoft 365 | selector1, selector2 | *.outlook.com |
| SendGrid | s1, s2, smtpapi | *.sendgrid.net |
| Mailchimp | k1, k2, k3 | *.mcsv.net |
| Amazon SES | amazonses | *.amazonses.com |
| Postmark | pm | *.mtasv.net |
| HubSpot | hs1, hs2 | — |
| Brevo (Sendinblue) | mail, sendinblue | *.sendinblue.com |
| Zoho Mail | zoho, zmail | *.zoho.com |
| OVH | ovhmo* | *.ovh.net |
This table covers the most common providers. The tool tests 100+ selectors in total.
Limitations of brute-force discovery
DNS does not allow listing a zone's subdomains (no wildcard enumeration on *._domainkey). Discovery relies on a catalog of known selectors.
What will be found:
- Standard selectors from 35+ providers in the catalog
- Generic selectors (
default,dkim,mail,s1,selector1, etc.) - Common numeric selectors (
dkim1,dkim2,k1,k2)
What will not be found:
- Custom or random selectors (e.g.,
campaign-2024-q3) - Dynamically generated selectors (hash, UUID)
- Selectors on subdomains (e.g.,
bounce.yourdomain.com)
For those cases, check the headers of your sent emails: DKIM-Signature: s=selector.
FAQ - Frequently Asked Questions
Q: What is a DKIM selector?
A: A DKIM selector is an identifier used to locate the DKIM public key in DNS. It is published at selector._domainkey.yourdomain.com. Each email provider uses its own selector, which allows multiple DKIM signatures to be active simultaneously.
Q: How can I find my DKIM selectors without sending an email?
A: This tool discovers your selectors via DNS brute-force: it tests 50 to 120 known selectors directly against your DNS zone. No email is sent. Smart mode first detects your providers via MX to prioritize the right selectors.
Q: What are the default DKIM selectors for major providers?
A: Google Workspace uses google. Microsoft 365 uses selector1 and selector2. SendGrid uses s1 and s2. Mailchimp uses k1, k2, and k3. Postmark uses pm. See the provider table above for the full list.
Q: Can you check DKIM without knowing the selector?
A: Yes, that's exactly what this tool does. Unlike traditional DKIM checkers, the Selector Finder automatically tests known selectors via DNS brute-force.
Q: What does "DKIM selector not found" mean?
A: No TXT record exists for this selector in DNS. Possible causes: DKIM is not configured, custom selector not in the catalog, record deleted, or incomplete DNS propagation.
Q: What's the difference between Smart mode and Full mode?
A: Smart mode detects your providers via MX and tests ~50 selectors. Full mode tests ~120 selectors without filtering. Use Full if Smart doesn't find all your selectors.
Q: Can the tool find all DKIM selectors?
A: No. Custom or dynamically generated selectors will not be detected. For those cases, check your email headers (DKIM-Signature: s=selector).
Related tools
| Tool | Purpose |
|---|---|
| DKIM Checker | Analyze a specific DKIM selector in depth |
| DKIM Syntax Checker | Validate DKIM record syntax before publishing |
| DKIM Generator | Generate DKIM key pairs (RSA/Ed25519) |
| Deliverability Audit | Check SPF, DKIM, DMARC, and MX for a domain |
| DMARC Inspector | Test your DMARC policy |
| Email Header Analyzer | Extract DKIM selectors from a received email |
Useful resources
- RFC 6376 - DKIM Signatures (official specification)
- RFC 8463 - Ed25519 for DKIM (Ed25519 signatures)
- Google - Set up DKIM (Google Workspace guide)
- Microsoft - DKIM in Exchange Online (Microsoft 365 guide)