DNS Propagation Check
Check a domain against selected DNS-over-HTTPS resolvers and compare returned A, AAAA, MX, CNAME, TXT, NS, or SOA records as results stream in one resolver at a time. The tool validates a hostname and record type, queries public resolvers server-side, and may fall back to local DNS resolution when remote checks fail.
DNS Propagation Check compares the DNS records returned for one hostname by a configured set of public DNS resolvers. Enter a domain, choose a record type, and the tool checks each resolver in sequence so you can see which services return records, which return no answer, and which fail during the request.
The check is useful after changing DNS records, moving hosting, adding mail records, switching nameservers, or troubleshooting why different users may see different answers. It is not an authoritative DNS audit. The page does not trace delegation, validate DNSSEC, compare SOA serials across nameservers, display TTL values, or prove that every location in the world has received the same answer.
How to use DNS Propagation Check
- Enter a domain name in the domain field. Use a hostname such as
digitaldomainkit.com, not a full URL withhttps://or a path. - Select the DNS record type you want to check. The available choices are A, AAAA, MX, CNAME, TXT, NS, and SOA.
- Start the check and wait while the page probes the configured DNS resolvers.
- Watch the table populate row by row. Results are streamed as the tool advances through the resolver list.
- Compare the records, warnings, and errors across resolvers before deciding whether the DNS change is still propagating or whether the domain configuration needs review.
The page resets earlier results each time you start a new check. A loading message indicates that the tool is probing global DNS resolvers and that values may stream in gradually. If the site's global settings enable reCAPTCHA, a challenge may appear before or during the form workflow.
Inputs and supported records
The input is intentionally strict. The submitted value is trimmed and then validated as a hostname with PHP domain validation. Empty values are rejected, and full URLs, spaces, paths, query strings, and invalid hostname characters should be removed before retrying. The selected record type must be one of the supported values shown in the dropdown.
| Input or setting | Accepted values | Notes |
|---|---|---|
| Domain | A required hostname, such as example.com or www.example.com |
The tool validates the trimmed host with FILTER_VALIDATE_DOMAIN and FILTER_FLAG_HOSTNAME. Do not include a protocol, port, path, or query string. |
| Record type | A, AAAA, MX, CNAME, TXT, NS, SOA |
The default record type is A. Other DNS record types are not available in this interface. |
| Output | Resolver name, resolver location, returned record values, and a status icon | Successful answers are shown as record data with trailing dots trimmed from displayed values. |
Resolvers checked
The current implementation checks a fixed resolver list. Most entries are queried through DNS-over-HTTPS JSON endpoints, while Google-style resolver endpoints use query parameters for the requested name and record type. Each server-side request uses a 15-second timeout.
| Resolver | Displayed location | Endpoint used by the tool |
|---|---|---|
| Google Public DNS | Global | https://dns.google/resolve |
| Cloudflare DNS | Global | https://cloudflare-dns.com/dns-query |
| NextDNS | Global | https://dns.nextdns.io/dns-query |
| Cloudflare Security | USA/Global | https://security.cloudflare-dns.com/dns-query |
| Cisco Umbrella | Global | https://doh.opendns.com/dns-query |
| Cloudflare Family | Global | https://family.cloudflare-dns.com/dns-query |
| Alibaba DNS | China | https://dns.alidns.com/resolve |
| DNSPod/Tencent | China/Asia | https://doh.pub/dns-query |
| DNS.SB | Germany/Europe | https://doh.dns.sb/dns-query |
Because these are public resolver services, their displayed locations are broad labels rather than a promise that the query originated from every city, ISP, or network in that region. A result can also be affected by resolver caching, resolver filtering policy, endpoint availability, upstream reachability, and the DNS response available at the time the request is made.
How to read the results
A successful row means the tool received a successful resolver response that included an Answer array for the requested record type, or that a fallback lookup found local records after a resolver exception. The records column lists the returned answer data after trimming trailing dots for cleaner display.
A warning with No records found means the resolver request completed but did not produce a displayed answer for that domain and record type. That can be normal. For example, many domains have an A record but no AAAA record, and a root domain may not have a CNAME record.
An error row means the resolver request did not produce a usable result. For the first resolver, a non-success response can fall back to the server's local dns_get_record result. On exceptions, every resolver row may attempt the same local fallback before showing an error. This means some successful-looking rows after failures may reflect DNS as seen by the Digital Domain Kit server rather than the named resolver endpoint.
Example check
A verified production connectivity check confirmed that the server can reach Google Public DNS at https://dns.google/resolve?name=digitaldomainkit.com&type=A. A typical A record check for digitaldomainkit.com asks each configured resolver for IPv4 address records and then displays any answer data returned by those resolvers.
If Google Public DNS and Cloudflare DNS return the same A value but another resolver reports No records found or a connection error, avoid assuming the domain is broken everywhere. Retry after a short wait, compare against the domain's authoritative DNS provider, and check whether the missing row is a resolver availability issue rather than a propagation issue.
Limitations and responsible use
DNS Propagation Check is a practical comparison tool, not a complete DNS diagnostic suite. It does not query every geographic region, every ISP resolver, or your own device's resolver. It does not access zone files, show TTL countdowns, verify DNSSEC signatures, follow the full delegation chain, compare authoritative nameserver SOA serial numbers, or prove that caches have expired worldwide.
Use the results as one signal among several. For high-stakes DNS changes, also check your DNS provider's zone editor, authoritative nameservers, application logs, CDN configuration, mail provider diagnostics, and local command-line tools such as dig or nslookup. When troubleshooting mail, remember that MX, TXT, SPF, DKIM, and DMARC behavior may involve separate hostnames and records.
Troubleshooting
| Problem | Likely cause | What to try |
|---|---|---|
| The domain is rejected | The value is empty or is not a valid hostname after trimming. | Remove https://, paths, spaces, ports, and query strings. Enter only the hostname. |
| A record type is not available | The interface only supports the configured record types. | Choose one of A, AAAA, MX, CNAME, TXT, NS, or SOA. |
Some resolvers show No records found |
The selected record may not exist, or the resolver may not currently have an answer to display. | Confirm the record exists at your DNS provider and test a record type that should definitely exist, such as NS for the root domain. |
| Rows show connection errors | A resolver endpoint may be unavailable, blocked, slow, or unreachable from the server. | Retry later and compare with other resolvers. Treat repeated endpoint failures separately from DNS propagation. |
| Results disagree after a DNS change | Resolver caches, TTLs, provider delays, or different upstream paths may still be in play. | Wait for the previous TTL window, verify the zone at the authoritative DNS provider, and recheck the exact hostname and record type. |
Related tools
Use DNS Lookup when you want a direct DNS record lookup from the site's server-side resolver rather than a resolver comparison. Use Domain WHOIS to review domain registration and nameserver information when ownership or registrar configuration may be part of the issue. Use HTTP Status Code Checker after DNS resolves to confirm that the target URL returns the expected web response.
Technical method and references
DNS Propagation Check is built and maintained by Digital Domain Kit. The verified implementation is a Laravel Livewire tool using public state for the entered query, selected record type, result list, error state, loading state, and current resolver index. The check resets previous results, validates the hostname and record type, sets the loading state, and then advances through resolvers one at a time using a browser event named next-check.
Google-style endpoints are called with name and type query parameters. DNS-over-HTTPS JSON endpoints are called with ct=application/dns-json and JSON content headers. Server-side HTTP requests use a 15-second timeout and are made without certificate verification in the current implementation. Technical behavior for this draft was reviewed against production implementation notes on September 14, 2026.
Primary references: RFC 8484 defines DNS Queries over HTTPS, and Google Public DNS JSON API documentation describes the JSON response style used by Google-compatible resolver endpoints. To report a problem with this tool page, use the site's contact page.