Skip to content
Mail TesterMail DoctorIMAP MigrationList VerificationArchive RecoveryMonitoring
What is my IP addressDNS Propagation CheckerTCP Port CheckerMTA-STS and TLS-RPT CheckerDNSSEC checkSecurity Headers CheckerSPF, DKIM and DMARC CheckerWHOIS and Domain LookupEmail Header AnalyzerSSL Certificate CheckDNS and MX LookupBlacklist CheckIs It DownSpeed testPassword generator

DNS Propagation Checker

Type a domain. We ask each of its own nameservers separately, and five public resolvers, and tell you which of the two things you are looking at: caches still holding the old answer, or your nameservers disagreeing with each other.

DNS does not propagate

Nothing is pushed anywhere. Each resolver keeps the answer it was given until the TTL on it runs out, then asks again. So “how long until it propagates” does have an answer, and it is the TTL of the OLD record — the one you can no longer see, because you changed it. If you are about to move something, drop that TTL to a few minutes a day before, not after.

What this does not tell you

What every resolver on earth sees. Five public caches and your own nameservers are a good sample and not a census: a corporate resolver, your router, or the one your ISP runs may still be holding something older. And a browser or an operating system keeps its own cache on top of that, which is why a page can stay wrong on one machine after everything here is green.

If you are here, this is usually what comes next

A photo now, or a warning later

This is where things stand this minute. Monitoring watches your DNS and tells you the day a record changes — which, when you did not change it, is the day worth hearing about.

See monitoring →

Frequently asked questions

How long does a DNS change take?
As long as the TTL that was on the old record, counted from the last time each resolver asked. Nothing is being sent anywhere: a cache simply holds what it was given until that timer runs out. A TTL of an hour means an hour; a TTL of a day means a day, and there is no way to make a cache forget early. The lesson is for next time — lower the TTL a day before you move something, then raise it again once it has settled.
Two of my nameservers give different answers. Is that propagation?
No, and that is the difference this page exists to show. Caches disagreeing with your zone is propagation and it ends by itself. Your own nameservers disagreeing with each other is a broken zone: a transfer that did not run, or an edit made in one place and not the others. It will not settle, and until it is fixed, what a visitor gets depends on which of your servers they happen to reach.
It says everything matches but my site still shows the old page.
Then the DNS is probably not your problem any more. What is left above the DNS is your own machine: the operating system caches lookups, and so does the browser, both for minutes at a time. Below it, a CDN or a proxy in front of your site has its own cache that has nothing to do with the DNS at all — and that one you have to clear yourself.