DNS Lookup
Look up A, MX, TXT, CAA, NS, SOA, SRV and PTR records from your browser over DNS-over-HTTPS. Pick Cloudflare or Google, see the DNSSEC flag and the raw JSON.
- Lookups send the domain name to the DNS resolver you pick (Cloudflare or Google)
- Free · No Sign-Up
Scan with WeChat to share this tool
Examples, details and FAQ Worked examples, how it compares with other tools, and answers to common questions.
Three Real Lookups
These ran on 2026-09-29; the AD flag and dnssec-failed.org results were checked again on 2026-09-30. Run them again and the TTLs will differ; the rest should match until the owners change their DNS.
Our own mail setup. zerotool.dev with type MX returns three Cloudflare Email Routing servers: 13 route1.mx.cloudflare.net., 20 route2.mx.cloudflare.net. and 63 route3.mx.cloudflare.net.. TXT returns the SPF policy v=spf1 include:_spf.mx.cloudflare.net ~all and a Google site verification token. TXT on _dmarc.zerotool.dev returns NXDOMAIN: we have not published a DMARC policy (RFC 7489 §6.1 puts it at that name). The DKIM key at cf2024-1._domainkey.zerotool.dev is 420 characters long, so it is stored as two strings, one of exactly 255 characters (RFC 1035 §3.3 limits each string to 255).
DNSSEC, signed and unsigned. example.com type A returns two addresses and the pill DNSSEC ✓. zerotool.dev returns two addresses and no DNSSEC, because the zone is not signed. The tool sends do=1 with every query. Without it, Cloudflare's AD flag varies. On 2026-09-30 we sent each query 30 times without do=1: example.com A, AAAA and NS came back "AD": false every time, and MX came back true every time. An earlier run of 20 example.com A queries gave 10 true and 10 false. With do=1, and from Google either way, every answer had true. RFC 6840 §5.8 says a resolver should set AD only when the query sets the DO or AD bit, so send do=1 whenever you need a reliable answer. With do=1 the answer also carries RRSIG signatures; the Records view hides them and Raw and JSON show them.
A broken zone. dnssec-failed.org is the failure example in Google's JSON API documentation. Both resolvers return SERVFAIL, and the DNSSEC pill reads DNSSEC failed. Under the records, Cloudflare's note reads EDE(9): DNSKEY Missing no SEP matching the DS found for dnssec-failed.org.. Google sends a sentence with links to DNSViz and Verisign's DNSSEC Debugger, plus a structured extended_dns_errors entry with code 9, which the tool shows as EDE(9): No DNSKEY matches DS RRs of dnssec-failed.org. Code 9 is "DNSKEY Missing" in RFC 8914 §4.10.
Cloudflare or Google: Why Answers Differ
Both resolvers serve the same JSON format over HTTPS (Cloudflare, Google). The JSON profile is not an RFC; the binary DNS-over-HTTPS format is RFC 8484. Comparing them with the dropdown shows three differences:
- Location. Google can send part of your IP address to authoritative servers (EDNS Client Subnet); Cloudflare generally does not forward ECS to external authoritative servers. A CDN can therefore give each resolver a different address, and Google's answer depends on where the query comes from. Google's JSON API lets you set that subnet with the
edns_client_subnetparameter (this page does not send it). On 2026-09-30,www.qq.comreturned121.14.77.201and121.14.77.221for114.114.114.0/24,43.159.109.55for8.8.8.0/24, and43.168.224.173for139.130.4.0/24. Cloudflare ignored the same parameter and returned43.159.109.55. - TXT format. In the 2026-09-30 tests, Cloudflare quoted separate strings while Google returned one unquoted string. This is a dated observation, not an API guarantee: Google's JSON documentation also contains quoted, segmented TXT examples.
- Notes. On an answered query that was not cached, Google adds
Response from <IP>, naming the authoritative server it asked. When validation fails, Google sends a sentence of explanation and anextended_dns_errorsfield instead, and Cloudflare lists Extended DNS Errors inComment. The tool shows all of these as resolver notes and writes Google's errors in Cloudflare'sEDE(n): textform.
How It Compares with dig and Web Lookup Sites
dig and nslookup ask the resolver your computer uses. When a VPN or proxy app answers port 53 itself, they show that app's answer: on a test machine running a proxy in fake-IP mode, dig @1.1.1.1 dnssec-failed.org printed NOERROR with 198.18.2.147. That address comes from 198.18.0.0/15, a block reserved for benchmark tests (RFC 6890) that proxies such as mihomo use as their default fake-IP range. This page uses HTTPS to reach the resolver, so it showed the real SERVFAIL. On a server, in scripts, or when you must ask one authoritative server (dig @ns1.example.com), use dig.
Google Admin Toolbox Dig sends your query to its own backend (/apps/dig/lookup). For dnssec-failed.org its main view says "Record not found!", and only the raw view shows rcode SERVFAIL. Its flags line for example.com reads QR RD RA, with no AD flag. DNS Checker queries "a selected list of DNS servers in multiple regions worldwide" from its servers, which is what you want for propagation checks.
This page is for the question in between: what does a major public resolver answer right now, is it DNSSEC-validated, and what exactly did it send back. To check what a web server returns once the name resolves, use the HTTP Header Analyzer; to read the certificate it serves, use the SSL Certificate Decoder.
Limits
- Two resolvers. Only Cloudflare and Google. You cannot enter your own DoH endpoint or an authoritative server.
- One vantage point per resolver. There is no propagation map; for that, use a multi-region checker.
- Time limit. Each query is cancelled after 5 seconds. If a resolver is blocked on your network, the page shows a network error; switch to the other resolver.
- Types. ALL covers eight types. PTR and SRV need their own queries, and PTR needs the
in-addr.arpaname typed in. Types outside the dropdown (DS, DNSKEY, HTTPS, TLSA) cannot be queried, though RRSIG and NSEC lines appear in Raw when the resolver sends them. - Input. At least two labels; letters, digits, hyphens and underscores, up to 63 characters per label and 253 in total; a label cannot start or end with a hyphen.
localhostor a barecomare rejected. The error names the reason:exa mple.comgives" " (U+0020) at character 4 is not allowed in a domain, and-foo.comgivesLabel 1 "-foo" starts with a hyphen. A host ending in a number, such ashttps://example.123/, is read as an IPv4 address and rejected with that reason; a port above 65535 or adns://prefix gets its own message too.
FAQ
Does ZeroTool see the domains I look up?
The browser sends the domain and record type directly to the selected cloudflare-dns.com or dns.google resolver, which receives your IP address and query. ZeroTool does not proxy the query, and the tool does not save queried domains in browser storage. Clear or Ctrl/⌘+L clears the domain and result. This page loads Google Analytics and AdSense. The tool's custom event parameters contain only the tool name and action; Google Analytics also collects standard page and device information. The actions are: lookup when a current DNS response is displayed (including DNS error responses), and copy_json after the current response is successfully copied. Network failures, failed copies and stale completions record no outcome event; events contain no query or response content.
Why does a signed domain show "no DNSSEC"?
The pill shows the AD (Authenticated Data) flag of the response. It is set only when every record in the answer was validated. A CNAME that leads into an unsigned zone clears it, even when the first name is signed. If validation fails outright, the resolver returns SERVFAIL instead of an answer. When that SERVFAIL carries a DNSSEC Extended DNS Error (codes 1, 2 and 5 to 12 in RFC 8914), the pill reads "DNSSEC failed" and the resolver note under the records says why. For any other SERVFAIL the pill is hidden: the resolver sent no answer, so the flag says nothing about signing.
How do I look up SPF, DMARC, DKIM, SRV or reverse (PTR) records?
Type the full owner name and pick the type. SPF is a TXT record on the domain itself, DMARC lives at _dmarc.example.com (TXT), a DKIM key at selector._domainkey.example.com (TXT; the selector is the s= value in the DKIM-Signature header of a message you received), and SRV records at names such as _xmpp-server._tcp.jabber.org. Names with underscores are accepted. For a reverse lookup, reverse the IPv4 address, add .in-addr.arpa and pick PTR: for 1.1.1.1 enter 1.1.1.1.in-addr.arpa, and Cloudflare answers one.one.one.one. The tool does not build that name from an IP address for you.
Why do results differ from dig, nslookup or the other resolver?
By default, dig and nslookup query your configured DNS server; you can also specify another server. They do not normally read your hosts file. A company VPN's DNS or a proxy app intercepting port 53 can change their answer. This page asks Cloudflare or Google over HTTPS, so it cannot see private DNS records or hosts-file overrides. Between the two resolvers, a CDN can return different addresses, because Google can pass part of your IP address to authoritative servers (EDNS Client Subnet) while Cloudflare generally does not forward ECS to external authoritative servers. TXT values also look different: each string inside a TXT record holds at most 255 bytes, so a long DKIM key is stored as two or more strings. In the dated tests below, Cloudflare returned quoted strings separated by a space, while Google joined them into one unquoted string.
Can I look up an internationalized domain name?
Yes. Type it as it is, for example bücher.example: the browser's URL parser converts it to Punycode (xn--bcher-kva.example) before the query. Full-width letters and digits and the ideographic full stop (。) are changed to ASCII too.
What if a resolver keeps failing with a network error?
Each query is cancelled after 5 seconds, with the message Request timed out after 5s. If your network blocks dns.google or cloudflare-dns.com, the page shows a network error; switch to the other resolver. If neither can be reached, the page cannot work on that network, so run dig on your own machine.