DNS Propagation Checker API GET

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.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/dnspropagation

Verification

Format

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

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // DNS Propagation Checker response payload
  }
}

About the DNS Propagation Checker API

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.

What people use it for

DNS Change Verification: Verify that DNS changes have propagated globally after updating nameservers, A records, or other DNS settings
Troubleshooting: Diagnose DNS issues by checking if different regions see different DNS values
Migration Monitoring: Monitor DNS propagation during domain or hosting migrations to know when it's safe to proceed
TTL Verification: Verify that TTL settings are working correctly by checking propagation timing

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 DNS Propagation Checker

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 DNS Propagation Checker API.

Read the docs →

What does the DNS Propagation Checker API do?

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.

How do I authenticate DNS Propagation Checker 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 DNS Propagation Checker API cost?

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

How fast is the DNS Propagation Checker 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 DNS Propagation Checker 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 DNS Propagation Checker API use?

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

Request parameters — GET /v1/dnspropagation

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 name to check propagation for domain

Optional

Parameter	Type	Example	Description
`type`Optional	string	`A`	The DNS record type to check `AAAAAMXNSTXTCNAME` default A

Example request

1
2

curl "https://api.apiverve.com/v1/dnspropagation?domain=google.com&type=A" \
  -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/dnspropagation

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": {
    "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 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
`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
`responseTime`Premium	number	`23`	Response time in milliseconds from this DNS server

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 — 30 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	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.

Compare all pricing tiers →

Call it from cURL — GET /v1/dnspropagation

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

1
2

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

Resources

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

Also published for

@apiverve/dnspropagationnpm APIVerve.API.DNSPropagationCheckerNuGet

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/dnspropagation

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.

Install — npm

npm install @apiverve/dnspropagation

Node.js

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

Resources

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

Also published for

APIVerve.API.DNSPropagationCheckerNuGet

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

Call it from Python — GET /v1/dnspropagation

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.

Python

import requests

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

Resources

Also published for

@apiverve/dnspropagationnpm APIVerve.API.DNSPropagationCheckerNuGet

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/dnspropagation

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.

Install — NuGet

dotnet add package APIVerve.API.DNSPropagationChecker

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/dnspropagation");
Console.WriteLine(json);

Resources

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

Also published for

@apiverve/dnspropagationnpm

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

Call it from Go — GET /v1/dnspropagation

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))

Resources

Also published for

@apiverve/dnspropagationnpm APIVerve.API.DNSPropagationCheckerNuGet

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

Call it from PHP — GET /v1/dnspropagation

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.

PHP

$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;

Resources

Also published for

@apiverve/dnspropagationnpm APIVerve.API.DNSPropagationCheckerNuGet

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

Call it from Ruby — GET /v1/dnspropagation

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.

Ruby

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.body

Resources

Also published for

@apiverve/dnspropagationnpm APIVerve.API.DNSPropagationCheckerNuGet

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

All articles →

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

DNS Propagation Checker API GET

Try it — live request, no key required

About the DNS Propagation Checker API

What people use it for

Ways to call it

Other ways to use DNS Propagation Checker

Questions.

Request parameters — GET /v1/dnspropagation

Required

Optional

Authentication

Response — GET /v1/dnspropagation

Response fields

Response headers

Errors

What a call costs — 30 credits per call

Call it from cURL — GET /v1/dnspropagation

Resources

Also published for

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

Resources

Also published for

Call it from Python — GET /v1/dnspropagation

Resources

Also published for

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

Resources

Also published for

Call it from Go — GET /v1/dnspropagation

Resources

Also published for

Call it from PHP — GET /v1/dnspropagation

Resources

Also published for

Call it from Ruby — GET /v1/dnspropagation

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — DNS Propagation Checker API

Domain Data

Related articles

Ready to build with DNS Propagation Checker? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog