DNS Propagation Checker API
DNS Propagation Checker verifies if DNS changes have propagated across multiple global DNS servers. It queries DNS servers worldwide to show the current state of your DNS records.
The DNS Propagation Checker API provides reliable and fast access to dns propagation checker data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.
To use DNS Propagation Checker, 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/dnspropagationCode Examples
Here are examples of how to call the DNS Propagation Checker API in different programming languages:
curl -X GET \
"https://api.apiverve.com/v1/dnspropagation" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/dnspropagation', {
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/dnspropagation', headers=headers)
data = response.json()
print(data)const https = require('https');
const url = require('url');
const options = {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
};
const req = https.request('https://api.apiverve.com/v1/dnspropagation', options, (res) => {
let data = '';
res.on('data', (chunk) => data += chunk);
res.on('end', () => console.log(JSON.parse(data)));
});
req.end();<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/dnspropagation');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'GET');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
'X-API-Key: your_api_key_here',
'Content-Type: application/json'
]);
$response = curl_exec($ch);
curl_close($ch);
$data = json_decode($response, true);
print_r($data);
?>package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/dnspropagation", 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))
}require 'net/http'
require 'json'
uri = URI('https://api.apiverve.com/v1/dnspropagation')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Get.new(uri)
request['X-API-Key'] = 'your_api_key_here'
request['Content-Type'] = 'application/json'
response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;
class Program
{
static async Task Main(string[] args)
{
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("X-API-Key", "your_api_key_here");
var response = await client.GetAsync("https://api.apiverve.com/v1/dnspropagation");
response.EnsureSuccessStatusCode();
var responseBody = await response.Content.ReadAsStringAsync();
Console.WriteLine(responseBody);
}
}Authentication
The DNS Propagation Checker 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 DNS Propagation Checker API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the DNS Propagation Checker API:
Check DNS Propagation
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
domain | string | required | The domain name to check propagation for Format: domain (e.g., google.com) | - | |
type | string | optional | The DNS record type to check Supported values: AAAAAMXNSTXT |
Response
The DNS Propagation Checker API returns responses in JSON, XML, YAML, and CSV formats:
Example Responses
{
"status": "ok",
"error": null,
"data": {
"domain": "google.com",
"recordType": "A",
"propagationComplete": true,
"serversChecked": 10,
"serversResponded": 10,
"uniqueResponses": 1,
"results": [
{
"server": "Google",
"location": "United States",
"ip": "8.8.8.8",
"success": true,
"records": [
"142.250.80.46"
],
"error": null,
"responseTime": 23
},
{
"server": "Cloudflare",
"location": "Global",
"ip": "1.1.1.1",
"success": true,
"records": [
"142.250.80.46"
],
"error": null,
"responseTime": 18
},
{
"server": "OpenDNS",
"location": "United States",
"ip": "208.67.222.222",
"success": true,
"records": [
"142.250.80.46"
],
"error": null,
"responseTime": 31
},
{
"server": "Quad9",
"location": "Global",
"ip": "9.9.9.9",
"success": true,
"records": [
"142.250.80.46"
],
"error": null,
"responseTime": 25
},
{
"server": "Comodo",
"location": "United States",
"ip": "8.26.56.26",
"success": true,
"records": [
"142.250.80.46"
],
"error": null,
"responseTime": 42
},
{
"server": "Level3",
"location": "United States",
"ip": "4.2.2.1",
"success": true,
"records": [
"142.250.80.46"
],
"error": null,
"responseTime": 28
},
{
"server": "Verisign",
"location": "United States",
"ip": "64.6.64.6",
"success": true,
"records": [
"142.250.80.46"
],
"error": null,
"responseTime": 35
},
{
"server": "DNS.Watch",
"location": "Germany",
"ip": "84.200.69.80",
"success": true,
"records": [
"142.250.80.46"
],
"error": null,
"responseTime": 89
},
{
"server": "Yandex",
"location": "Russia",
"ip": "77.88.8.8",
"success": true,
"records": [
"142.250.80.46"
],
"error": null,
"responseTime": 112
},
{
"server": "Hurricane Electric",
"location": "United States",
"ip": "74.82.42.42",
"success": true,
"records": [
"142.250.80.46"
],
"error": null,
"responseTime": 29
}
]
}
}<?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>
<domain>google.com</domain>
<recordType>A</recordType>
<propagationComplete>true</propagationComplete>
<serversChecked>10</serversChecked>
<serversResponded>10</serversResponded>
<uniqueResponses>1</uniqueResponses>
<results>
<result>
<server>Google</server>
<location>United States</location>
<ip>8.8.8.8</ip>
<success>true</success>
<records>
<record>142.250.80.46</record>
</records>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<responseTime>23</responseTime>
</result>
<result>
<server>Cloudflare</server>
<location>Global</location>
<ip>1.1.1.1</ip>
<success>true</success>
<records>
<record>142.250.80.46</record>
</records>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<responseTime>18</responseTime>
</result>
<result>
<server>OpenDNS</server>
<location>United States</location>
<ip>208.67.222.222</ip>
<success>true</success>
<records>
<record>142.250.80.46</record>
</records>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<responseTime>31</responseTime>
</result>
<result>
<server>Quad9</server>
<location>Global</location>
<ip>9.9.9.9</ip>
<success>true</success>
<records>
<record>142.250.80.46</record>
</records>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<responseTime>25</responseTime>
</result>
<result>
<server>Comodo</server>
<location>United States</location>
<ip>8.26.56.26</ip>
<success>true</success>
<records>
<record>142.250.80.46</record>
</records>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<responseTime>42</responseTime>
</result>
<result>
<server>Level3</server>
<location>United States</location>
<ip>4.2.2.1</ip>
<success>true</success>
<records>
<record>142.250.80.46</record>
</records>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<responseTime>28</responseTime>
</result>
<result>
<server>Verisign</server>
<location>United States</location>
<ip>64.6.64.6</ip>
<success>true</success>
<records>
<record>142.250.80.46</record>
</records>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<responseTime>35</responseTime>
</result>
<result>
<server>DNS.Watch</server>
<location>Germany</location>
<ip>84.200.69.80</ip>
<success>true</success>
<records>
<record>142.250.80.46</record>
</records>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<responseTime>89</responseTime>
</result>
<result>
<server>Yandex</server>
<location>Russia</location>
<ip>77.88.8.8</ip>
<success>true</success>
<records>
<record>142.250.80.46</record>
</records>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<responseTime>112</responseTime>
</result>
<result>
<server>Hurricane Electric</server>
<location>United States</location>
<ip>74.82.42.42</ip>
<success>true</success>
<records>
<record>142.250.80.46</record>
</records>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<responseTime>29</responseTime>
</result>
</results>
</data>
</response>
status: ok
error: null
data:
domain: google.com
recordType: A
propagationComplete: true
serversChecked: 10
serversResponded: 10
uniqueResponses: 1
results:
- server: Google
location: United States
ip: 8.8.8.8
success: true
records:
- 142.250.80.46
error: null
responseTime: 23
- server: Cloudflare
location: Global
ip: 1.1.1.1
success: true
records:
- 142.250.80.46
error: null
responseTime: 18
- server: OpenDNS
location: United States
ip: 208.67.222.222
success: true
records:
- 142.250.80.46
error: null
responseTime: 31
- server: Quad9
location: Global
ip: 9.9.9.9
success: true
records:
- 142.250.80.46
error: null
responseTime: 25
- server: Comodo
location: United States
ip: 8.26.56.26
success: true
records:
- 142.250.80.46
error: null
responseTime: 42
- server: Level3
location: United States
ip: 4.2.2.1
success: true
records:
- 142.250.80.46
error: null
responseTime: 28
- server: Verisign
location: United States
ip: 64.6.64.6
success: true
records:
- 142.250.80.46
error: null
responseTime: 35
- server: DNS.Watch
location: Germany
ip: 84.200.69.80
success: true
records:
- 142.250.80.46
error: null
responseTime: 89
- server: Yandex
location: Russia
ip: 77.88.8.8
success: true
records:
- 142.250.80.46
error: null
responseTime: 112
- server: Hurricane Electric
location: United States
ip: 74.82.42.42
success: true
records:
- 142.250.80.46
error: null
responseTime: 29
| key | value |
|---|---|
| domain | google.com |
| recordType | A |
| propagationComplete | true |
| serversChecked | 10 |
| serversResponded | 10 |
| uniqueResponses | 1 |
| results | [{server:Google,location:United States,ip:8.8.8.8,success:true,records:[142.250.80.46],error:null,responseTime:23},{server:Cloudflare,location:Global,ip:1.1.1.1,success:true,records:[142.250.80.46],error:null,responseTime:18},{server:OpenDNS,location:United States,ip:208.67.222.222,success:true,records:[142.250.80.46],error:null,responseTime:31},{server:Quad9,location:Global,ip:9.9.9.9,success:true,records:[142.250.80.46],error:null,responseTime:25},{server:Comodo,location:United States,ip:8.26.56.26,success:true,records:[142.250.80.46],error:null,responseTime:42},{server:Level3,location:United States,ip:4.2.2.1,success:true,records:[142.250.80.46],error:null,responseTime:28},{server:Verisign,location:United States,ip:64.6.64.6,success:true,records:[142.250.80.46],error:null,responseTime:35},{server:DNS.Watch,location:Germany,ip:84.200.69.80,success:true,records:[142.250.80.46],error:null,responseTime:89},{server:Yandex,location:Russia,ip:77.88.8.8,success:true,records:[142.250.80.46],error:null,responseTime:112},{server:Hurricane Electric,location:United States,ip:74.82.42.42,success:true,records:[142.250.80.46],error:null,responseTime:29}] |
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 |
|---|---|---|
domain | string | |
recordType | string | |
propagationComplete | boolean | |
serversChecked | number | |
serversResponded | number | |
uniqueResponses | number | |
| [ ] Array items: | array[10] | |
â”” server | string | |
â”” location | string | |
â”” ip | string | |
â”” success | boolean | |
â”” records | array | |
â”” error | object | |
â”” responseTime | number |
Headers
Required and optional headers for DNS Propagation Checker API requests:
| Header Name | Required | Example Value | Description |
|---|---|---|---|
X-API-Key | required | your_api_key_here | Your APIVerve API key. Found in your dashboard under API Keys. |
Accept | optional | application/json | Specify response format: application/json (default), application/xml, or application/yaml |
User-Agent | optional | MyApp/1.0 | Identifies your application for analytics and debugging purposes |
X-Request-ID | optional | req_123456789 | Custom request identifier for tracking and debugging requests |
Cache-Control | optional | no-cache | Control caching behavior for the request and response |
GraphQL AccessALPHA
Access DNS Propagation Checker through GraphQL to combine it with other API calls in a single request. Query only the dns propagation checker 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 {
dnspropagation(
input: {
domain: "google.com"
type: "A"
}
) {
domain
recordType
propagationComplete
serversChecked
serversResponded
uniqueResponses
results
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The DNS Propagation Checker API supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call DNS Propagation Checker directly from browser-based applications without proxy servers.
| CORS Header | Value | Description |
|---|---|---|
Access-Control-Allow-Origin | * | Accepts requests from any origin |
Access-Control-Allow-Methods | * | Accepts any HTTP method |
Access-Control-Allow-Headers | * | Accepts any request headers |
Browser Usage: You can call DNS Propagation Checker directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.
Rate Limiting
DNS Propagation Checker API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all DNS Propagation Checker users.
| Plan | Rate Limit | Description |
|---|---|---|
| Free | 5 requests/min | Hard rate limit enforced - exceeding will return 429 errors |
| Starter | No Limit | Production ready - standard traffic priority |
| Pro | No Limit | Production ready - preferred traffic priority |
| Mega | No Limit | Production ready - highest traffic priority |
Learn more about rate limiting →
Rate Limit Headers
When rate limits apply, each DNS Propagation Checker response includes headers to help you track your usage:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum number of requests allowed per time window |
X-RateLimit-Remaining | Number of requests remaining in the current window |
X-RateLimit-Reset | Unix timestamp when the rate limit window resets |
Handling Rate Limits
Free Plan: When you exceed your rate limit, DNS Propagation Checker returns a 429 Too Many Requests status code. Your application should implement appropriate backoff logic to handle this gracefully.
Paid Plans: No rate limiting or throttling applied. All paid plans (Starter, Pro, Mega) are production-ready.
Best Practices for DNS Propagation Checker:
- Monitor the rate limit headers to track your DNS Propagation Checker usage (Free plan only)
- Cache dns propagation checker responses where appropriate to reduce API calls
- Upgrade to Pro or Mega for guaranteed no-throttle DNS Propagation Checker performance
Note: DNS Propagation Checker rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using DNS Propagation Checker on Free tier.
Error Codes
The DNS Propagation Checker API uses standard HTTP status codes to indicate success or failure:
| Code | Message | Description | Solution |
|---|---|---|---|
200 | OK | Request successful, data returned | No action needed - request was successful |
400 | Bad Request | Invalid request parameters or malformed request | Check required parameters and ensure values match expected formats |
401 | Unauthorized | Missing or invalid API key | Include x-api-key header with valid API key from dashboard |
403 | Forbidden | API key lacks permission or insufficient credits | Check credit balance in dashboard or upgrade plan |
429 | Too Many Requests | Rate limit exceeded (Free: 5 req/min) | Implement request throttling or upgrade to paid plan |
500 | Internal Server Error | Server error occurred | Retry request after a few seconds, contact support if persists |
503 | Service Unavailable | API temporarily unavailable | Wait and retry, check status page for maintenance updates |
Learn more about error handling →
Need help? Contact support with your X-Request-ID for assistance.
Integrate DNS Propagation Checker with SDKs
Get started quickly with official DNS Propagation Checker SDKs for your preferred language. Each library handles authentication, request formatting, and error handling automatically.
Available for Node.js, Python, C#/.NET, and Android/Java. All SDKs are open source and regularly updated.
Integrate DNS Propagation Checker with No-Code API Tools
Connect the DNS Propagation Checker API to your favorite automation platform without writing code. Build workflows that leverage dns propagation checker data across thousands of apps.





All platforms use your same API key to access DNS Propagation Checker. Visit our integrations hub for step-by-step setup guides.
Frequently Asked Questions
How do I get an API key for DNS Propagation Checker?
How many credits does DNS Propagation Checker cost?
Each successful DNS Propagation Checker 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 dns propagation checker lookups.
Can I use DNS Propagation Checker in production?
The free plan is for testing and development only. For production use of DNS Propagation Checker, 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 DNS Propagation Checker from a browser?
What happens if I exceed my DNS Propagation Checker credit limit?
When you reach your monthly credit limit, DNS Propagation Checker 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.



