DNS Propagation Checker API

OnlineCredit Usage:15 per callLive Data

avg: 3000ms|p50: 2640ms|p75: 3240ms|p90: 3960ms|p99: 5400ms

Overview

To use DNS Propagation Checker, you need an API key. You can get one by creating a free account and visiting your dashboard.

Live Test DNS Propagation Checker API

GET Endpoint

URL

https://api.apiverve.com/v1/dnspropagation

Example

How to call the DNS Propagation Checker API in different programming languages.

cURL Request

curl -X GET \
  "https://api.apiverve.com/v1/dnspropagation?domain=google.com&type=A" \
  -H "X-API-Key: your_api_key_here"

JavaScript (Fetch API)

const response = await fetch('https://api.apiverve.com/v1/dnspropagation?domain=google.com&type=A', {
  method: 'GET',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  }
});

const data = await response.json();
console.log(data);

Python (Requests)

import requests

headers = {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
}

response = requests.get('https://api.apiverve.com/v1/dnspropagation?domain=google.com&type=A', headers=headers)

data = response.json()
print(data)

Go (net/http)

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

Example 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
      }
    ]
  }
}

Authentication

The DNS Propagation Checker API requires authentication via API key. Include your API key in the request header:

Required Header

X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

Test the DNS Propagation Checker API directly in your browser with live requests and responses.

Live Test DNS Propagation Checker APITry it free with instant results - no signup required

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`)	-	`google.com`
`type`	string	`optional`	The DNS record type to check Supported values: `AAAAAMXNSTXT`	`A`	`A`

Response

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

200 OK

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

YAML Response

200 OK

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

CSV Response

200 OK

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}]

Live Test DNS Propagation Checker API

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
`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
[ ] Array items:	array[10]	`Array of objects`	Array of propagation results from each DNS server checked
└ `server`	string	`"Google"`	-
└ `location`	string	`"United States"`	-
└ `ip`	string	`"8.8.8.8"`	-
└ `success`	boolean	`true`	-
└ `records`	array	`["142.250.80.46"]`	-
└ `error`	object	`null`	-
└ `responseTime`	number	`23`	-

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

Test DNS Propagation Checker in the GraphQL Explorer to confirm availability and experiment with queries.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

GraphQL Endpoint

POST https://api.apiverve.com/v1/graphql

GraphQL Query Example

query {
  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.

Try in GraphQL Explorer GraphQL Documentation

CORS Support

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

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

Official DNS Propagation Checker packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →

JitPack

No-Code Integrations

DNS Propagation Checker works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →

Zapier

Make

Pipedream

n8n

Power Automate

Frequently Asked Questions

How do I get an API key for DNS Propagation Checker?

Sign up for a free account at dashboard.apiverve.com. Your API key will be automatically generated and available in your dashboard. The same key works for DNS Propagation Checker and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.

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?

Yes! The DNS Propagation Checker API supports CORS with wildcard configuration, so you can call it directly from browser-based JavaScript without needing a proxy server. See the CORS section above for details.

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.

What's Next?

Continue your journey with these recommended resources

Browse All APIs

Explore our complete catalog of APIs

Authentication Guide

Learn about API keys and security

Rate Limits

Understand usage limits and best practices

Was this page helpful?

DNS Propagation Checker API

Overview

GET Endpoint

Example

Authentication

Interactive API Playground

Parameters

Check DNS Propagation

Response

Other Response Formats

Response Structure

Response Data Fields

Headers

GraphQL AccessALPHA

CORS Support

Rate Limiting

Error Codes

SDKs for DNS Propagation Checker

No-Code Integrations

Frequently Asked Questions

People who used this also used...

WHOIS Lookup

URL Unshortener

URL Title

What's Next?

Browse All APIs

Authentication Guide

Rate Limits