DNS Lookup

Network

Query DNS records including A, AAAA, MX, TXT, NS, CNAME, SOA and CAA via Google or Cloudflare DoH. Inspect record name, type, TTL and data in one click.

Samples:
Domain

About DNS Lookup

When a site will not load, the first question is usually which address the domain actually resolves to. A DNS lookup tool moves that step out of the terminal and into the browser, to confirm whether a record took effect, whether it points at the intended host, and what each record type returns. Lookup hands a domain plus a record type to a resolver and returns the matching records. The common types divide the work. A gives an IPv4 address, AAAA an IPv6 address, CNAME marks the name as an alias of another domain. MX names the hosts that accept mail, TXT is routinely used for ownership verification and anti-spam policy, and NS declares which servers are authoritative for the zone. Practical notes: When "I changed the record but nothing happened", query authoritative and local resolution separately: authoritative reflects whether the record is actually published, while local resolution layers caches on top. So a mismatch simply means the cache has not expired and the fix is waiting rather than editing again. After switching DNS providers pay attention to TTL, since a longer TTL means slower propagation; lower it before the migration and raise it afterwards. Limits: Browser lookups are constrained by same-origin policy and go through a public DNS API, so what you see is the result that API observes rather than your machine's real resolution path. Internal domains and split-horizon setups that return different addresses inside and outside can look completely different here, and such investigations belong on the command line inside the network. A CNAME cannot coexist with other record types under the same name, which is a protocol restriction rather than a tool flaw, and conflicting configuration simply fails to resolve. Propagation is also gradual, with recursive resolvers worldwide updating at different times, so one query is not evidence that the change is live everywhere. Data and privacy: a lookup reveals which domain you are investigating, and internal or unreleased project domains are especially sensitive. This tool queries from the browser without logging what you searched for and keeps no history on a server; for sensitive names, query from the command line locally. Worth fixing in your diagnostic order: confirm the resolution result matches expectation, then confirm the network layer is reachable, and only then suspect the application. Reversing that order wastes a lot of time in irrelevant directions. For routine maintenance, keep key domain records and their TTLs in configuration management, note the current values before a change, and verify with several public resolvers immediately afterwards, which prevents the classic accident of changing a record and never restoring it. Teams running canary or disaster-recovery switches should also prepare a rollback version of the records before flipping, so a mistake does not leave them reconstructing values from memory. Getting started is simple: query the record type you actually need, address records for a website and mail records for email. Then check whether the number of returned values matches expectations, since several addresses usually means load spreading, and finally confirm no stale address is left behind. For ongoing care, monitor critical domains and alert when the resolution result changes, so an expiring domain, an accidental edit or a provider outage is discovered before users complain rather than after traffic drops.

How It Works Internally

A lookup hands a name plus a record type to a resolver and gets back the matching set. The types divide the work: address records give IPs, alias records declare another name as canonical, mail exchange records name the receiving hosts, text records carry ownership verification and anti-spam policy, and name server records declare who is authoritative. Results also layer caches, so "my change did not take effect" usually just means a cache has not expired.

The common record types
Inputoltool.net
OutputA → IPv4 address | AAAA → IPv6 address | MX → mail host and priority | TXT → verification and policy strings

Measured on This Page

Lookup worksexample.com A returns 172.66.147.243 and 104.20.23.154 with TTL 300s — real current resolution, not a hard-coded sample
External dependency disclosedThe page states plainly that it queries Google or Cloudflare over DoH — necessary disclosure, since the domain leaves for a third party, unlike the purely local tools on this site
Record typesEight types: A, AAAA, MX, TXT, NS, CNAME, SOA and CAA, covering everyday troubleshooting
Failure pathAn invalid name reports an NXDOMAIN-style error rather than presenting 'no records' as success

The usual confusion with a DNS tool is why results differ from your local dig, and there are 3 common reasons: you are not querying the same resolver — this page talks DoH to Google or Cloudflare while your office or ISP recursive resolver caches something else, so CDN answers legitimately differ; caching and TTL — a changed record can linger for one TTL; and geography or path — authoritative servers return nearer nodes based on EDNS client subnet. Know the privacy boundary too: every domain looked up here passes through an external DNS provider, so weigh that before troubleshooting internal hostnames.

How this was measured: An A lookup for example.com was run and the returned addresses and TTL checked, alongside a check of whether the page discloses that queries go to an external DoH service. · Measured 2026-10-31

How to Use

  1. Open "DNS Lookup"
  2. Enter a domain and choose a record type such as A or MX
  3. Run the query with the button or the Enter key
  4. The table lists name, type, TTL and record data
  5. Copy a single record with the icon at the row end

Use Cases

  • Resolution troubleshooting — Check A/AAAA records to confirm the domain points at the right IP and root-cause "site won't load".
  • Mail config audit — Check MX and TXT (SPF/DKIM) to fix rejected or junked email.
  • Migration validation — Compare old and new records and TTL after a DNS change to confirm global propagation.
  • Certificate authorization — Check CAA to ensure only designated CAs may issue certs for the domain.
  • Delegation mapping — Check NS and SOA to clarify subdomain delegation and zone master/slave.
  • Verify CDN mapping — Resolve A/AAAA records to confirm the domain points to the expected CDN edge IPs after a provider switch.
  • Detect domain takeover — Check CNAME records for dangling DNS that could lead to subdomain takeover by an unregistered target.

FAQ

Which provider handles the query?

You can switch between Google and Cloudflare; requests go directly to the DoH endpoint (dns.google or cloudflare-dns.com), not relayed by this site.

Why "No records found"?

The domain has no record of that type — possibly unconfigured or wrong type selected; try NS or SOA to confirm the domain exists.

What unit is TTL?

Seconds. It is how long the record may be cached; after a change, expect roughly one TTL for global propagation.

Can my queries leak?

DoH is HTTPS-encrypted so third parties can't easily snoop, but the DoH provider itself sees the request.

Can it do reverse (PTR) lookups?

This release focuses on forward records; PTR reverse lookups aren't provided — use dig -x on the command line.

Results differ from dig/nslookup — which one is right?

Usually caching. Browsers, the OS resolver and recursive resolvers each cache and keep serving old values until TTL expires, while dig queries your configured server directly. Treat the authoritative server answer as truth; use this tool for a quick cross-check.

Why can I not find TXT / CNAME records?

Two common causes: the domain genuinely has no such record (many sites only set A/AAAA and MX), or you queried a subdomain while the record lives on the parent. Query the parent zone; if it is still empty the record simply does not exist.

The lookup keeps timing out or failing — what should I check?

In order: verify the spelling and TLD (a missing .com yields NXDOMAIN); confirm your network allows outbound DNS (corporate networks often block port 53); confirm the domain is actually registered. Queries run from the browser, so a proxy or firewall will show up as a timeout.