DNS propagation
DNS Live stream /api/v1/dns/propagationQuery 15 global resolvers — see if your DNS change has propagated worldwide.
Inconsistent — propagation in progress
15 answer sets A
Queried 15 resolvers across the world for adwords.google.com.
Cloudflare
1.1.1.1
31 ms
- 142.250.27.100
- 142.250.27.113
- 142.250.27.138
- 142.250.27.101
- 142.250.27.139
- 142.250.27.102
Cloudflare 2
1.0.0.1
32 ms
- 142.250.102.100
- 142.250.102.101
- 142.250.102.139
- 142.250.102.113
- 142.250.102.102
- 142.250.102.138
Google
8.8.8.8
30 ms
- 142.250.27.100
- 142.250.27.102
- 142.250.27.113
- 142.250.27.138
- 142.250.27.139
- 142.250.27.101
Google 2
8.8.4.4
29 ms
- 142.250.27.139
- 142.250.27.101
- 142.250.27.138
- 142.250.27.113
- 142.250.27.102
- 142.250.27.100
Quad9
9.9.9.9
29 ms
- 142.250.102.100
- 142.250.102.113
- 142.250.102.139
- 142.250.102.101
- 142.250.102.102
- 142.250.102.138
OpenDNS
208.67.222.222
62 ms
- 142.250.27.102
- 142.250.27.113
- 142.250.27.138
- 142.250.27.139
- 142.250.27.100
- 142.250.27.101
OpenDNS 2
208.67.220.220
51 ms
- 142.250.27.113
- 142.250.27.138
- 142.250.27.139
- 142.250.27.100
- 142.250.27.101
- 142.250.27.102
Level 3
4.2.2.2
33 ms
- 142.251.127.113
- 142.251.127.100
- 142.251.127.138
- 142.251.127.101
- 142.251.127.102
- 142.251.127.139
Comodo Secure
8.26.56.26
36 ms
- 142.251.127.100
- 142.251.127.138
- 142.251.127.101
- 142.251.127.113
- 142.251.127.139
- 142.251.127.102
Verisign
64.6.64.6
31 ms
- 142.251.127.139
- 142.251.127.101
- 142.251.127.113
- 142.251.127.100
- 142.251.127.102
- 142.251.127.138
Yandex
77.88.8.8
124 ms
- 74.125.205.139
- 74.125.205.100
- 74.125.205.101
- 74.125.205.113
- 74.125.205.138
- 74.125.205.102
CleanBrowsing
185.228.168.9
34 ms
- 192.178.211.138
- 192.178.211.101
- 192.178.211.100
- 192.178.211.102
- 192.178.211.139
- 192.178.211.113
Control D
76.76.2.0
31 ms
- 192.178.223.113
- 192.178.223.139
- 192.178.223.102
- 192.178.223.138
- 192.178.223.100
- 192.178.223.101
AdGuard
94.140.14.14
33 ms
- 108.177.123.138
- 108.177.123.101
- 108.177.123.100
- 108.177.123.139
- 108.177.123.113
- 108.177.123.102
Mullvad
194.242.2.2
32 ms
No records returned.
Distinct answer sets
1
142.250.27.100,142.250.27.113,142.250.27.138,142.250.27.101,142.250.27.139,142.250.27.102
2
142.250.102.100,142.250.102.101,142.250.102.139,142.250.102.113,142.250.102.102,142.250.102.138
3
142.250.27.100,142.250.27.102,142.250.27.113,142.250.27.138,142.250.27.139,142.250.27.101
4
142.250.27.139,142.250.27.101,142.250.27.138,142.250.27.113,142.250.27.102,142.250.27.100
5
142.250.102.100,142.250.102.113,142.250.102.139,142.250.102.101,142.250.102.102,142.250.102.138
6
142.250.27.102,142.250.27.113,142.250.27.138,142.250.27.139,142.250.27.100,142.250.27.101
7
142.250.27.113,142.250.27.138,142.250.27.139,142.250.27.100,142.250.27.101,142.250.27.102
8
142.251.127.113,142.251.127.100,142.251.127.138,142.251.127.101,142.251.127.102,142.251.127.139
9
142.251.127.100,142.251.127.138,142.251.127.101,142.251.127.113,142.251.127.139,142.251.127.102
10
142.251.127.139,142.251.127.101,142.251.127.113,142.251.127.100,142.251.127.102,142.251.127.138
11
74.125.205.139,74.125.205.100,74.125.205.101,74.125.205.113,74.125.205.138,74.125.205.102
12
192.178.211.138,192.178.211.101,192.178.211.100,192.178.211.102,192.178.211.139,192.178.211.113
13
192.178.223.113,192.178.223.139,192.178.223.102,192.178.223.138,192.178.223.100,192.178.223.101
14
108.177.123.138,108.177.123.101,108.177.123.100,108.177.123.139,108.177.123.113,108.177.123.102
15
(empty)
How to use DNS propagation
-
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
Click "Inspect"
host.tools issues real probes (DNS, HTTP, TCP, TLS, WHOIS where applicable) and renders the result in milliseconds.
-
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=adwords.google.com
curl -s '/api/v1/dns/propagation?q=adwords.google.com'
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.
- ✓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