DNS-over-HTTPS (DoH) Lookup
Look up A, AAAA, MX, and TXT records for any domain over an encrypted DNS-over-HTTPS query.
Requires an internet connection — this lookup runs against a public DNS-over-HTTPS resolver, not a local database.
Related tools
About this tool
DNS-over-HTTPS (DoH) wraps an ordinary DNS query inside an encrypted HTTPS request instead of sending it as plain text over UDP port 53, which is how DNS has traditionally worked. That matters because plain DNS queries are trivially visible to anyone on the network path — an ISP, a public Wi-Fi operator, or anyone else sniffing traffic — while a DoH query looks like any other HTTPS request and its contents are encrypted end to end. This tool performs exactly that kind of query, letting you look up records for any domain the same way a DoH-enabled browser or operating system resolver would.
A single lookup fetches four record types at once: A records (the IPv4 addresses a domain resolves to), AAAA records (the IPv6 equivalent), MX records (which mail servers are responsible for accepting email for the domain, in priority order), and TXT records (arbitrary text data commonly used for domain verification, SPF/DKIM/DMARC email authentication policies, and other machine-readable metadata). Each record comes back with its TTL (time-to-live), which tells you how long a resolver is allowed to cache that answer before it has to ask again.
The query itself is sent to a public DoH resolver over HTTPS and returned as structured JSON, which this tool parses and displays per record type. Because DNS resolution fundamentally requires reaching a server outside your machine — there's no way to look up who owns a domain without asking someone who knows — this is one of the few tools in this toolbox that needs an active internet connection to function; everything else in the toolbox works entirely offline.
This gets used for a lot of everyday troubleshooting: confirming a domain's A/AAAA records point where you expect after a DNS change, checking whether MX records are configured correctly before trusting a domain to receive mail, or reading a TXT record to verify SPF, DKIM, or a domain-ownership token without needing a terminal or a dig/nslookup installation. Because it's a plain web page, it works the same way on a phone, a locked-down work laptop, or any machine where installing a command-line DNS tool isn't an option.
Keep in mind that TTL values and propagation mean a fresh DNS change may not show up immediately everywhere — a public resolver may still be serving a cached answer until its TTL expires, even though the authoritative nameserver already has the new record.
Frequently asked questions
What is DNS-over-HTTPS? expand_more
It's a way of sending a DNS query wrapped inside an encrypted HTTPS request instead of unencrypted UDP, so the query and its answer aren't visible in plain text to anyone monitoring the network in between.
Which record types does this tool look up? expand_more
A (IPv4 address), AAAA (IPv6 address), MX (mail server), and TXT (arbitrary text, often used for SPF/DKIM/DMARC and domain verification) — all four are fetched in a single lookup.
Why does this tool need an internet connection when the rest of the toolbox works offline? expand_more
DNS resolution inherently requires asking an external server who owns a domain — there's no local database that could answer that question — so this is the one tool here that can't run without live network access.
Why don't I see a change I just made to my DNS records? expand_more
DNS answers are cached according to each record's TTL (time-to-live). A resolver may keep serving the old answer until that TTL expires, even though the authoritative nameserver already has the updated record.
Is this the same as using dig or nslookup? expand_more
It looks up the same kinds of records, but over an encrypted DNS-over-HTTPS query to a public resolver rather than the plain UDP query dig or nslookup normally sends, and it needs no terminal or installed tools — just a browser.