What is DNS Lookup
DNS Lookup shows the public records that connect a domain name to internet services. A and AAAA records point to IPv4 and IPv6 addresses. MX records identify mail exchangers. TXT records are often used for verification, SPF, DKIM, DMARC, and service ownership checks. NS records show authoritative name servers. This is the common online check people need when searching for DNS records, mail routing, or domain configuration.
A clear DNS view helps developers, site owners, and support teams debug domain launches, email delivery, CDN changes, verification records, and misconfigured name servers.
How to Use DNS Lookup
Enter a domain such as google.com. You can also paste a URL, and the tool will use the hostname for the lookup. A, AAAA, MX, TXT, and NS records are checked together by default so the result is useful without extra switches.
Review each record group separately. Empty groups mean the resolver did not return records for that type, not necessarily that the domain is broken.
Common DNS Lookup Use Cases
DNS Lookup is useful whenever a domain points to the wrong service, email stops arriving, a verification record is missing, or a migration needs a quick sanity check. Developers use A and AAAA records to confirm the addresses a browser or server may connect to. Operations teams use MX records to verify mail routing. Product and support teams use TXT records to check whether a third-party service has been authorized correctly.
The tool is also helpful during launches. When a site moves to a new CDN or host, DNS records are often changed before application traffic is switched. A lookup gives a compact view of the important record groups so the team can compare the expected values with the public answer. For public troubleshooting, this is faster than asking a user to install command-line tools.
How to Read DNS Records
A records point a domain to IPv4 addresses, and AAAA records point it to IPv6 addresses. If both exist, clients may choose either depending on network support and resolver behavior. MX records contain a priority and host name for mail delivery. Lower priority numbers are preferred. NS records show which name servers are authoritative for the domain, which matters when debugging delegation or stale DNS changes.
TXT records are flexible text values. They are commonly used for SPF, DKIM, DMARC, site verification, domain ownership checks, and service-specific configuration. Because TXT records can contain long strings, the result card preserves line breaks and provides copy actions. That makes it easier to compare a value with a provider dashboard without losing punctuation or spacing.
When a domain has several records of the same type, compare the whole set rather than only the first value. Load balancers, CDNs, mail providers, and verification services often publish multiple records on purpose, so repeated values are not automatically a mistake.
DNS Propagation and Caching Notes
This page checks DNS from one lookup location. It is not a global propagation checker. DNS answers can vary by resolver, region, cache age, and authoritative server behavior. A record that has just changed may appear updated in one place and stale in another until TTLs expire.
For a first diagnosis, this lookup is still valuable. It confirms the public answer visible to the lookup tool and shows whether the domain has the expected record groups.
Troubleshooting DNS Lookup
If the tool reports an invalid domain, remove spaces, unsupported characters, or incomplete URLs. The lookup accepts normal domains and URLs with hostnames, but it does not accept localhost, raw paths, or malformed schemes. If you pasted a URL, only the hostname is queried; the path and query string are ignored.
If a record group is empty, check whether that record type is expected for the domain. Not every domain has IPv6, mail, or TXT records. If every group fails, the domain may not exist, name servers may not be reachable, or a temporary lookup issue may have occurred.
When investigating a recent DNS change, write down the old value, the expected new value, the record type, and the TTL shown in your DNS provider. A lookup result becomes much easier to interpret when it is compared against a specific expected record instead of a vague statement that DNS is not working.
That comparison also helps teams communicate clearly during incidents because everyone can discuss the same record name, type, returned value, owner, priority, and next action.
Clear DNS notes reduce repeated checks and make handoffs calmer.