Vantage points

Compare browser and server requests

Query the same public DoH resolver from your browser and Cloudflare’s edge, then compare the answers side by side.

When to use it

Use this when

  • You want to check that a public DoH resolver is reachable from your device.
  • You want to compare the public resolver’s answers to requests from your browser and Cloudflare’s edge.

Steps

Do this

  1. Choose a request originUse the Run from selector under the result area: Server queries the selected public resolver from Cloudflare’s edge, Your browser sends a direct DoH request from your device, Hybrid uses the browser when available, and Both runs the pair.
  2. Compare both columnsBoth mode renders browser and server results with an agree/differ banner for the selected public resolver.
  3. Check browser reachabilityA successful browser result confirms that your device reached the selected DoH endpoint and received an answer.

Examples

Copyable commands

Deep link — both
https://dnsbin.ca/?tab=lookup&name=example.com&type=A&mode=both
Deep link — client only
https://dnsbin.ca/?tab=lookup&name=example.com&type=A&mode=client

Operational notes

Keep in mind

  • Browser-direct requests support Cloudflare, Google, and DNS.SB. For other resolvers, Client mode asks you to switch resolver or mode, while Both runs server-only. For a single Lookup, Hybrid falls back to the server when browser requests are unavailable or fail.
  • These modes query public DoH resolvers. They do not query your device’s configured DNS server or private split-horizon DNS.
  • Composite tools (DNSSEC, Mail health, Discovery, Trace, Blocklist) always run server-side; mode applies to record lookups.
  • REST endpoints always execute on the server — client-side resolution is a browser feature of the web app.