DNS propagation
DNS Live stream /api/v1/dns/propagationQuery 15 global resolvers — see if your DNS change has propagated worldwide.
Inconsistent — propagation in progress
9 answer sets A
Queried 15 resolvers across the world for services.google.com.
- www3.l.google.com.
- 172.217.23.238
- www3.l.google.com.
- 172.217.23.238
- www3.l.google.com.
- 142.251.209.238
- www3.l.google.com.
- 142.251.209.238
- www3.l.google.com.
- 172.217.171.110
- www3.l.google.com.
- 142.251.209.238
- www3.l.google.com.
- 142.251.209.238
- www3.l.google.com.
- 192.178.24.174
- www3.l.google.com.
- 142.251.20.100
- 142.251.20.138
- 142.251.20.139
- 142.251.20.113
- 142.251.20.101
- 142.251.20.102
- www3.l.google.com.
- 173.194.222.100
- 173.194.222.102
- 173.194.222.138
- 173.194.222.101
- 173.194.222.139
- 173.194.222.113
- www3.l.google.com.
- 74.125.128.113
- 74.125.128.101
- 74.125.128.138
- 74.125.128.139
- 74.125.128.102
- 74.125.128.100
- www3.l.google.com.
- 172.217.171.110
- www3.l.google.com.
- 142.251.134.174
www3.l.google.com.,172.217.23.238
www3.l.google.com.,142.251.209.238
www3.l.google.com.,172.217.171.110
www3.l.google.com.,192.178.24.174
(empty)
www3.l.google.com.,142.251.20.100,142.251.20.138,142.251.20.139,142.251.20.113,142.251.20.101,142.251.20.102
www3.l.google.com.,173.194.222.100,173.194.222.102,173.194.222.138,173.194.222.101,173.194.222.139,173.194.222.113
www3.l.google.com.,74.125.128.113,74.125.128.101,74.125.128.138,74.125.128.139,74.125.128.102,74.125.128.100
www3.l.google.com.,142.251.134.174
-
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.
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/v1/dns/propagation?q=services.google.com
curl -s '/api/v1/dns/propagation?q=services.google.com'
<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.
Common questions
Is DNS propagation free?
Where does the data come from?
How fresh are the results?
?nocache=1 for a forced refresh.Can I run this from the command line?
host.tools dns propagation YOUR_INPUT.Can I monitor results over time?
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