Check DNS record propagation across multiple global nameservers to verify DNS changes have taken effect.
A DNS propagation check compares the current answer for one hostname and record type across nameservers in different locations. It helps reveal whether resolvers are returning the new value, an older cached value, or no usable answer. The result is a snapshot of selected nameservers, not proof that every device worldwide sees the same record. The common surprise is that differing answers are not always stale: geographic routing, multiple valid records, and resolver-specific cache timing can also produce variation.
The checker requests the chosen record type for the same hostname from multiple nameserver locations and presents the observed answers separately. Comparing those rows shows whether the returned values agree. Record types must be interpreted independently: an A check examines IPv4 address records, while MX, TXT, CNAME, AAAA, and other checks concern their own DNS data.
DNS resolvers may retain a previously received answer for its remaining time to live, or TTL. Because caches were populated at different times, they can switch to a replacement record at different moments. A missing record can also be cached negatively. Repeated checks therefore show observations over time, but they do not force caches to refresh or accelerate a DNS change.
There is no single worldwide completion time. Visibility depends on the previous record's TTL, when each resolver cached it, whether negative answers were cached, and whether the authoritative configuration is correct. A lower new TTL does not shorten the lifetime of an older answer that resolvers already stored with a higher TTL.
No. It is strong evidence that the sampled nameservers currently agree, but it does not test every recursive resolver, browser, operating system, router, or private network. If one user still sees an old destination, compare the resolver they actually use and check for local application, operating-system, or network caches.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.