DNS Lookup
Resolve A, AAAA, CNAME, MX, TXT, NS and SOA records for a domain through a public DNS-over-HTTPS resolver, and read the TTL it returned.
What this DNS lookup does
It asks one public DNS-over-HTTPS resolver what records a domain publishes and reports exactly what that resolver answered. Enter a domain name, choose a record type, and read the records it returned.
The answer is one resolver's answer
The result is what the resolver this tool uses — Cloudflare's public resolver at cloudflare-dns.com — returned at the moment you ran it. A resolver in another network, or your own ISP's resolver, may hold a different cached copy and can answer differently. That is a property of DNS caching, not a fault in either answer. This page reports one resolver's reply; it does not compare several and it does not claim they agree.
The record types
A is an IPv4 address, AAAA an IPv6 address, CNAME an alias, MX a mail exchanger and its priority, TXT free text (including the _dmarc and _acme-challenge names), NS the delegated nameservers, and SOA the zone's authority record — primary server, contact, serial and timers. Those seven are the whole set: ask for any other type and the tool names the supported ones instead of forwarding the request.
Reading the answer
Every record carries the value the resolver returned and the TTL it returned with it. A caching resolver may serve a cached copy, so that TTL can be lower than the TTL the zone itself publishes — it is the time left on the answer you were given, not the zone's configured value.
NXDOMAIN means the resolver reports that the name does not exist. NODATA is a different answer: the name exists, but it publishes no records of the type you asked for, and the report says so in words rather than showing an unexplained empty list. A timeout, a SERVFAIL, a REFUSED, an HTTP failure or an oversized answer is reported as the failure it is, never as an empty success.
Privacy and safety
The lookup runs on the tool server, so the domain you enter is sent to the public resolver for this request, and nothing else is. There is no API key, no account and no per-query quota. The resolver endpoint is a constant in the tool's source, so your input cannot aim the request at another host; redirects are not followed, the request is bounded in time and bytes, and no response body is written to disk or logged.
Enter a domain and a record type and this page asks a public DNS-over-HTTPS resolver — Cloudflare's, at `cloudflare-dns.com` — for that name, then lists the records it returned with the TTL attached to each.
The seven record types it will ask for are A, AAAA, CNAME, MX, TXT, NS and SOA. Anything else is refused before a request is made, and the domain is validated and passed as a query parameter, never as part of a URL.
The empty answer is distinguished from a missing domain: NODATA means the name exists but publishes no record of that type, while NXDOMAIN means the resolver says the name does not exist at all.
What the answer reports
Each record carries its name, its type, the TTL the resolver returned and the record data. A TXT record's quotes and an MX record's preference number are reported as the resolver wrote them.
The payload also reports whether the resolver set the authenticated-data flag. That flag is the resolver's own claim about DNSSEC validation, not a validation this tool performed.
A truncated answer is flagged rather than silently cut, and an oversized response above 64 KB is refused with its own message.
- Types: A, AAAA, CNAME, MX, TXT, NS, SOA
- Per-record TTL, as returned
- NODATA, NXDOMAIN, SERVFAIL and REFUSED each reported separately
Why two tools can disagree
A TTL is the value the resolver returned, and a caching resolver may be serving a copy, so it can be lower than what the zone publishes. Two lookups minutes apart can report different TTLs.
If a resolver times out or references a different nameserver set, the answer is a failure with a reason rather than an invented record. Nothing here guesses at a value.
How to use the domain and type fields
Enter the domain and pick one of the seven record types, A, AAAA, CNAME, MX, TXT, NS or SOA, then run the tool. Anything else is refused before a request is made, and the name travels as a query parameter.
Read each record with its name, type, data and TTL, plus the resolver's authenticated-data flag as its own claim. NODATA means the name exists without that type; NXDOMAIN means the name does not exist.
What to Expect
Best for
- Checking which address a name currently resolves to
- Reading the MX or TXT records for a domain before a mail migration
- Confirming that a DNS change has propagated to a public resolver
Not ideal for
- A domain whose records are only visible on an internal resolver
- Querying a record type outside the seven, such as CAA or SRV
- Proving a record does not exist anywhere, since one resolver is one view
What this tool keeps
- The TTL the resolver returned, per record
- The typed domain alongside the normalised name that was queried
- A distinct reason for NODATA, NXDOMAIN, SERVFAIL and REFUSED
What may need cleanup
- A TTL read from cache rather than from the zone
- A TXT record's quoted string, which may need the quotes removed for use
- An NODATA answer, which means the type is absent rather than the domain
Common errors
- Reading NODATA as a claim that the domain does not exist
- Expecting an internal or split-horizon record to appear
- Querying a CAA or SRV record and reading the refusal as a resolver fault
Example use cases
- Checking the MX records before switching mail providers
- Confirming an A record change after an edit
- Reading the TXT record for a domain verification
Sample input
Ask for the MX records of example.com.
Sample output
A list of MX hosts with their preference numbers and the TTL the resolver returned for each.
Who this is for
- Developers checking a DNS change
- System administrators preparing a mail migration
- Anyone who needs to read a TXT or MX record from outside the network
Frequently asked questions
Which resolver does the DNS lookup use?
Cloudflare's public DNS-over-HTTPS resolver at cloudflare-dns.com, so the answer is one resolver's view of the name.
Can it prove a record does not exist anywhere?
No. One resolver is one view, and a record visible only on an internal resolver will not appear.
What does an NODATA answer mean?
The name exists but the requested record type does not; NXDOMAIN means the name itself was not found.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.