DNS Lookup
Look up public DNS records using Cloudflare's recursive resolver and interpret the response status and TTL.
The domain and record type are sent to our endpoint and Cloudflare's DNS resolver only when you select Look up DNS. Do not enter private names or sensitive information.
Cancel stops waiting in this browser; a query already sent to the resolver may still finish.
Enter a public domain and select Look up DNS.
How to use DNS Lookup
- Enter a public domain, such as example.com; do not paste a URL.
- Choose the DNS record type and select Look up DNS. Nothing is queried automatically.
- Read the DNS status before using the records. Use Cancel to stop waiting or Copy to share the current result.
Example
Input / settings:
Illustrative query: example.com, record type A
Output:
Illustrative answer (not a live result): example.com. 300 IN A 192.0.2.1 TTL: 300 seconds
When to use
- Inspect A and AAAA answers while configuring a public service.
- Review public MX routing or TXT verification records.
- Compare public CNAME or NS answers with your DNS provider's configuration.
Overview
Look up public DNS records using Cloudflare's recursive resolver and interpret the response status and TTL.
Supported input
One public domain or record name, including IDNA international names and underscore labels such as _dmarc.example.com. Select A, AAAA, CNAME, MX, TXT, or NS. URLs, IP literals, ports, single-label names and local or non-DNS namespaces such as home.arpa, .local, .onion and .alt are rejected.
Output details
Cloudflare's DNS response code, answer record names, types, TTL in seconds, and presentation-format data. Returned CNAME records are shown alongside the requested type. No authority/additional sections are displayed.
Limitations
- This is a recursive resolver view, not an authoritative zone export, propagation check, HTTP reachability test, or proof that a service is available.
- Caches, split DNS, resolver location, and record rotation can produce different answers elsewhere. A TTL is a cache lifetime, not a countdown to worldwide propagation.
- NXDOMAIN means the resolver reports no such name. NODATA means no answer for the selected type; CNAME records may still be present. SERVFAIL can include DNSSEC validation or upstream failures.
- The DNSSEC AD flag is reported by the resolver. An unset flag is not proof of insecurity; this tool does not independently validate signatures.
- Queries have time, response-size, record-count and alias limits. Truncated responses may be incomplete. No extra queries follow aliases, and TXT quoting is preserved as returned.
- The tool is disabled unless its deployment is configured. Query only public names; do not enter private infrastructure names or secrets.
Privacy and security
On request, the domain and record type are sent to our Cloudflare endpoint and Cloudflare's DNS resolver. Our application does not persist queries or results; Cloudflare processes requests under its own policies.
References
- Cloudflare DNS over HTTPS JSON API
- Cloudflare public DNS resolver privacy
- RFC 1035 — DNS implementation and specification
Frequently asked questions
Does this query my device's DNS resolver?
No. Our endpoint asks Cloudflare's 1.1.1.1 recursive resolver. A corporate or local resolver may return different records.
Why are there no records for a name that exists?
The selected type may not exist. Check the status and choose another type. SERVFAIL and NXDOMAIN are different from an empty NOERROR answer.
Can I enter an international domain or a TXT record name?
Yes. International names are normalized to IDNA ASCII. Underscore labels such as _dmarc are accepted. Enter the name only, without scheme, path or port.
Are the query and results stored?
Our application keeps them in memory for the current lookup and does not save them to a database, browser storage, or analytics events. The domain and type are sent to Cloudflare, which has separate hosting and resolver privacy policies.
How is this different from DNS Record Parser?
DNS Lookup makes a live resolver query. DNS Record Parser reads records you paste and runs locally without a DNS query.
Does Cancel undo a DNS query?
No. Cancel stops waiting for the response in this browser. It cannot undo a query that has already reached the resolver.