| # | Resolver | Answer | TTL | AD | Time (ms) | Copy |
|---|---|---|---|---|---|---|
| {{ i+1 }} | {{ row.resolver }} | {{ row.answer || '—' }} | {{ row.ttl !== null ? row.ttl : '—' }} | {{ row.ad === true ? '✔' : (row.ad === false ? '✖' : '—') }} | {{ row.ms !== null ? row.ms : '—' }} | |
| No data. | ||||||
Domain name records describe where a name points and how that name should be handled. Propagation is the pace and consistency with which updates appear across the world, and a global domain name propagation checker helps you see agreement at a glance.
The checker queries a range of public resolvers and condenses their answers into one percentage that is easy to read and compare. You can use that number to judge when a change is broadly visible so a cutover is less risky.
You provide a full domain such as example.com and choose a record type like A or MX. You may also enable integrity checking and an optional client subnet hint to compare how different networks would be steered.
For example you switch a mail record to a new provider and run a check after ten minutes. Most resolvers return the new target and the percentage climbs to 80 to 95 then you can schedule the switchover.
Propagation is not instant and cached answers can persist beyond expectations. Treat the percentage as a guide and verify with sample clients in the regions that matter most.
The Domain Name System (DNS) maps hostnames to resource records, which are the structured answers returned by resolvers. Each response also carries a time to live value indicating how long the answer may be reused without asking again.
The checker evaluates three outcomes from the selected resolvers: the majority answer string, the proportion that match that majority expressed as a percentage, and the per‑resolver response time measured in milliseconds. When the percentage is high, the chosen resolvers agree on one answer; when it is low, answers are mixed or failing.
Responses can include an authenticated data flag when integrity validation is active. If a client subnet hint is supplied, some resolvers may tailor answers to that network, which affects the distribution you observe.
Comparisons are limited to the resolvers you select. Each resolver reflects one of its global nodes, so results summarize those vantage points rather than every internet provider cache.
| Symbol | Meaning | Unit/Datatype | Source |
|---|---|---|---|
| p | Propagation percentage | percent | Derived |
| n | Resolvers matching the majority answer | count | Derived |
| N | Resolvers queried | count | Selection |
| Per‑resolver response time | ms | Derived | |
| TTL | Minimum time to live across returned records | seconds | Derived |
| AD | Authenticated Data flag from the resolver | boolean | Derived |
| rr | Record type | enumeration | Input |
| Field | Type | Min | Max | Step/Pattern | Error Text / Notes |
|---|---|---|---|---|---|
| Domain | FQDN | 2 labels | 253 chars | Each label 1 to 63, letters digits and dash, not starting or ending with dash | “Enter a valid domain (FQDN).” Trailing dot removed before query. |
| Record type | Enum | — | — | A, AAAA, CNAME, MX, NS, TXT, SOA, SRV, CAA | Used as the query type. |
| Timeout | Number | 500 | — | Step 100 ms | Per‑resolver cutoff in milliseconds. |
| Retries | Integer | 0 | — | Step 1 | Additional attempts per resolver. |
| Integrity flag | Boolean | — | — | Requests integrity records | Enables AD reporting when supported. |
| Checking disabled flag | Boolean | — | — | Ask resolver not to set AD | For comparative testing of validation paths. |
| Client subnet | Text (CIDR) | — | — | Example 0.0.0.0/0 or 2001:db8::/32 | Optional; string is passed as provided. |
| Input | Accepted Families | Output | Encoding/Precision | Rounding |
|---|---|---|---|---|
| Domain, record type, optional flags | Text domain; record type enum | Table of answers and timings; summary percent; charts | JSON copy and download, CSV copy and download | Percent rounded to nearest integer |
Requests run concurrently across resolvers. Work scales linearly with the number selected. Timeouts and limited retries cap worst‑case latency.
Given identical inputs and current resolver states, the checker yields the same aggregation. Network timing and upstream caches introduce normal variability.
Queries reveal the domain and type to public resolvers. Avoid entering sensitive internal names. Integrity flags expose whether validation was performed, but do not enforce it end‑to‑end.
Behavior aligns with IETF specifications for the Domain Name System, DNS integrity extensions, and client subnet signaling. Resolver policies vary by operator.
Requests are issued from the browser directly to chosen public resolvers over HTTPS. No data is transmitted or stored server‑side by this page.
Domain name propagation is summarized as a percentage of resolvers that agree on the same answer.
Pro tip: keep the resolver set constant across runs so percentages remain comparable.
No. Queries go from your browser to the resolvers you select, and the page does not keep records server‑side.
It reflects only the selected resolvers at the time of the check. It is a helpful proxy for readiness, not a guarantee of universal visibility.
Percent is an integer. Time is in milliseconds. TTL values are seconds. You can copy a CSV table and a JSON payload of inputs, stats, and results.
No. It needs network access to contact public resolvers and gather answers.
It indicates that a resolver reports an authenticated answer. If absent or disabled, the state is unknown for that resolver.
Some records legitimately have several values or vary by network. The checker normalizes and compares them to decide the majority string.
Clear the selection, pick the single resolver you want, then run the check to see its answer and timing alone.
Terms depend on how this page is distributed. Consult the surrounding site or package notes for licensing details.