DNS Propagation

What It Does

Queries the specified DNS record from 8 major public DNS resolvers in parallel — Cloudflare (1.1.1.1), Google (8.8.8.8), Quad9 (9.9.9.9), OpenDNS (208.67.222.222), AdGuard, DNS.SB, Mullvad, and NextDNS — and compares results. Reports propagation status (complete, partial, none), identifies inconsistent responses, and calculates propagation percentage. Classifies the result as `aligned`, `propagating`, `geo_distributed`, or `inconsistent` so users can distinguish stale-cache lag from intentional geo-load balancing (e.g. Azure Traffic Manager, AWS Route 53 latency routing).

Why It's Useful

After DNS changes, propagation can take hours to complete globally. Some ISP resolvers cache aggressively beyond the TTL value (RFC 2308). This endpoint tests against 8 major public resolvers across multiple regions that correctly honor TTL, giving you a reliable propagation baseline to verify changes and troubleshoot DNS-related user reports.

Use Cases

Parameters

Response Fields

Code Examples

curl "https://api.edgedns.dev/v1/dns/propagation" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d "domain=example.com"

const response = await fetch(
  'https://api.edgedns.dev/v1/dns/propagation?domain=example.com',
  {
    headers: {
      'Authorization': 'Bearer YOUR_API_KEY'
    }
  }
);

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

import requests

response = requests.get(
    'https://api.edgedns.dev/v1/dns/propagation',
    headers={'Authorization': 'Bearer YOUR_API_KEY'},
    params={
    'domain': 'example.com'
    }
)

data = response.json()
print(data)

Related Endpoints

External References

Learn more about the standards and protocols behind this endpoint.