Look up DNS records for any domain using DNS over HTTPS. Query A, AAAA, MX, CNAME, TXT, and NS records instantly — free, private, and browser-based.
100% Client-Side Execution Zero Server Storage Infinite File Size Limits GDPR/KVKK Privacy Compliant
Last updated
DNS Lookup is a free, browser-based tool
from UseToolSuite's
Network & API Tools collection.
All processing happens locally on your device — your data is never uploaded to any server.
Use the tool below, then scroll down for detailed documentation, frequently asked questions, and related resources.
Advertisement
Querying Google & Cloudflare DoH endpoints...
Google DNS
Cloudflare DNS
What is DNS Lookup?
DNS Lookup is a free tool that queries Domain Name System records for any public domain using DNS over HTTPS (DoH). It supports A, AAAA, MX, CNAME, TXT, NS, and CAA record types — the most common records needed for troubleshooting domain resolution, email delivery, domain verification, and nameserver configuration. Queries are routed simultaneously through Google and Cloudflare public DNS endpoints for real-time propagation checking.
Zero-Knowledge Architecture
Unlike typical DNS lookup tools that route requests through backend servers (which can cache or log your activity), this tool executes entirely client-side. The browser directly communicates with DoH endpoints via `fetch`, meaning there is absolutely no intermediate server logging your domain queries. The raw JSON payload and parsing happens in your own local environment.
Record types, decoded for real tasks
Knowing what each record does matters more than memorising letters. Here is the working developer’s view:
Record
Answers the question
You touch it when…
A / AAAA
”What IP serves this name?” (v4 / v6)
Pointing a domain at a server
CNAME
”What other name should I follow?”
Aliasing www → apex, or to a SaaS host
MX
”Where does email for this domain go?”
Setting up or debugging mail
TXT
”What text policy is published here?”
SPF, DKIM, DMARC, domain verification
NS
”Which servers are authoritative?”
Delegating or migrating a zone
SOA
”Who owns this zone and how fresh is it?”
Checking serial numbers after a change
Debugging email deliverability with three lookups
When mail goes to spam, the diagnosis is almost always in DNS, and three queries find it:
MX — confirm mail is routed to the provider you expect, with sane priorities (lower number = higher priority).
TXT (apex) — read the SPF record. A common failure is multiple SPF records (only one is allowed) or a stray -all that hard-fails legitimate senders.
TXT (_dmarc subdomain) — check the DMARC policy. p=reject with a misaligned SPF/DKIM setup will bounce your own newsletters.
Get all three aligned and inbox placement usually fixes itself within a TTL or two.
Why this tool and dig sometimes disagree
This lookup uses DNS over HTTPS against Google and Cloudflare’s public recursive resolvers. Your local dig may hit your ISP’s resolver, your corporate split-horizon DNS, or a caching layer with a different TTL countdown. So three honest answers can all be “correct” simultaneously — they reflect different caches at different moments in the propagation window. To see the uncached truth, query the domain’s authoritative nameserver directly (dig @ns1.example.com example.com). Disagreement between resolvers right after a change is propagation in progress, not a bug.
TTL is a planning tool, not just a number
Before any migration, lower the TTL on the records you intend to change — to 300 seconds (5 minutes) a day ahead of time. That way, when you flip the record, the old value drains from caches in minutes instead of the 24–48 hours a high TTL imposes. After the change settles, raise the TTL back up to cut query load. Treating TTL as a deliberate lever rather than a default is what separates a smooth cutover from a day of “it works for me but not for them.”
How to Use This Tool
1
Enter Domain
Type the domain name (e.g. example.com).
2
Select Record
Choose the DNS record type you want to query.
3
Resolve
Click Lookup to fetch records simultaneously from Google and Cloudflare for comparison.
How helpful was this tool?
Click to rate
Awesome! Glad it helped.
We don't have a marketing budget. The best way to support this free tool is by sharing it with other developers!
Help us improve!
Sorry it didn't meet your expectations. We're always looking to make these tools better. What was missing or broken?
Essential terms and definitions related to DNS Lookup.
DNS (Domain Name System)
The hierarchical naming system that translates human-readable domain names (like example.com) into IP addresses (like 93.184.216.34) that computers use to identify each other on the network. DNS is often called the phonebook of the internet.
TTL (Time To Live)
A value in DNS records that specifies how long (in seconds) a resolver should cache the record before querying the authoritative server again. Lower TTL values mean faster propagation of changes but higher query load on nameservers. Common values range from 300 (5 minutes) to 86400 (24 hours).
Authoritative Nameserver
A DNS server that holds the original (authoritative) DNS records for a domain. When a recursive resolver needs to look up a domain, it ultimately queries the authoritative nameserver to get the definitive answer. NS records in the parent zone point to these servers.
Frequently Asked Questions
What is DNS over HTTPS (DoH) and why use it?
DNS over HTTPS encrypts DNS queries using the HTTPS protocol, preventing eavesdropping and manipulation of DNS data. This tool uses Google Public DNS (dns.google) or Cloudflare (cloudflare-dns.com) DoH endpoints, which are free, require no API key, and work directly from the browser.
What do the different DNS record types mean?
A records map a domain to an IPv4 address. AAAA records map to IPv6. MX records specify mail servers for the domain. CNAME records create aliases pointing to another domain. TXT records hold text data like SPF (email authentication) and domain verification. NS records identify the authoritative nameservers for the domain.
Why might DNS lookup results differ from what I expect?
DNS uses caching at multiple levels (browser, OS, ISP, recursive resolver). Results may reflect cached data with a TTL (Time To Live) that has not yet expired. If you recently changed DNS records, propagation can take from minutes to 48 hours depending on the TTL values set on the records.
Can I look up DNS records for internal/private domains?
No. This tool queries public DNS resolvers (Google/Cloudflare), which can only resolve publicly registered domain names. Internal domains that exist only on private DNS servers are not accessible from public resolvers.
Why can't I put a CNAME on my root (apex) domain?
DNS rules forbid a CNAME coexisting with any other record on the same name, and the apex (example.com) must carry NS and SOA records. A CNAME there would conflict with them, so the lookup either fails or behaves unpredictably. Modern DNS providers offer 'CNAME flattening', 'ANAME', or 'ALIAS' records that imitate apex CNAME behaviour by resolving the target and serving its A/AAAA records — that is what you want for pointing example.com at a platform like Netlify or a load balancer.
How do I verify SPF and DMARC with a TXT lookup?
Query the TXT record of your domain for SPF — it starts with 'v=spf1' and lists the servers allowed to send mail (e.g. 'v=spf1 include:_spf.google.com ~all'). For DMARC, query the TXT record at the special subdomain _dmarc.yourdomain.com; it starts with 'v=DMARC1' and sets policy (p=none, quarantine, or reject). DKIM lives at selector._domainkey.yourdomain.com. If any of these are missing, your mail is far more likely to land in spam.
Troubleshooting & Technical Tips
Common errors developers encounter and how to resolve them.
No records found for domain
Verify the domain name is spelled correctly and is a registered domain. Some record types may not exist for all domains — for example, not all domains have AAAA (IPv6) or MX records. Try querying a different record type or check if the domain is active.
DNS query timeout or network error
This can occur due to network connectivity issues, ad blockers intercepting the DoH request, or browser security policies. Try disabling ad blockers temporarily or switching between Google and Cloudflare DoH providers.
SERVFAIL or NXDOMAIN response
NXDOMAIN means the domain does not exist in DNS. SERVFAIL indicates the authoritative nameserver failed to respond. For NXDOMAIN, verify the domain is registered. For SERVFAIL, the domain's nameservers may be misconfigured — check with the domain registrar.
Related Guides
In-depth articles covering the concepts behind DNS Lookup.
We use cookies to show personalized ads via Google AdSense.
All our tools process data locally in your browser — no personal data is collected.
You can accept personalized ads or continue with general ads only.
Privacy Policy
