Home › All Tools ›

DNS Lookup

Use DNS Lookup online for free at FreeToolZones — no sign-up, no watermark.

Loading tool...

Every time you type a domain name into a browser, a DNS lookup translates that name into the addresses and records a computer needs to reach the right server. The DNS Lookup tool lets you run that same query yourself and see the answer. You enter a domain, choose a record type, and the tool asks Google Public DNS over an encrypted connection, then shows the records it returned, including each record value and its TTL. It is the fastest way to check whether a domain points to the right server, whether mail records are present, or whether a recent DNS change has taken effect at a major public resolver.

DNS problems are common and confusing because the symptoms look like other failures: a site that will not load, email that bounces, or a subdomain that works for one person and not another. Seeing the actual records removes the guesswork. Instead of wondering whether a change was saved, you can read exactly what a resolver returns right now. This article explains what the tool shows, how to run each type of lookup, what the results mean, and where the limits of a browser-based check lie.

What Is the DNS Lookup Tool?

The DNS Lookup tool is a free online tool that queries DNS records for a domain name using Google Public DNS through DNS-over-HTTPS. You provide a domain such as example.com and pick one record type at a time: A, AAAA, MX, TXT, NS, or CNAME. The tool sends the query to the resolver, reads the answer section of the response, and displays the results in a table with four columns: Name, Type, TTL, and Value. It also shows a short status note explaining the response code, for example that the name resolved, that it does not exist, or that the resolver reported a server failure.

DNS, the Domain Name System, is the directory of the internet. A domain name is easy for people to remember, but computers connect using IP addresses and service records. DNS records store those mappings. An A record maps a name to an IPv4 address, an AAAA record maps it to an IPv6 address, an MX record names the mail servers that accept email for the domain, a TXT record holds text used for verification and email authentication, an NS record names the authoritative name servers, and a CNAME record makes one name an alias of another. When any of these records is missing or wrong, the service that depends on it fails, even though the domain itself is registered and paid for.

This tool reflects what Google Public DNS sees at the moment you run the check. That is a useful, well-defined viewpoint: Google Public DNS is a large resolver used by many networks, so its answer is a good indicator of what most visitors will see once cached records expire. It is not, however, the same as asking the domain authoritative name servers directly, and it is not the same as asking every resolver in the world. A record that was changed minutes ago may still show the old value until the old TTL expires, and different resolvers may disagree briefly during that window.

How to Use the DNS Lookup Tool

The widget has two inputs and one button. The steps below match exactly what you will see on the page.

  1. Enter the domain name. In the “Domain name” field, type a domain without http://, for example example.com. The tool cleans up the input: if you paste a full URL, it strips the scheme, path, query, and port, keeping only the host name. Subdomains work too, so you can look up www.example.com or mail.example.com directly.
  2. Choose a record type. Use the “Record type” dropdown to pick one type: A for IPv4 addresses, AAAA for IPv6 addresses, MX for mail servers, TXT for text records, NS for name servers, or CNAME for aliases. Each run checks one type, so run the tool again to check a different type.
  3. Press Look Up DNS Records. The tool first checks that the host name is valid. If it is not, you will see an error asking for a valid domain name. If it is valid, the tool shows that it is querying DNS records for the host.
  4. Read the status note and the table. The result heading names the host and the record type. Under it, a status note explains the response: OK means the name resolved, NXDOMAIN means the name does not exist, and SERVFAIL means the resolver reported a server failure. If records were returned, they appear in a table showing the record name, type, TTL in seconds, and value. If none were returned, the tool says so plainly.
  5. Note the source line. Below the results, the tool states that the source is Google Public DNS over DNS-over-HTTPS and that results reflect what that public resolver sees right now. Keep that in mind when comparing with results from your own network or another lookup service.

TTL, shown in the table as a number of seconds, is the time a resolver is allowed to cache the record before asking again. A TTL of 300 means five minutes, 3600 means one hour, and 86400 means one day. Short TTLs make changes spread quickly but increase query load; long TTLs make lookups faster but slow down changes. When you change a record, the old value can keep appearing until the old TTL expires, which is the most common reason a correct change seems not to work at first.

Key Features of the DNS Lookup Tool

  • Six record types. A, AAAA, MX, TXT, NS, and CNAME cover the records most site owners and email administrators need to check. Each type answers a different question, from “which server hosts this site” to “which servers accept mail for this domain.”
  • Google Public DNS over HTTPS. Queries go to Google Public DNS using DNS-over-HTTPS, an encrypted channel. The source is named in the results, so you always know whose view of DNS you are reading.
  • Full answer table. Results show the record name, type, TTL, and value for every answer returned. Multiple records, such as several MX entries or several A records for load balancing, all appear, not just the first one.
  • Plain status explanations. Response codes are translated into plain language: OK, NXDOMAIN, and SERVFAIL are each explained, and any other code is shown numerically. You do not need to memorize DNS response codes to understand the result.
  • Forgiving input handling. Pasted URLs are cleaned automatically, so pasting https://example.com/page still looks up example.com. Invalid host names produce a clear error before any query is sent.
  • Honest empty results. When no records of the requested type exist, the tool says that no records were returned rather than showing a blank page or an invented value. An empty MX result, for example, is itself useful information.

Practical Use Cases

Checking a website move or server change

When a site moves to a new host, its A record must point to the new server address. A site owner can run an A lookup before the move to record the old address, update the record at the DNS provider, and then run the lookup again to confirm the new address appears. If the old address still shows, the likely cause is caching: the old TTL has not expired yet. Checking the TTL in the result tells the owner how long to wait before worrying. The same check confirms that a subdomain such as shop.example.com points where it should after it is created.

Diagnosing email delivery problems

Email depends on MX records to find the receiving server and on TXT records for SPF, DKIM, and DMARC authentication. If mail bounces or lands in spam, an MX lookup shows whether mail servers are listed at all and in what priority order, while a TXT lookup shows whether the authentication records exist. A missing MX record explains total mail failure, and a missing or mistyped TXT record explains authentication failures. These checks do not prove that the mail server itself works, but they rule out the DNS half of the problem quickly.

Verifying domain ownership and service setup

Many services ask you to add a TXT or CNAME record to prove you own a domain or to connect the service. After adding the record, a lookup of that exact type confirms it is visible to a public resolver before you press the verify button in the other service. This avoids the frustrating loop of failed verifications caused by a record that was saved in the wrong zone, typed with an extra character, or simply not yet visible. Checking the exact subdomain the service asked for, rather than the bare domain, is important because verification records often live on a specific host name.

Investigating a domain that will not resolve

When a domain shows a “server not found” error, an NS lookup shows which name servers are responsible for it, and an A lookup shows whether an address exists. An NXDOMAIN status means the name does not exist in DNS at all, which points to a registration, name server, or zone problem rather than a web server problem. A SERVFAIL status points to a resolver or authoritative server failure. Each outcome leads to a different next step: contact the registrar, fix the name servers, or wait and retry. Without the lookup, all of these failures look identical in a browser.

Learning how a domain is configured

Students, junior developers, and curious site owners use DNS lookups to learn how real domains are put together. Looking up the NS records of a familiar site shows which DNS provider it uses, its MX records show which mail service handles its email, and its TXT records often reveal the services it has authorized. Comparing the A and AAAA results shows whether the site supports IPv6. These are all public records by design, and reading them is a practical way to understand how the pieces of a domain fit together.

Tips and Best Practices

  • Check the exact host name. Records for example.com, www.example.com, and mail.example.com are independent. Always look up the precise name that is failing or being configured.
  • Check one type at a time and write down results. Because each run covers one record type, keep notes when diagnosing a problem that spans several types, such as a site move that involves A, CNAME, and MX records together.
  • Read the TTL before concluding a change failed. If a change was made recently, compare the time since the change with the TTL. A record with a one-day TTL can legitimately show the old value for hours after an update.
  • Lower the TTL before a planned move. A day or two before changing servers, set the TTL low, for example 300 seconds, so the change spreads quickly when you make it. Raise it again afterward if you prefer longer caching.
  • Compare with a second resolver when results surprise you. Use the DNS Propagation Checker, which queries both Google and Cloudflare, to see whether two major resolvers agree. Disagreement usually means propagation is still in progress.
  • Do not edit records you do not understand. Deleting an MX or TXT record can break email, and changing NS records can take a whole domain offline. Use lookups to understand the current setup before changing anything, and keep a copy of the old values.

Limitations

This tool queries one resolver, Google Public DNS, from your browser. It does not query the domain authoritative name servers directly, so it cannot show records that the authoritative servers hold but the resolver has not fetched or has cached in older form. It also cannot show the full DNS zone, only the answers for the single type you requested. Records that exist but are not of that type stay hidden until you look them up separately.

The tool supports six record types and does not offer others, such as SOA, CAA, SRV, PTR, or DNSSEC-related types. SOA data, which includes zone timing values, is not displayed, although the tool recognizes the type code if it appears in an answer. The tool also cannot diagnose problems beyond DNS: a correct A record does not prove the web server is running, a correct MX record does not prove the mail server accepts connections, and a successful lookup does not prove the site loads. Pair DNS checks with the uptime and ping tools when you need to test the server itself. Finally, if the Google DNS service is unreachable from your network, the lookup fails with an error rather than falling back to another resolver in this widget.

Frequently Asked Questions

Why does the lookup show an old address after I changed my DNS?

Because of caching. Resolvers keep records for the TTL period, so the old value can persist until that time expires. Check the TTL in the result: a TTL of 3600 means up to an hour. Wait for the TTL to pass, then check again. If the old value persists well beyond the TTL, check that you edited the correct zone at the correct provider.

What does NXDOMAIN mean?

NXDOMAIN means the name does not exist in DNS according to the resolver. The domain may be unregistered, the subdomain may never have been created, or the name servers may be misconfigured. It is a DNS-level answer, not a web server error, so fixing it means fixing records or name servers, not the website files.

Can I look up subdomains and www versions?

Yes. Enter the full host name, such as www.example.com or blog.example.com. Each host name has its own records, so a lookup of the bare domain tells you nothing about its subdomains. CNAME records are common on www host names, and the tool will show the alias target when you query the CNAME type.

Does this tool change my DNS records?

No. It only reads records through a public resolver. To change records, you must sign in to your DNS provider or registrar and edit the zone there. This tool is for checking and diagnosing, and it cannot create, edit, or delete any record.

Why do different DNS checkers show different results?

Different resolvers cache records at different times and may be in different locations. During propagation after a change, disagreement is normal and temporary. The DNS Propagation Checker on this site queries two major resolvers side by side, which makes such differences visible instead of confusing.

Related Tools

Use these tools alongside a DNS lookup to test the servers and addresses behind the records.

Browse More Tools