b2KIT

DNS Propagation Checker

Check DNS propagation across global resolvers. See if your DNS changes have propagated to servers worldwide.

Tested tool guide Tested browser tools Checked August 16, 2026

What DNS Propagation Checker does and how it behaves

DNS Propagation Checker compares the DNS answers currently visible through resolvers in multiple parts of the world. Enter the name whose records changed, and the result shows where resolver answers agree or differ. The common surprise is that DNS changes are not pushed everywhere at once: a caching resolver can keep an earlier answer until its cached data expires. Matching results cover the resolvers sampled by the checker, not every cache or device on the Internet.

How the result is produced

1

Resolver comparison

The checker asks multiple geographically distributed resolvers for the same DNS name and places their current answers side by side. A resolver may return the new record data, an older cached value, or no usable answer. Comparing those rows reveals whether disagreement is isolated to particular sampled locations or shared across much of the displayed set.

2

Cache timing

Each displayed result is a point-in-time DNS observation. Recursive resolvers cache record sets according to TTL values, so they do not necessarily query an authoritative server for every check. The checker observes that state; it does not shorten a TTL, flush another operator's cache, or guarantee when every resolver will replace an earlier answer.

Good uses

  • Check whether sampled resolvers now return a new address after changing an A or AAAA record.
  • Compare regional DNS answers while investigating why some visitors still reach an earlier server or hostname target.
  • Observe whether a delegation or other DNS record change is appearing consistently through resolvers around the world.

Limits and checks

  • The displayed resolvers are only a sample. Agreement among them does not prove that every ISP, company network, router, or device cache has the same answer.
  • A returned value may have come from a resolver's cache. The result alone does not establish when that resolver last contacted an authoritative name server.
  • No usable answer is ambiguous. It can reflect a missing requested record, a DNS configuration problem, or a temporary lookup failure, so it is not by itself proof that the entire domain is unavailable.

Common questions

Why do some locations still show the previous DNS value?

Those resolvers may still hold a cached answer whose TTL has not expired. Different resolvers can have different cache ages because they did not all request the record at the same time. Rechecking can show the sampled answers changing, but the checker cannot force an external resolver to discard its cache.

Do matching results mean DNS propagation is complete?

No. They mean the resolvers shown by this check returned matching answers at that moment. Other recursive resolvers, local operating-system caches, browsers, routers, and applications may retain different data. Treat full agreement as useful evidence of broad consistency, not as proof that every possible DNS client has updated.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools