DKIM Validator API GET

DKIM Validator checks the DomainKeys Identified Mail (DKIM) DNS records for a domain to verify that they are present and correctly formatted.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/dkimvalidator

Verification

Format

No key required to try it. Get a key to use it in your app.

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // DKIM Validator response payload
  }
}

About the DKIM Validator API

This tool inspects the DKIM record by performing DNS lookups for common selectors. It validates the syntax, surfaces the public-key length in bits, flags testing mode, and derives a composite email-signing posture score so you can tell at a glance whether a domain's DKIM key actually protects its mail.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use DKIM Validator

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the DKIM Validator API.

Read the docs →

What does the DKIM Validator API do?

DKIM Validator checks the DomainKeys Identified Mail (DKIM) DNS records for a domain to verify that they are present and correctly formatted.

How do I authenticate DKIM Validator API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the DKIM Validator API cost?

Each call spends 10 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the DKIM Validator API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the DKIM Validator API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the DKIM Validator API use?

GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — GET /v1/dkimvalidator

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`domain`Required	string	`google.com`	The domain to validate the DKIM record for domain

Optional

Parameter	Type	Example	Description
`selector`Optional	string	`google`	The DKIM selector to look up (the label before ._domainkey). When omitted, a list of common selectors is tried

Example request

1
2

curl "https://api.apiverve.com/v1/dkimvalidator?domain=google.com&selector=google" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — GET /v1/dkimvalidator

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "selector": "20230601",
    "host": "google.com",
    "dkim_host": "20230601._domainkey.google.com",
    "cname_target": null,
    "has_dkim_record": true,
    "dkim_record": "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4zd3nfUoLHWFbfoPZzAb8bvjsFIIFsNypweLuPe4M+vAP1YxObFxRnpvLYz7Z+bORKLber5aGmgFF9iaufsH1z0+aw8Qex7uDaafzWoJOM/6lAS5iI0JggZiUkqNpRQLL7H6E7HcvOMC61nJcO4r0PwLDZKwEaCs8gUHiqRn/SS3wqEZX29v/VOUVcI4BjaOz",
    "dkim_records_count": 1,
    "version": "DKIM1",
    "key_type": "rsa",
    "key_bits": 1416,
    "is_test_mode": false,
    "issues_found": [
      {
        "code": "WEAK_PUBLIC_KEY_BITS",
        "type": "warning",
        "message": "Public key uses weak 1416 bits"
      }
    ],
    "valid": true,
    "risk_score": 25,
    "risk_level": "medium"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`selector`	string	`"20230601"`	DKIM selector used for DNS record lookup
`host`	string	`"google.com"`	Domain name being validated
`dkim_host`	string	`"20230601._domainkey.google.com"`	Full DKIM DNS record hostname with selector
`cname_target`	object	`null`	CNAME target if present in DNS record
`has_dkim_record`	boolean	`true`	Whether DKIM record exists in domain DNS
`dkim_record`	string	`"v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4zd3nfUoLHWFbfoPZzAb8bvjsFIIFsNypweLuPe4M+vAP1YxObFxRnpvLYz7Z+bORKLber5aGmgFF…`	Complete DKIM record value and public key
`dkim_records_count`	number	`1`	Number of DKIM records found for domain
`version`	string	`"DKIM1"`	DKIM protocol version from record
`key_type`	string	`"rsa"`	Public key algorithm type used
`key_bits`	number	`1416`	Length of the DKIM public key in bits. 2048 or higher is the current recommendation; below 1024 is dangerously weak. 0 indicates a revoked key (empty p= value), and null means no decodable key is present
`is_test_mode`	boolean	`false`	Whether the record sets t=y (testing mode). In testing mode receivers are told to treat mail as if DKIM were not deployed, so signatures carry no enforcement weight
`issues_found`Premium	array[1]		Array of detected issues with DKIM configuration
`code`Premium	string	`"WEAK_PUBLIC_KEY_BITS"`	Error code identifying the specific issue
`type`Premium	string	`"warning"`	Severity level of the issue
`message`Premium	string	`"Public key uses weak 1416 bits"`	Human-readable description of the issue
`valid`	boolean	`true`	Overall DKIM record validity status
`risk_score`Premium	number	`25`	Composite 0-100 email-signing weakness score derived from the key length, testing mode and hash algorithm — higher means the deployed DKIM key offers less real protection (a revoked or sub-1024-bit key scores high; a 2048-bit enforced key scores low)
`risk_level`Premium	string	`"medium"`	Risk band derived from the score: low, medium or high

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 10 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	DKIM Validator calls	Per 1,000 calls
Free	Free	200	20	Free
Starter	$29.99	200,000	20,000	$1.50
Pro	$99.99	1,000,000	100,000	$1.00
Mega	$299.99	4,000,000	400,000	$0.75

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — GET /v1/dkimvalidator

No SDK to install — this is a plain HTTPS call to /v1/dkimvalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/dkimvalidator" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/dkimvalidator-apiSource, issues and the examples this page is built from.ReferenceDKIM Validator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/dkimvalidatornpm APIVerve.API.DKIMValidatorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/dkimvalidator

Install the Node.js SDK, then call the DKIM Validator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/dkimvalidator

Node.js

const res = await fetch("https://api.apiverve.com/v1/dkimvalidator", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/dkimvalidatorThe published Node.js client, versioned and signed.GitHubapiverve/dkimvalidator-apiSource, issues and the examples this page is built from.ReferenceDKIM Validator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.DKIMValidatorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/dkimvalidator

No SDK to install — this is a plain HTTPS call to /v1/dkimvalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/dkimvalidator",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/dkimvalidatornpm APIVerve.API.DKIMValidatorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/dkimvalidator

Install the C# / .NET SDK, then call the DKIM Validator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.DKIMValidator

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/dkimvalidator");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.DKIMValidatorThe published C# / .NET client, versioned and signed.GitHubapiverve/dkimvalidator-apiSource, issues and the examples this page is built from.ReferenceDKIM Validator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/dkimvalidatornpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/dkimvalidator

No SDK to install — this is a plain HTTPS call to /v1/dkimvalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/dkimvalidator", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/dkimvalidatornpm APIVerve.API.DKIMValidatorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/dkimvalidator

No SDK to install — this is a plain HTTPS call to /v1/dkimvalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/dkimvalidator");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/dkimvalidatornpm APIVerve.API.DKIMValidatorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/dkimvalidator

No SDK to install — this is a plain HTTPS call to /v1/dkimvalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/dkimvalidator")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/dkimvalidatornpm APIVerve.API.DKIMValidatorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

7 SSL Certificate Problems That Kill TrustExpired certs, mismatched domains, weak encryption. A practical checklist for catching SSL issues before your users do.Read

DNS Lookups: A Developer's Debugging GuideDNS problems cause connection failures and email issues. Learn how to use DNS lookups to diagnose problems faster.Read

WHOIS Data: Domain Intelligence for Business and SecurityWHOIS data reveals domain ownership, age, and infrastructure. Use it for lead qualification, research, and fraud detection.Read

DKIM Validator API GET

Try it — live request, no key required

About the DKIM Validator API

Ways to call it

Other ways to use DKIM Validator

Questions.

Request parameters — GET /v1/dkimvalidator

Required

Optional

Authentication

Response — GET /v1/dkimvalidator

Response fields

Response headers

Errors

What a call costs — 10 credits per call

Call it from cURL — GET /v1/dkimvalidator

Resources

Also published for

Call it from Node.js — GET /v1/dkimvalidator

Resources

Also published for

Call it from Python — GET /v1/dkimvalidator

Resources

Also published for

Call it from C# / .NET — GET /v1/dkimvalidator

Resources

Also published for

Call it from Go — GET /v1/dkimvalidator

Resources

Also published for

Call it from PHP — GET /v1/dkimvalidator

Resources

Also published for

Call it from Ruby — GET /v1/dkimvalidator

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — DKIM Validator API

Domain Data

Related articles

Ready to build with DKIM Validator? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog