Encrypted resolver diagnostic
Inspect the answer and the resolver round trip.
Query real DNS data over HTTPS, review TTL and DNSSEC, and separate resolver behavior from a general bandwidth problem.
Live measurement
DNS Lookup & Latency Diagnostics
Do not enter an internal hostname. The query is sent to Cloudflare 1.1.1.1.
This test uses only small requests, but background tabs, extensions and battery saving can still affect timing.
Results will update live on this page.
This run
Network quality summary
Translate it into real tasks
These are transparent threshold-based guides, not service guarantees.
VPN deltas versus direct baseline
Method
Cloudflare 1.1.1.1 JSON DoH
The page sends three no-store HTTPS GET requests to the official cloudflare-dns.com/dns-query endpoint with DNSSEC requested. It displays the returned record data and TTL, response code, DNSSEC authenticated-data flag, median request time and timing spread.
A concrete example
What a fast empty answer means
A status 0 response with no AAAA answers can be a valid result: the name exists but publishes no IPv6 address. NXDOMAIN uses status 3 and means the queried name does not exist.
Limits and uncertainty
What these numbers can—and cannot—tell you.
- 01
This measures Cloudflare DoH from the browser, not the operating system resolver currently configured on the device.
- 02
Request time includes HTTPS connection setup or reuse, browser scheduling and resolver work; it is not pure DNS server processing time.
- 03
The queried domain is sent to Cloudflare 1.1.1.1. Do not enter a private internal hostname.
Anonymous feedback
Did this tool solve the job?
Found a problem or an idea to make this tool better? Tell us. We review every report and start working on actionable improvements within 2 days, continuously improving reliability and usability.