host.tools

DNS propagation

DNS Live stream /api/v1/dns/propagation

Query 15 global resolvers — see if your DNS change has propagated worldwide.

Try: host.com checkhost.com google.com
Related: DNS lookup (dig) DNS propagation Domain WHOIS SSL certificate inspector HTTP headers Security headers grader MX lookup SPF tester DMARC tester

Inconsistent — propagation in progress

14 answer sets A

Queried 15 resolvers across the world for auth.staging.widn.ai.

Cloudflare
1.1.1.1
49 ms
  • d1h5wxv7b1nt1m.cloudfront.net.
  • 18.239.83.13
  • 18.239.83.124
  • 18.239.83.11
  • 18.239.83.51
Cloudflare 2
1.0.0.1
63 ms
  • d1h5wxv7b1nt1m.cloudfront.net.
  • 18.239.83.11
  • 18.239.83.13
  • 18.239.83.124
  • 18.239.83.51
Google
8.8.8.8
72 ms
  • d1h5wxv7b1nt1m.cloudfront.net.
  • 18.239.208.61
  • 18.239.208.89
  • 18.239.208.88
  • 18.239.208.12
Google 2
8.8.4.4
71 ms
  • d1h5wxv7b1nt1m.cloudfront.net.
  • 18.239.208.61
  • 18.239.208.12
  • 18.239.208.88
  • 18.239.208.89
Quad9
9.9.9.9
42 ms
  • d1h5wxv7b1nt1m.cloudfront.net.
  • 18.245.46.109
  • 18.245.46.45
  • 18.245.46.126
  • 18.245.46.15
OpenDNS
208.67.222.222
101 ms
  • d1h5wxv7b1nt1m.cloudfront.net.
  • 18.239.208.61
  • 18.239.208.88
  • 18.239.208.89
  • 18.239.208.12
OpenDNS 2
208.67.220.220
98 ms
  • d1h5wxv7b1nt1m.cloudfront.net.
  • 18.239.208.61
  • 18.239.208.88
  • 18.239.208.89
  • 18.239.208.12
Level 3
4.2.2.2
165 ms
  • d1h5wxv7b1nt1m.cloudfront.net.
  • 18.245.46.126
  • 18.245.46.109
  • 18.245.46.15
  • 18.245.46.45
Comodo Secure
8.26.56.26
137 ms
  • d1h5wxv7b1nt1m.cloudfront.net.
  • 18.245.46.109
  • 18.245.46.45
  • 18.245.46.15
  • 18.245.46.126
Verisign
64.6.64.6
48 ms
  • d1h5wxv7b1nt1m.cloudfront.net.
  • 18.245.46.15
  • 18.245.46.126
  • 18.245.46.45
  • 18.245.46.109
Yandex
77.88.8.8
748 ms
  • d1h5wxv7b1nt1m.cloudfront.net.
  • 108.157.229.84
  • 108.157.229.125
  • 108.157.229.58
  • 108.157.229.2
CleanBrowsing
185.228.168.9
71 ms
  • d1h5wxv7b1nt1m.cloudfront.net.
  • 18.245.46.45
  • 18.245.46.126
  • 18.245.46.15
  • 18.245.46.109
Control D
76.76.2.0
57 ms
  • d1h5wxv7b1nt1m.cloudfront.net.
  • 18.239.83.13
  • 18.239.83.51
  • 18.239.83.124
  • 18.239.83.11
AdGuard
94.140.14.14
180 ms
  • d1h5wxv7b1nt1m.cloudfront.net.
  • 3.163.63.91
  • 3.163.63.111
  • 3.163.63.77
  • 3.163.63.44
Mullvad
194.242.2.2
39 ms
No records returned.
Distinct answer sets
1 d1h5wxv7b1nt1m.cloudfront.net.,18.239.83.13,18.239.83.124,18.239.83.11,18.239.83.51
2 d1h5wxv7b1nt1m.cloudfront.net.,18.239.83.11,18.239.83.13,18.239.83.124,18.239.83.51
3 d1h5wxv7b1nt1m.cloudfront.net.,18.239.208.61,18.239.208.89,18.239.208.88,18.239.208.12
4 d1h5wxv7b1nt1m.cloudfront.net.,18.239.208.61,18.239.208.12,18.239.208.88,18.239.208.89
5 d1h5wxv7b1nt1m.cloudfront.net.,18.245.46.109,18.245.46.45,18.245.46.126,18.245.46.15
6 d1h5wxv7b1nt1m.cloudfront.net.,18.239.208.61,18.239.208.88,18.239.208.89,18.239.208.12
7 d1h5wxv7b1nt1m.cloudfront.net.,18.245.46.126,18.245.46.109,18.245.46.15,18.245.46.45
8 d1h5wxv7b1nt1m.cloudfront.net.,18.245.46.109,18.245.46.45,18.245.46.15,18.245.46.126
9 d1h5wxv7b1nt1m.cloudfront.net.,18.245.46.15,18.245.46.126,18.245.46.45,18.245.46.109
10 d1h5wxv7b1nt1m.cloudfront.net.,108.157.229.84,108.157.229.125,108.157.229.58,108.157.229.2
11 d1h5wxv7b1nt1m.cloudfront.net.,18.245.46.45,18.245.46.126,18.245.46.15,18.245.46.109
12 d1h5wxv7b1nt1m.cloudfront.net.,18.239.83.13,18.239.83.51,18.239.83.124,18.239.83.11
13 d1h5wxv7b1nt1m.cloudfront.net.,3.163.63.91,3.163.63.111,3.163.63.77,3.163.63.44
14 (empty)
How to use DNS propagation
  1. 1
    Paste your input

    Enter the value at the top — domain, IP, URL, email, ASN, hash, whatever fits this tool. The smart input auto-detects type.

  2. 2
    Click "Inspect"

    host.tools issues real probes (DNS, HTTP, TCP, TLS, WHOIS where applicable) and renders the result in milliseconds.

  3. 3
    Open the API tab

    Every web tool has a sibling /api/v1/dns/propagation JSON endpoint with the same payload. One copy-as-curl click and you're scripting it.

Why this matters

DNS is the routing layer for everything you do on the internet. A bad TTL, a missing MX or an unsigned zone propagates outages and inboxes-full-of-spam in minutes. Verify before you ship.

API equivalent
/api/v1/dns/propagation?q=auth.staging.widn.ai 
curl -s '/api/v1/dns/propagation?q=auth.staging.widn.ai'
Embed this tool
<iframe src="/dns/propagation?q={INPUT}&embed=1"
  width="100%" height="600" frameborder="0"></iframe>

Drop into any HTML page. The embed=1 flag hides nav and footer.

FAQ · DNS propagation

Common questions

Is DNS propagation free?
Yes — every tool is free on the web with a 200/hour rate limit per IP. The matching API endpoint /api/v1/dns/propagation is free up to 100 requests/hour, no key required.
Where does the data come from?
Real-time probes against authoritative sources (DNS root, RIRs, registries, the target server itself), plus partner data feeds from hostinfo.com (GeoIP/ASN) and hostcheck.com (reputation).
How fresh are the results?
Live by default. Cached for 5 minutes to make repeat queries instant; pass ?nocache=1 for a forced refresh.
Can I run this from the command line?
Yes — every tool ships with a copy-as-curl. There's also an official CLI: host.tools dns propagation YOUR_INPUT.
Can I monitor results over time?
Pro tier lets you schedule any tool to run every 1/5/15/60 min and alert on diff. See monitors.
host.tools Pro

Run DNS propagation on a schedule. Get pinged when it changes.

Pro gets you bulk lookups, monitors, webhook alerts, history, exports and 10,000 API calls/day. $19/mo.

See pricing Tour monitors
  • ✓Schedule any tool — every 1, 5, 15, 60 min
  • ✓Diff against last run, alert on change
  • ✓Webhook + email + Slack + PagerDuty + OpsGenie
  • ✓Bulk CSV upload, 1,000 inputs per job
  • ✓Export results as CSV / NDJSON / Excel
  • ✓90-day history, comparison view