Enter a domain, URL, IP, email, or record and get a focused result without setup.
DKIM Selector Discovery
Discover DKIM selectors for any domain. Check common providers and validate public keys.
GET /v1/tools/dkim/discover?domain=example.com
Run the check, then ship the workflow
Use the browser tool for a fast answer, then move the same logic into scripts, monitoring, or product flows when it becomes repeatable.
Outputs highlight statuses, risks, records, and next actions instead of raw provider noise.
Use the request and response examples to turn a one-off check into an API call or recipe.
Used by people at these companies
What this tool helps you decide
Each page is shaped around a practical operational question, not just a raw lookup.
See the current DNS, registration, security, pricing, or reputation evidence.
Compare the result with related checks so the next move is easier to trust.
Copy examples, open linked tools, or move into API documentation when you need scale.
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
Check live service health and documented failure responses before you integrate.
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
Authenticated endpoints use API keys with clear credit costs before you call them.
Start with 10,000 monthly credits and upgrade only when usage grows.
Key Features
Probe common DKIM selector names for the domain.
Show likely mail providers when a selector matches a known pattern.
See how many selectors were checked and how many were found.
Example request
GET /v1/tools/dkim/discover?domain=example.com
Example response
{
"checked": 8,
"found": [
{ "selector": "google", "provider_hint": "Google Workspace" }
]
}
Built on the same API
The browser experience previews DomScan's structured endpoints, so teams can validate a use case before writing code.
Frequently asked questions
A selector points to the public key record for a signing service, which lets you publish multiple keys and rotate them over time.
Common patterns like google, selector1, or k1 often map to known email platforms, so the detector can suggest a likely provider.
The domain may not use DKIM, may use uncommon selector names, or may publish keys on a different subdomain or service.

