Enter a domain, URL, IP, email, or record and get a focused result without setup.
DKIM Record Checker
Enter a sending domain and DKIM selector to retrieve and validate the public key published at selector._domainkey.domain.
GET /v1/tools/dkim/check?domain=example.com&selector=google
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 1,000 free credits every month. Need more? Pick a monthly plan or buy a one-time pack.
Key Features
Query the exact DKIM DNS name formed from the domain and selector.
Check the published DKIM record structure, version, key type, and key data.
See the queried DNS name, returned record, and any missing or invalid fields.
Example request
GET /v1/tools/dkim/check?domain=example.com&selector=google
Example response
{
"domain": "example.com",
"selector": "google",
"dns_name": "google._domainkey.example.com",
"exists": true,
"valid": true,
"key_type": "rsa",
"key_size": 2048
}
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
Look for the s= value in an email's DKIM-Signature header or check the DKIM settings in your email service.
No. It validates the public key record for the supplied domain and selector. Verifying a message signature also requires the complete signed email.
The selector may be incorrect, the record may not be published, or a recent DNS change may not yet be visible to the resolver used for the check.

