DNS Lookup
Ask a public resolver what a domain actually points to. The records come back verbatim; the only thing timed is the HTTPS request that fetched them.
DNS lookup
Sends one query from your browser to Cloudflare 1.1.1.1 and shows what comes back. No account, no key, nothing stored.
Your query goes directly from this browser to Cloudflare 1.1.1.1 (cloudflare-dns.com). Cloudflare receives the domain you look up and your IP address, and handles them under its own privacy policy. This site never sees your query and stores nothing.
Enter a domain to look up its records. Nothing is sent until you press “Look up”.
What this tool does
You type a domain, choose a record type, and this page sends exactly one DNS query to Cloudflare's public resolver at 1.1.1.1, using DNS over HTTPS (DoH). Whatever comes back is displayed as it arrived.
- It is a lookup. It answers "what does this name point to?".
- A — the IPv4 addresses for the name.
- AAAA — the IPv6 addresses for the name.
- CNAME — the canonical name this name is an alias for.
- MX — the mail servers that accept email for the domain, with priorities.
- TXT — free-text records; commonly SPF, DKIM, domain verification and DMARC policy.
- NS — the authoritative nameservers for the zone.
- SOA — the zone's start-of-authority record, including its serial number.
- CAA — which certificate authorities are allowed to issue certificates for the domain.
The timing figure, precisely
The tool shows a query round-trip time: how long the HTTPS request from your browser to the resolver took to come back. It is measured directly with the browser's own high-resolution clock, and it is the only timing shown anywhere on this page.
It is not your DNS speed. Specifically, it does not tell you:
- how long your device takes to resolve names, because your device almost certainly asks a different resolver — your router, your ISP, or a local cache;
- how long an uncached lookup would take, since the resolver very likely had the answer cached already;
- anything comparable with
digor your router's reported DNS latency, because DoH adds an HTTPS exchange that plain DNS does not have.
Read it as "how far away and how busy was the resolver for this one request", not as a benchmark.
Who receives your query
The query is sent directly from your browser to Cloudflare at cloudflare-dns.com. It does not pass through this site's servers, and we do not operate a proxy for it.
That has two consequences worth stating plainly:
- Cloudflare sees it. It receives the domain you looked up and your IP address, and processes them under its own policy. Cloudflare publishes commitments for its public resolver, including truncating source IP addresses and deleting resolver logs within 25 hours. See the 1.1.1.1 privacy documentation for the current, authoritative version.
- We do not see it. Because the request goes browser-to-Cloudflare, this site never receives the domain you typed. There is no backend, no log, no counter and no analytics on this page — and your query is not stored anywhere in your browser either.
If you would rather not disclose a domain to a third-party resolver, do not use this tool for it. That is a real trade-off, not a disclaimer.
Reading the response
Every answer carries a TTL (time to live) in seconds — how long a resolver may keep the answer cached before asking again. A low TTL on a popular domain usually means you are seeing a cached copy close to expiry, not a slow resolver.
When a lookup returns nothing, the reason matters:
| What you see | What it means |
|---|---|
| NOERROR with records | The name exists and has records of the type you asked for. |
| NOERROR with no records | The name exists, but it has no records of that type. The domain is not broken — ask for a different type. |
| NXDOMAIN | The name does not exist at all. Check the spelling before concluding anything. |
| SERVFAIL | The resolver could not complete the lookup. Usually a resolver or upstream problem, not proof the domain is broken. |
| REFUSED | The resolver declined to answer. |
What it cannot tell you
- Whether your DNS is fast. A browser cannot time your operating system's resolver, so no part of this tool measures it. See the timing section above.
- Which resolver is quickest for you. Comparing resolvers here would mostly measure which one had the answer cached. That is why this version queries one resolver and offers no comparison.
- Whether your ISP is intercepting DNS. Not observable from a browser.
- Whether changing DNS will speed up your connection. It will not change your bandwidth. It can affect how quickly a first connection to a new name starts.
- Live propagation. A single public resolver's view is not every resolver's view, and caching means a recent change may not appear yet.