Overview
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.
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl "https://api.apiverve.com/v1/dnspropagation?domain=google.com&type=A" \
-H "x-api-key: your_api_key_here"const res = await fetch('https://api.apiverve.com/v1/dnspropagation?domain=google.com&type=A', {
headers: { 'x-api-key': 'your_api_key_here' },
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.get(
"https://api.apiverve.com/v1/dnspropagation?domain=google.com&type=A",
headers={"x-api-key": "your_api_key_here"},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/dnspropagation?domain=google.com&type=A", nil)
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
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.
Parameters
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
domainRequired | string | The domain name to check propagation for domain |
typeOptional | string | The DNS record type to checkAAAAAMXNSTXTCNAMEdefault A |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"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 |
responseTimePremium | number | 23 | Response time in milliseconds from this DNS server |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- 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
Other ways to use DNS Propagation Checker
Set up DNS Propagation Checker on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Domain Data: