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 auth.liberia.healthcare.sandtech.app.
Cloudflare
1.1.1.1
56 ms
- do1ckqc2wqktx.cloudfront.net.
- 18.245.31.92
- 18.245.31.6
- 18.245.31.54
- 18.245.31.118
Cloudflare 2
1.0.0.1
31 ms
- do1ckqc2wqktx.cloudfront.net.
- 18.245.31.118
- 18.245.31.6
- 18.245.31.54
- 18.245.31.92
Google
8.8.8.8
67 ms
- do1ckqc2wqktx.cloudfront.net.
- 13.225.239.2
- 13.225.239.20
- 13.225.239.114
- 13.225.239.126
Google 2
8.8.4.4
35 ms
- do1ckqc2wqktx.cloudfront.net.
- 13.225.239.2
- 13.225.239.20
- 13.225.239.126
- 13.225.239.114
Quad9
9.9.9.9
60 ms
- do1ckqc2wqktx.cloudfront.net.
- 3.173.161.122
- 3.173.161.93
- 3.173.161.92
- 3.173.161.105
OpenDNS
208.67.222.222
137 ms
- do1ckqc2wqktx.cloudfront.net.
- 13.225.239.20
- 13.225.239.114
- 13.225.239.126
- 13.225.239.2
OpenDNS 2
208.67.220.220
118 ms
- do1ckqc2wqktx.cloudfront.net.
- 13.225.239.126
- 13.225.239.2
- 13.225.239.20
- 13.225.239.114
Level 3
4.2.2.2
108 ms
- do1ckqc2wqktx.cloudfront.net.
- 13.32.220.20
- 13.32.220.6
- 13.32.220.100
- 13.32.220.114
Comodo Secure
8.26.56.26
70 ms
- do1ckqc2wqktx.cloudfront.net.
- 18.245.31.6
- 18.245.31.118
- 18.245.31.92
- 18.245.31.54
Verisign
64.6.64.6
86 ms
- do1ckqc2wqktx.cloudfront.net.
- 3.173.161.105
- 3.173.161.92
- 3.173.161.122
- 3.173.161.93
Yandex
77.88.8.8
416 ms
- do1ckqc2wqktx.cloudfront.net.
- 3.164.230.70
- 3.164.230.63
- 3.164.230.115
- 3.164.230.30
CleanBrowsing
185.228.168.9
64 ms
- do1ckqc2wqktx.cloudfront.net.
- 18.245.31.54
- 18.245.31.92
- 18.245.31.118
- 18.245.31.6
Control D
76.76.2.0
64 ms
- do1ckqc2wqktx.cloudfront.net.
- 3.173.161.122
- 3.173.161.93
- 3.173.161.105
- 3.173.161.92
AdGuard
94.140.14.14
276 ms
- do1ckqc2wqktx.cloudfront.net.
- 3.162.247.96
- 3.162.247.50
- 3.162.247.4
- 3.162.247.12
Mullvad
194.242.2.2
32 ms
No records returned.
Distinct answer sets
1
do1ckqc2wqktx.cloudfront.net.,18.245.31.92,18.245.31.6,18.245.31.54,18.245.31.118
2
do1ckqc2wqktx.cloudfront.net.,18.245.31.118,18.245.31.6,18.245.31.54,18.245.31.92
3
do1ckqc2wqktx.cloudfront.net.,13.225.239.2,13.225.239.20,13.225.239.114,13.225.239.126
4
do1ckqc2wqktx.cloudfront.net.,13.225.239.2,13.225.239.20,13.225.239.126,13.225.239.114
5
do1ckqc2wqktx.cloudfront.net.,3.173.161.122,3.173.161.93,3.173.161.92,3.173.161.105
6
do1ckqc2wqktx.cloudfront.net.,13.225.239.20,13.225.239.114,13.225.239.126,13.225.239.2
7
do1ckqc2wqktx.cloudfront.net.,13.225.239.126,13.225.239.2,13.225.239.20,13.225.239.114
8
do1ckqc2wqktx.cloudfront.net.,13.32.220.20,13.32.220.6,13.32.220.100,13.32.220.114
9
do1ckqc2wqktx.cloudfront.net.,18.245.31.6,18.245.31.118,18.245.31.92,18.245.31.54
10
do1ckqc2wqktx.cloudfront.net.,3.173.161.105,3.173.161.92,3.173.161.122,3.173.161.93
11
do1ckqc2wqktx.cloudfront.net.,3.164.230.70,3.164.230.63,3.164.230.115,3.164.230.30
12
do1ckqc2wqktx.cloudfront.net.,18.245.31.54,18.245.31.92,18.245.31.118,18.245.31.6
13
do1ckqc2wqktx.cloudfront.net.,3.173.161.122,3.173.161.93,3.173.161.105,3.173.161.92
14
do1ckqc2wqktx.cloudfront.net.,3.162.247.96,3.162.247.50,3.162.247.4,3.162.247.12
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=auth.liberia.healthcare.sandtech.app
curl -s '/api/v1/dns/propagation?q=auth.liberia.healthcare.sandtech.app'
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