DNS Propagation Checker
Check a DNS record against public resolvers around the world and see where a change has landed.
- Next.js
- TypeScript
Confirm your DNS updates have taken effect around the world.
DNS Propagation Checker is a DNS checker API that 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.
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
"domain": "google.com",
"recordType": "A",
"propagationComplete": false,
"serversChecked": 10,
"serversResponded": 10,
"uniqueResponses": 35,
"results": [
{
"server": "Google",
"location": "United States",
"ip": "8.8.8.8",
"success": true,
"records": [
"192.179.16.100",
"192.179.16.101",
"192.179.16.102",
"192.179.16.113",
"192.179.16.138",
"192.179.16.139"
],
"error": null,
"responseTime": 6
},
{
"server": "Cloudflare",
"location": "Global",
"ip": "1.1.1.1",
"success": true,
"records": [
"142.250.177.238"
],
"error": null,
"responseTime": 38
},
{
"server": "OpenDNS",
"location": "United States",
"ip": "208.67.222.222",
"success": true,
"records": [
"173.194.193.100",
"173.194.193.101",
"173.194.193.102",
"173.194.193.113",
"173.194.193.138",
"173.194.193.139"
],
"error": null,
"responseTime": 24
},
{
"server": "Quad9",
"location": "Global",
"ip": "9.9.9.9",
"success": true,
"records": [
"142.250.125.100",
"142.250.125.101",
"142.250.125.102",
"142.250.125.113",
"142.250.125.138",
"142.250.125.139"
],
"error": null,
"responseTime": 13
},
{
"server": "Control D",
"location": "Global",
"ip": "76.76.2.0",
"success": true,
"records": [
"74.125.202.100",
"74.125.202.101",
"74.125.202.102",
"74.125.202.113",
"74.125.202.138",
"74.125.202.139"
],
"error": null,
"responseTime": 15
},
{
"server": "Level3",
"location": "United States",
"ip": "4.2.2.1",
"success": true,
"records": [
"142.251.186.100",
"142.251.186.101",
"142.251.186.102",
"142.251.186.113",
"142.251.186.138",
"142.251.186.139"
],
"error": null,
"responseTime": 22
},
{
"server": "Verisign",
"location": "United States",
"ip": "64.6.64.6",
"success": true,
"records": [
"142.251.211.14"
],
"error": null,
"responseTime": 24
},
{
"server": "DNS4EU",
"location": "Europe",
"ip": "86.54.11.100",
"success": true,
"records": [
"142.251.34.238"
],
"error": null,
"responseTime": 116
},
{
"server": "Yandex",
"location": "Russia",
"ip": "77.88.8.8",
"success": true,
"records": [
"142.251.38.110"
],
"error": null,
"responseTime": 149
},
{
"server": "Hurricane Electric",
"location": "United States",
"ip": "74.82.42.42",
"success": true,
"records": [
"142.251.214.206"
],
"error": null,
"responseTime": 18
}
]
}
}
Check a DNS record against public resolvers around the world and see where a change has landed.
DNS Propagation Checker works by querying the same DNS record from multiple geographically distributed DNS servers. This helps identify if recent DNS changes have propagated globally or if some regions still have cached old records.
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
Same data, same APIVerve account, same credit balance — one key works on all of them.
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.
| Parameter | Type | Example | Description |
|---|---|---|---|
domainRequired | string | google.com | The domain name to check propagation for domain |
| Parameter | Type | Example | Description |
|---|---|---|---|
typeOptional | string | A | The DNS record type to checkAAAAAMXNSTXTCNAMEdefault A |
curl "https://api.apiverve.com/v1/dnspropagation?domain=google.com&type=A" \
-H "x-api-key: YOUR_API_KEY"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-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
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.
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.
{
"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": "Control D",
"location": "Global",
"ip": "76.76.2.0",
"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": "DNS4EU",
"location": "Europe",
"ip": "86.54.11.100",
"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
}
]
}
}
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 |
|---|---|---|---|
domain | string | "google.com" | The domain name that was checked for propagation |
recordType | string | "A" | The DNS record type that was queried (A, AAAA, MX, etc) |
propagationComplete | boolean | true | Whether DNS has propagated across all servers |
serversChecked | number | 10 | Total number of DNS servers checked globally |
serversResponded | number | 10 | Number of servers that responded successfully |
uniqueResponses | number | 1 | Number of unique DNS values returned by all servers |
results | array[10] | Array of propagation results from each DNS server checked | |
server | string | "Google" | DNS server provider name (Google, Cloudflare, OpenDNS, etc) |
location | string | "United States" | Geographic location of the DNS server |
ip | string | "8.8.8.8" | IP address of the DNS server being queried |
success | boolean | true | Whether the query to this server succeeded |
records | array | [142.250.80.46] | Array of DNS records returned by this server |
error | object | null | Error message if query failed, null if successful |
responseTimePremium | number | 23 | Response time in milliseconds from this DNS server |
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 |
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. |
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 | DNS Propagation Checker calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 6 | Free |
| Starter | $29.99 | 200,000 | 6,666 | $4.50 |
| Pro | $99.99 | 1,000,000 | 33,333 | $3.00 |
| Mega | $299.99 | 4,000,000 | 133,333 | $2.25 |
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.
No SDK to install — this is a plain HTTPS call to /v1/dnspropagation with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/dnspropagation" \
-H "x-api-key: YOUR_API_KEY"Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Install the Node.js SDK, then call the DNS Propagation Checker API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/dnspropagationconst res = await fetch("https://api.apiverve.com/v1/dnspropagation", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
No SDK to install — this is a plain HTTPS call to /v1/dnspropagation with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/dnspropagation",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Install the C# / .NET SDK, then call the DNS Propagation Checker API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.DNSPropagationCheckerusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/dnspropagation");
Console.WriteLine(json);Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
No SDK to install — this is a plain HTTPS call to /v1/dnspropagation 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/dnspropagation", 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))Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
No SDK to install — this is a plain HTTPS call to /v1/dnspropagation with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/dnspropagation");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
No SDK to install — this is a plain HTTPS call to /v1/dnspropagation with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/dnspropagation")
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.bodyOnly the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Drop an interactive DNS Propagation Checker form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the DNS Propagation Checker API.
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
The DNS Migration Checklist Nobody Talks AboutDNS propagation takes 24-48 hours. Except when it doesn't. Here's the zero-downtime DNS migration checklist.Read
7 SSL Certificate Problems That Kill TrustExpired certs, mismatched domains, weak encryption. A practical checklist for catching SSL issues before your users do.Read