Queries go straight to a public DNS-over-HTTPS resolver — Cloudflare, falling back to Google. Both are free and need no API key or account. The name you type is the only thing sent.
Learn
History for this tool
The most recent data you entered in this tool, stored only in this browser.
Save what you type here, in this browser? Your work would go into this browser's local storage, so a refresh or a trip to another tool does not wipe it. You also get a short list of previous entries under the form, each one restorable with a click. Nothing is ever uploaded, and there is no account.
Being straight about the trade-off: anything kept there can be read by anyone who can use this browser profile, and by any script that later runs on this site. A tool page can hold a private key, a password or a signed token. Saving is convenient; it is not private.
About this tool
Resolve A, AAAA, CNAME, MX, TXT, NS, SOA, CAA and SRV records over DNS-over-HTTPS, so the query travels over an encrypted connection instead of plain UDP on port 53. It asks Cloudflare first, falls back to Google, and reports which resolver answered.Questions
- Why is there no ANY query?
- Both Cloudflare and Google refuse ANY over DoH and return NOTIMP. Querying each record type individually is what the resolvers actually support.
- Is this the same as dig?
- They can ask for the same records, but this page uses HTTPS to a public resolver, while
dignormally uses the DNS resolver configured for your device. The route, cache, and answer may differ. HTTPS protects the connection to the selected resolver; it does not prove the DNS record itself is correct. - Why do I get a different answer than my own resolver?
- You are asking a public resolver with its own cache. A different answer usually means a different cache state, or a CDN handing back the node nearest to the resolver rather than to you.