DNS record online confirmation tool (DNS over HTTPS compatible) | ZeroTools

This tool provides a lookup interface for specifying a hostname and DNS record type to inspect the results returned by an external public DNS service.

The input fields consist of three items: hostname/domain name, record type, and DoH query server. You select one query destination from Cloudflare DNS or Google Public DNS.

This is not a feature for querying both providers simultaneously for comparison.

When you click "Resolve (Lookup)", the entered hostname and selected record type are sent to the JSON API of the selected DNS over HTTPS (DoH) service.

The page does not host an internal DNS server; instead, the browser formats and displays the responses returned by the external service.

Therefore, an active internet connection is required, and the tool cannot be used offline.

By default, the A record for google.com and Cloudflare DNS are selected. Each operation queries a single name and record type. There is no batch feature to query multiple domains or all record types at once, no input field for custom DNS servers, and no storage of past query results.

To make strings copied from browser address bars easier to use, if the input begins with http:// or https://, that prefix is stripped.

Everything after the first slash is then truncated. For example, https://example.com/path?id=1 is queried as example.com.

This is not complete URL parsing. There is no separate validation or correction for port numbers, user information, queries or fragments lacking slashes, or internationalized domain names.

To prevent querying unintended names, enter only the plain hostname such as example.com or www.example.com.

Selecting Cloudflare sends a GET request to cloudflare-dns.com, while selecting Google sends it to the JSON endpoint at dns.google.

The name is URL-encoded as a query parameter, and the Accept header requests application/dns-json. While DoH transmits the query from your browser to the selected provider over HTTPS, the queried hostname and record type are received by that provider.

The eight supported record types are A, AAAA, CNAME, MX, TXT, NS, CAA, and SRV. A resolves the IPv4 address corresponding to the hostname, and AAAA resolves the IPv6 address.

CNAME checks canonical name aliases. If another record type appears within the response chain, the contents returned in the external service's Answer array are displayed directly as rows.

MX checks mail exchange destinations and priorities, TXT inspects strings used for domain verification or email authentication, and NS checks authoritative nameservers for the namespace.

CAA covers certificate authority authorization rules, while SRV represents service priority, weight, port, and target hosts. Because the formatted Data column varies by record type, values cannot all be read uniformly as IP addresses.

This tool does not automatically evaluate whether record values comply with operational policies or whether SPF, DKIM, DMARC, or other configurations satisfy operational requirements.

Text strings such as TXT records must be verified manually against the specifications of your mail or authentication service.

Upon receiving a response, the tool displays the DNS response status with its description, the list of resolved Answer records, and the raw JSON payload.

Typical statuses include NOERROR (completed without error), NXDOMAIN (domain does not exist), SERVFAIL (server failure), FORMERR (format error), and REFUSED (query refused).

NOERROR does not guarantee that one or more records were found. A domain may exist while returning zero Answer records for the selected type.

In that case, the interface indicates that no answers were returned for the selected type. NXDOMAIN is distinct from a NOERROR response with zero Answer records.

The Answer table lists the hostname, type, TTL, and Data. The TTL indicates the remaining cache duration in seconds returned in the response, but this value alone cannot determine the exact moment global caches expire worldwide.

The raw JSON pane on the right displays the formatted external API response. Copying relies on the browser Clipboard API and depends on clipboard permissions and environment support.

Cloudflare DNS and Google Public DNS operate as independent recursive resolvers. Even when querying the same name and record type, responses may temporarily differ due to cache status, previous query timestamps, and routing paths.

Immediately after modifying DNS records, one provider may return the updated value while the other still serves cached data.

This tool sends a single query to the chosen provider and renders its response. It is not a global propagation checker that polls multiple geographic locations or resolvers.

Comparing both providers requires switching the selection and running the query separately.

If results differ from expectations, verify the queried name and type, authoritative DNS configurations, TTL values, and elapsed time since the change.

Results on this screen should not be treated as definitive proof of completed propagation, mail delivery success, certificate issuance feasibility, or root cause determination for outages.

DNS queries are sent directly from your browser to Cloudflare or Google. The entered hostname and record type are transmitted to the selected endpoint and are subject to external API availability, network restrictions, and browser policies.

Using HTTPS via DoH does not conceal query data from the chosen provider, nor does it guarantee the accuracy of returned answers.

The interface parses the Status and Answer arrays from the external API, mapping recognized type numbers to record names in the table.

While Question data is retained internally, it is not displayed in a dedicated table; raw API payloads can be reviewed in the raw JSON view.

The tool does not break out Authority or Additional sections into separate tables, measure response latency, compare history, or edit and transfer zone files.

There is no built-in DNSSEC signature validation, direct querying of authoritative nameservers, or recursive path tracing. While useful for quick lookups similar to an online nslookup, it does not replicate all command-line options of nslookup or dig.

Please use it for preliminary checks with full awareness of the communication scope and destinations.