Query the same record on three independent public resolvers at once and see whether your change has propagated yet.
When you change a DNS record, whether it's a site's IP (A), a mail routing entry (MX) or an alias (CNAME), the change does not appear everywhere instantly. Every recursive resolver around the world keeps a cached copy of the old value until its TTL expires, and different internet providers use different resolvers. This tool queries the same domain and record type against three independent public resolvers, Cloudflare (1.1.1.1), Google Public DNS (8.8.8.8) and DNS.SB, at the same time, straight from your browser via DNS-over-HTTPS. If all three return the same value, propagation is complete on those providers. If they diverge, the change is still spreading across the internet.
Paste the code into your HTML and the tool shows up on your page, without J-Kit's navigation and ads. It still runs in the browser of whoever visits your site.
<iframe
src="https://jkit.tools/embed/en-US/dns-propagation-checker"
width="100%"
height="600"
style="border:0"
loading="lazy"
title="DNS Propagation Checker"
></iframe>These references help contextualize formulas, standards, APIs and limitations used on this page. They do not replace professional validation when a result has legal, financial, medical or operational impact.
It's the time a DNS record change takes to be reflected across every recursive resolver in the world. There is no mechanism to "push" the change, each resolver only fetches the new value after the old cached value's TTL expires.
The check queries 3 public resolvers (Cloudflare, Google Public DNS and DNS.SB) in parallel, straight from your browser, without touching our server. If all of them agree, propagation is complete.
For safety, the browser talks directly to fixed public resolvers, passing only the queried name, the J-Kit server is never used as an intermediary, avoiding IP exposure and SSRF. A DNS query is public by nature, like any name resolution.