APIVerve
Monitor DNS Changes Across the Globe

DNS Propagation Checker API.

Check DNS record propagation from multiple global locations. Verify that DNS changes have propagated worldwide, monitor propagation progress, and troubleshoot DNS issues.

Get your free API keyRead the docs
Free tier, no card< 200ms responses99.9% uptime SLA
GET/v1/dnspropagationlive
Response200 OK · sample
{
  "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
      }
    ]
  }
}
Sample response · verify to run one live call, no signup
Integrates with your favorite tools
LangChainn8nZapierMakePipedreamPower AutomatePostman
How it works

DNS Propagation Checker API

Check DNS record propagation from multiple global locations. Verify that DNS changes have propagated worldwide, monitor propagation progress, and troubleshoot DNS issues.

  • Check propagation from multiple global locations
  • Real-time propagation status updates
  • Support for all DNS record types
  • Verify expected values have propagated
  1. 1

    Send one request

    A single authenticated GET with the location you care about — no SDK required.

    GET /v1/dnspropagation?query=…
x-api-key: your_key
  2. 2

    We do the aggregation

    Each request pulls from multiple upstream sources and computes the derived fields for you.

  3. 3

    Get clean JSON back

    One structured object, typically under 200 ms — ready to render.

    { domain, recordType, propagationComplete, … }
The response

Everything in a single call.

/v1/dnspropagationapplication/json
domain"google.com"
recordType"A"
propagationCompletetrue
serversChecked10
serversResponded10
uniqueResponses1
resultsarray of 10
Use cases

What developers build with it.

Real applications shipping on this endpoint today — each with the numbers that made it worth wiring up.

See every use case

DNS Migration Verification

Use our DNS Propagation API to automatically check propagation from multiple global locations. Set up automated monitoring to alert you when propagation is complete.

Verify propagation from multiple continentsAutomate migration workflowsReduce risk of premature infrastructure changes
Zero downtimemigrations with verification
Automate 100%of propagation checks
Global coveragefrom 10+ locations

DevOps & CI/CD Integration

Integrate our API into CI/CD pipelines to automatically verify DNS propagation. Block deployments until DNS is fully propagated, then proceed automatically.

Automated deployment gatesReduce deployment failuresIntegrate with any CI/CD tool
Faster deploymentswith automated checks
Eliminate manualverification steps
CI/CD integrationin minutes
Start coding

Call it in your language.

Copy a working request, or install a typed SDK. Same endpoint, same key.

const res = await fetch("https://api.apiverve.com/v1/dnspropagation?domain=google.com&type=A", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);
Included in your key

One subscription, the whole monitor dns changes across the globe stack.

Every related API ships with your key — no separate plans, no extra keys, one bill.

See pricing
8APIs in this bundle
99.9%uptime SLA
The bundle
dnspropagationYou’re herednslookupmxlookupwhoislookupnameserversdnsseccheckdomainavailabilitysslchecker
No code required

Wire it into the tools you already run.

Ready-made recipes for Zapier, Make, and n8n — trigger on an event, and the data lands where your team works.

Google Sheets
DNS Propagation Log in Google Sheets
WhenNew row added in Google Sheets with domain
ThenCheck DNS propagation → write propagationComplete, serversChecked, and serversResponded to the row
Slack
DNS Propagation Alert in Slack
WhenScheduled periodic trigger
ThenCheck DNS propagation → if propagationComplete is true, post confirmation with serversResponded to Slack
Airtable
DNS Propagation Tracker in Airtable
WhenNew record created in Airtable
ThenCheck DNS propagation for domain → update record with propagationComplete, serversChecked, and results
Notion
DNS Propagation Dashboard in Notion
WhenNew page created in Notion
ThenCheck DNS propagation → update page with domain, recordType, propagationComplete, and results details
Salesforce
DNS Propagation on Salesforce Domain Records
WhenNew record created in Salesforce
ThenCheck DNS propagation → update record with domain, propagationComplete, and serversChecked
GitHub
GitHub Pages DNS Propagation Check
WhenNew repository with custom domain configured
ThenCheck DNS propagation → post propagationComplete and serversResponded as issue comment
Browse all integrations
Learn

Understand the data behind the API.

Understanding DNS Propagation

Learn how DNS changes spread across the global DNS infrastructure.

TTL Best Practices for DNS Changes

How to optimize TTL settings for smooth DNS migrations.

DNS Migration Strategies

Proven approaches for zero-downtime DNS migrations.

Questions about the API

How long does DNS propagation typically take?
DNS propagation usually takes 24-48 hours to complete globally, but can be faster (minutes to hours) depending on TTL settings. Lower TTL values mean faster propagation, while higher TTLs may cause delays as caches expire.
From which locations do you check DNS propagation?
We check DNS propagation from multiple locations across North America, Europe, Asia-Pacific, South America, and other regions to give you a comprehensive view of global propagation status.
Can I check propagation for any DNS record type?
Yes! Our API supports checking propagation for A, AAAA, MX, TXT, CNAME, NS, SOA, and other DNS record types. Specify the record type in your API request.
Why do some locations show different results?
Different DNS servers cache records for varying durations based on TTL. During propagation, some locations may still have old cached values while others show the new records. This is normal DNS behavior.
How can I speed up DNS propagation?
Lower your TTL values before making changes (ideally 24-48 hours in advance). After propagation completes, you can increase TTL again. Note that you cannot force other DNS servers to refresh their caches.
Can I verify a specific expected value has propagated?
Yes! Include the expected value in your API request, and we will indicate whether each location returns the expected result. This is useful for verifying migrations or DNS changes.
How often should I check propagation status?
For most changes, checking every 15-30 minutes is sufficient. Our API has no rate limiting issues for reasonable polling intervals. You can also set up automated monitoring.
What causes propagation delays?
High TTL values, DNS caching at ISP level, and geographic distance from authoritative nameservers can cause delays. Some ISPs also cache DNS records longer than specified TTLs.

Start building with the DNS Propagation Checker API. Free tier, no card required — your key is live in minutes.

Get your free API key→Read the docs

Bonus: 300+ more APIs

The same key unlocks every other APIVerve endpoint — reach for them when you need them.

Browse the catalog