How to use it 01 Type a domain and choose a record type. 02 Pick Cloudflare or Google, or switch on compare to query both providers in parallel. 03 Press Query; each provider panel reports its own response time and status. 04 Read the answer rows — name, type, TTL and data — and the DNSSEC badge.
Worked readouts The panel renders the numeric type and status codes as names, so a reading is a set of labels rather than raw protocol numbers. Its mapping includes A = 1 , NS = 2 , CNAME = 5 , SOA = 6 , MX = 15 , TXT = 16 , AAAA = 28 and CAA = 257 ; anything outside the table prints as TYPE<n>. Status 0 is NOERROR, 3 is NXDOMAIN ("this name does not exist"), 2 is SERVFAIL and 5 is REFUSED. A TTL is the cache lifetime in seconds: 300 means five minutes, 3600 an hour, 86400 a day. The panel builds its queries as https://cloudflare-dns.com/dns-query?name=example.com&type=A for Cloudflare and https://dns.google/resolve?name=example.com&type=MX for Google — the two DoH JSON endpoints behind the provider buttons.
What a lookup really answers DNS is a distributed tree: a root server delegates to a top-level domain, which delegates to the zone that owns the name, and a recursive resolver walks that chain and caches each answer for its TTL. The panel asks a public recursive resolver over DNS-over-HTTPS, which wraps the DNS query in an HTTPS POST/GET and returns JSON, so the reply you see is that resolver's cached view at that moment. Record types answer different questions: A and AAAA map a name to an IPv4 or IPv6 address, CNAME points one name at another, MX names mail servers (with a preference number), TXT carries arbitrary text such as SPF and domain-verification strings, NS lists the zone's name servers, SOA describes the zone's authority, and CAA restricts which certificate authorities may issue certificates. When the resolver sets the AD (authenticated data) flag, the answer chain was DNSSEC-validated.
Limits and honest assumptions
Two resolvers, not the world. Compare mode shows Cloudflare and Google; a negative answer from both is strong evidence but not proof, and caches with long TTLs can serve stale data after a change.
"DNSSEC: not validated" is not "unsigned". The badge reports the AD bit of this answer; a resolver that does not validate, or a chain that is signed but not validated for this query, both show as not validated.
Answers belong to the moment. Response times and TTLs are live network observations; the same query a minute later can read differently.
Network required , and the query goes directly from your browser to the provider — there is no server in between. What it does not do. It does not check propagation worldwide, transfer zones or capture packets; Subnet is for address arithmetic, not DNS.
NXDOMAIN and NODATA look similar, and are not A wrong record type on a name that exists returns NOERROR with an empty answer list — "no records" — while a name that does not exist returns status 3, NXDOMAIN. The first means the name is fine but this type is not published; the second means the name itself is absent, so other types will fail too. The second trap is the cache: a TTL of 86400 means an old address can survive a migration for a day even though every authoritative server already has the new one. If a change "hasn't propagated", check the TTL and query the authoritative NS directly before blaming the world.
Where it is used Verifying a record after a change Query the type you changed, confirm NOERROR and the expected data, then confirm the TTL so you know how long the old value can survive in caches.
Checking mail and security configuration MX rows show where mail is routed; TXT rows expose SPF, DKIM and verification records; CAA rows show which certificate authorities are authorised to issue.
Comparing resolvers Run the same name against Cloudflare and Google and compare answers and response times — a difference is usually caching or anycast geography, and it is worth understanding before you open a support ticket.
Privacy Queries go directly from your browser to the selected provider over HTTPS; the domain you type is visible to that provider and to nothing else in this page.
References
IETF, RFC 1035: Domain Names — Implementation and Specification , rfc-editor.org (访问日期:2026-10-07)— record types, TTLs and the protocol the codes come from.
IETF, RFC 8484: DNS Queries over HTTPS (DoH) , rfc-editor.org (访问日期:2026-10-07)— the HTTPS transport the panel uses.
IETF, RFC 4035: Protocol Modifications for the DNS Security Extensions , rfc-editor.org (访问日期:2026-10-07)— the AD bit and DNSSEC validation semantics.
Wikipedia, Domain Name System , en.wikipedia.org (访问日期:2026-10-07)— hierarchy, recursion, caching and record roles.
Calculators in this hub
Hand-picked tools, one click away. The mini versions compute live and carry your values into the full calculator.
Sources & review
Reviewed by CalcX Editorial Team
Updated 2026-10-07