DNS Lookup Tool to Query Records for Any Domain Name

Behind every domain name sits a small directory of records that tells the internet where its website lives, where its email goes, and which services speak for it. This DNS lookup tool queries those records for any domain and shows them in a readable form — the fastest way to answer questions like "where does this site's mail actually go?" or "did my DNS change take effect?"

What DNS Records Are and Why You Would Look Them Up

DNS — the Domain Name System — works like a phone book for the internet. When a browser wants example.com, it asks DNS for the address. But a domain holds more than one entry. Different record types point to different services, all published where anyone can query them.

Lookups are everyday work for anyone who runs a website or email: verifying a migration really moved, checking why mail lands in spam, confirming a verification record was published correctly, investigating a domain you are about to buy, or diagnosing why a subdomain refuses to load. Because the records are public, a lookup shows you exactly what the rest of the internet sees — not what you hope it sees.

The Record Types You Will Meet in the Results

• A and AAAA — the IPv4 and IPv6 addresses of the host. This is where the website itself lives.
• CNAME — an alias pointing one name at another hostname, common for subdomains handed to third-party services.
• MX — the mail servers that accept email for the domain, with priority numbers deciding the order they are tried.
• TXT — free-text records used for verification and email security policies such as SPF, DKIM selectors and DMARC.
• NS — the authoritative nameservers responsible for the domain's zone.
• SOA — the zone's administrative record, including its serial number and refresh timers.
• PTR — reverse lookups, mapping an address back to a hostname, mainly used by mail servers.

Running a Lookup, Step by Step

1. Open the DNS Lookup tool.
2. Type the domain name you want to inspect — for example, your own domain after a hosting change.
3. Click Query DNS to fetch the records.
4. Read through the results, grouped by record type, and note the values and TTLs shown.
5. If you need to keep or share the raw data, click Copy JSON Records to copy the full result set in JSON form.
6. To check a subdomain, run a separate lookup on the full subdomain name — records are published per name, not inherited automatically.

When you have changed records recently and the answers look stale, the companion DNS propagation check shows what different servers around the world currently return.

Real Jobs a Lookup Handles in a Minute

After a website migration. You moved hosts on Monday; the A record should now point at the new server's address. A lookup confirms the published value — and if it still shows the old address, you know the change was never saved or was made in the wrong zone.

Email stopped arriving. Mail problems are very often MX problems. If the MX records point at a provider you cancelled, or vanished during an edit, a lookup exposes it immediately, before you start blaming spam filters.

Verifying a third-party service. Mail platforms, analytics and domain-verification flows ask you to publish a specific TXT or CNAME record. A lookup tells you whether the record exists exactly as requested — a step people skip and then debug blindly. The MX lookup tool gives a focused view when mail routing is the whole question.

Researching a domain. Before buying or trusting a domain, its NS and MX records reveal which providers run its site and mail. Combined with a WHOIS lookup, you get a fair picture of how the domain is operated.

Why Answers Sometimes Look Wrong — and Other Traps

The most common confusion is caching. Every record carries a TTL — a lifetime in seconds — and resolvers keep answers until it expires. Change a record five minutes after lowering nothing, and much of the internet may serve the old value for hours. That is not the lookup lying; it is DNS working as designed.

Editing the wrong zone is the second trap. If your domain's NS records point to your registrar but you edited records at your host (or the reverse), the changes exist somewhere the internet never asks. Always confirm which nameservers are authoritative first — they are in the NS records themselves.

Watch out also for the root-versus-subdomain distinction: a record for www.example.com says nothing about example.com, and vice versa. And remember a lookup shows what is published publicly; it cannot see a private internal zone, so internal company hostnames will correctly return nothing here.

DNS Lookup Questions, Answered

Is it legal to look up any domain's records?

Yes. DNS records are published precisely so that other systems can query them; looking them up is normal, public network behaviour.

Why is a record I just added not showing?

Either it was added to the wrong zone, or resolvers are still serving cached answers until the old TTL expires. Verify the authoritative nameservers and wait out the TTL.

What does TTL mean in the results?

Time To Live — how many seconds other servers may cache that answer. Lower TTLs make changes spread faster but increase query load; 3600 seconds (one hour) is a common default.

Can a lookup tell me who owns a domain?

Not directly — that is registration data, held in WHOIS. DNS shows technical records; WHOIS shows the registrant and registrar details that are public.

Why does a domain have several A records?

Multiple addresses spread traffic across servers for capacity or resilience. Resolvers rotate through them, so consecutive lookups may list them in a different order.

What does it mean if there are no MX records?

The domain is not configured to receive email at those addresses — mail sent there has no published destination and will generally fail or fall back unpredictably.

What is the JSON output useful for?

The Copy JSON Records button gives you the complete result in a structured format — handy for pasting into a ticket, a script, or a change log.

Can this tool change or fix my DNS?

No. It only reads published records. Changes are made wherever your DNS zone is hosted — usually your registrar, host, or a DNS provider's control panel.

The Public Record Never Guesses

Most DNS mysteries dissolve the moment you can see the records the internet actually serves. Make this lookup part of your routine after every migration, mail change or verification step: two minutes of reading saves hours of guessing, and the answer it shows is the same one your visitors' devices are getting.