DNS Propagation Checker
Query the same DNS record from several public resolvers around the world to see whether a change has propagated everywhere.
A records for ailearnhub.net
Inconsistent8 of 8 resolvers answered.
Google 8.8.8.8
US / Global
104.21.30.172, 172.67.173.120
Cloudflare 1.1.1.1
Global (anycast)
104.21.30.172, 172.67.173.120
Quad9 9.9.9.9
Switzerland / Global
104.21.30.172, 172.67.173.120
OpenDNS 208.67.222.222
US
104.21.30.172, 172.67.173.120
AdGuard DNS 94.140.14.14
Cyprus / EU
104.21.30.172, 172.67.173.120
Level3 4.2.2.2
US
104.21.30.172, 172.67.173.120
DNS.WATCH 84.200.69.80
Germany / EU
188.114.96.3, 188.114.97.3
Yandex 77.88.8.8
Russia
104.21.30.172, 172.67.173.120
FAQ
Why do resolvers disagree?
After a DNS change, resolvers keep the old answer until the record's TTL expires, so some show old data.
How long is full propagation?
Usually minutes to a few hours, bounded by the record's TTL; NS/registrar changes can take longer.
Which resolvers are used?
Independent public resolvers such as Google, Cloudflare, Quad9, OpenDNS and others.
About propagation
We ask several independent public resolvers for the same record at once. If they all return the same answer, your change has propagated; if not, caches still hold the old value.
- Lower the TTL before planned DNS changes to speed up propagation.
- A/AAAA for hosting, MX for mail, NS for delegation.