DKIM Validator API
Overview
To use DKIM Validator, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/dkimvalidatorExample
How to call the DKIM Validator API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/dkimvalidator?domain=google.com" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/dkimvalidator?domain=google.com', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/dkimvalidator?domain=google.com', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/dkimvalidator?domain=google.com", nil)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"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",
"issues_found": [
{
"code": "WEAK_PUBLIC_KEY_BITS",
"type": "warning",
"message": "Public key uses weak 1416 bits"
}
],
"valid": true
}
}Authentication
The DKIM Validator API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the DKIM Validator API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the DKIM Validator API:
Validate DKIM Record
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
domain | string | required | The domain to validate the DKIM record for Format: domain (e.g., google.com) | - |
Response
The DKIM Validator API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<selector>20230601</selector>
<host>google.com</host>
<dkim_host>20230601._domainkey.google.com</dkim_host>
<cname_target xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<has_dkim_record>true</has_dkim_record>
<dkim_record>v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4zd3nfUoLHWFbfoPZzAb8bvjsFIIFsNypweLuPe4M+vAP1YxObFxRnpvLYz7Z+bORKLber5aGmgFF9iaufsH1z0+aw8Qex7uDaafzWoJOM/6lAS5iI0JggZiUkqNpRQLL7H6E7HcvOMC61nJcO4r0PwLDZKwEaCs8gUHiqRn/SS3wqEZX29v/VOUVcI4BjaOz</dkim_record>
<dkim_records_count>1</dkim_records_count>
<version>DKIM1</version>
<key_type>rsa</key_type>
<issues_found>
<item>
<code>WEAK_PUBLIC_KEY_BITS</code>
<type>warning</type>
<message>Public key uses weak 1416 bits</message>
</item>
</issues_found>
<valid>true</valid>
</data>
</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
issues_found:
- code: WEAK_PUBLIC_KEY_BITS
type: warning
message: Public key uses weak 1416 bits
valid: true
| key | value |
|---|---|
| selector | 20230601 |
| host | google.com |
| dkim_host | 20230601._domainkey.google.com |
| cname_target | |
| 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 |
| issues_found | [{code:WEAK_PUBLIC_KEY_BITS,type:warning,message:Public key uses weak 1416 bits}] |
| valid | true |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
selector | string | DKIM selector used for DNS record lookup | |
host | string | Domain name being validated | |
dkim_host | string | Full DKIM DNS record hostname with selector | |
cname_target | object | CNAME target if present in DNS record | |
has_dkim_record | boolean | Whether DKIM record exists in domain DNS | |
dkim_record | string | Complete DKIM record value and public key | |
dkim_records_count | number | Number of DKIM records found for domain | |
version | string | DKIM protocol version from record | |
key_type | string | Public key algorithm type used | |
| [ ] Array items: | array[1] | Array of detected issues with DKIM configuration | |
â”” code | string | - | |
â”” type | string | - | |
â”” message | string | - | |
valid | boolean | Overall DKIM record validity status |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access DKIM Validator through GraphQL to combine it with other API calls in a single request. Query only the dkim validator data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
dkimvalidator(
input: {
domain: "google.com"
}
) {
selector
host
dkim_host
cname_target
has_dkim_record
dkim_record
dkim_records_count
version
key_type
issues_found
valid
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The DKIM Validator API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
DKIM Validator requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The DKIM Validator API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for DKIM Validator
Official DKIM Validator packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
DKIM Validator works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for DKIM Validator?
How many credits does DKIM Validator cost?
Each successful DKIM Validator API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful dkim validator lookups.
Can I use DKIM Validator in production?
The free plan is for testing and development only. For production use of DKIM Validator, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use DKIM Validator from a browser?
What happens if I exceed my DKIM Validator credit limit?
When you reach your monthly credit limit, DKIM Validator API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








