About DNS over HTTPS Lookup
Takes a single domain name and performs a DNS lookup using DNS over HTTPS. By default, Cloudflare and Google DNS over HTTPS services are supported. Can be used with any service that supports the GET parameters name and type.
Input: text. Output: structured JSON.
Format reference: DNS over HTTPS background and specification
Example
Use “Try example” to load this public sample and its settings, then run it.
Settings used in this example
| Parameter | Example value | Input and choices |
|---|---|---|
| Resolver | "https://cloudflare-dns.com/dns-query" | Google, Cloudflare. Escape sequences such as \n, \r and \t are supported |
| Request Type | A | A, AAAA, ANAME, CERT, CNAME, DNSKEY, HTTPS, IPSECKEY, LOC, MX, NS, OPENPGPKEY, PTR, RRSIG, SIG, SOA, SPF, SRV, SSHFP, TA, TXT, URI, ANY |
| Answer Data Only | true | On or off |
| Disable DNSSEC validation | false | On or off |
Input
example.com
Result
This example sends a DNS query to the selected resolver. Network access is required and answers can change.
The resolver receives your query
Running this tool sends the requested name to the selected DNS resolver. Results reflect that resolver’s view and cache at the time of the request.
Parameters
| Parameter | Default value | Input and choices |
|---|---|---|
| Resolver | "https://dns.google.com/resolve" | Google, Cloudflare. Escape sequences such as \n, \r and \t are supported |
| Request Type | A | A, AAAA, ANAME, CERT, CNAME, DNSKEY, HTTPS, IPSECKEY, LOC, MX, NS, OPENPGPKEY, PTR, RRSIG, SIG, SOA, SPF, SRV, SSHFP, TA, TXT, URI, ANY |
| Answer Data Only | false | On or off |
| Disable DNSSEC validation | false | On or off |
Before interpreting the result
Protocol parsers need the correct byte representation and framing. HTTP Request and DNS over HTTPS contact remote services only when you run them; browser network and CORS restrictions still apply.
How to use this page
- Paste your input or open a local file.
- Adjust tool options if needed, then choose Run tool.
- Copy the result or download the original output bytes.
Inputs and results are not added to the public catalogue or saved in the URL. Processing happens in your browser; HTTP Request and DNS over HTTPS send the requests you explicitly run. Files up to 128 MiB can be opened; decompression and image tools may have smaller processing limits. Large results have a shortened preview. Text and HTML downloads use UTF-8; binary downloads preserve output bytes. Pasted text follows browser newline handling; open a file when exact input bytes matter.