DNS Lookup
Check public DNS records for a domain to verify website, email, and nameserver setup.
DNS Record Lookup
A DNS lookup helps you query the public DNS data tied to a domain so you can review the records behind website routing, email delivery, and DNS delegation. Use it when you need to look up DNS records before troubleshooting a site issue, verifying a mail setup, or confirming that a domain is pointing where you expect.
How To Check DNS Records
- Enter the domain name in the input field.
- Click Get Records.
- Review the DNS records returned for that domain.
- Compare the result with the DNS configuration you expected to publish.
When To Use a DNS Lookup Tool
This tool is the right choice when a domain is not resolving as expected, when email routing needs verification, or when you want to confirm that nameserver and record changes are present in public DNS. It is also useful before domain migrations, SSL issuance, third-party verification, or mail authentication setup, because those workflows depend on published DNS records being correct.
A DNS lookup is not the same as a propagation checker. A standard lookup shows the records a resolver can return for a domain, while a propagation checker is better when you need to compare what multiple resolvers in different locations are seeing after a recent change. TTL settings also affect how quickly updates are reflected across cached responses.
How To Read the Results After You Lookup DNS Records
A and AAAA records
A records map a name to an IPv4 address, and AAAA records map a name to an IPv6 address. If a website is unreachable or loading from the wrong server, these are often the first records to inspect because they determine where traffic is sent at the IP layer.
CNAME records
A CNAME record points one hostname to another hostname instead of directly to an IP address. This matters when a subdomain should follow another canonical host, and it also matters because a CNAME is not interchangeable with every other record type at the same name.
MX and TXT records
MX records define where mail for a domain should be delivered and in what priority order. TXT records often carry verification tokens or email policy data such as SPF and related authentication content, so they are frequently checked during mail onboarding and domain verification work.
NS and SOA records
NS records identify the authoritative nameservers for a zone, which is essential when you are confirming delegation or troubleshooting a mismatch between registrar and DNS host. SOA data is more administrative, but it can still help when you need to understand which zone is authoritative and whether you are looking at the right source of truth.
What To Do After a DNS Record Lookup
If the returned records match your intended setup, the next step is usually to test the service that depends on them, such as the website, mail flow, or domain verification process. If the records are missing, pointing to the wrong target, or still showing older values, check whether you edited the correct hostname, whether the change was made at the authoritative DNS provider, and whether cached data governed by TTL may still be in circulation.
When you need to check DNS records during a change window, compare what you expected to publish with what the lookup actually returns. That simple comparison prevents many common mistakes, especially when the issue is not the domain itself but the exact record name, record type, or target value.
Common Mistakes When You Check DNS Records
One common mistake is checking the root domain when the record actually lives on a subdomain such as www, mail, or a verification host. Another is treating a CNAME like a direct destination instead of following it to the final answer. A third is assuming that a recently edited record should appear everywhere immediately, even though cached responses can persist until TTL expires.
It is also easy to focus on one record and miss the wider dependency. A website problem may involve A, AAAA, CNAME, and NS records together, while an email issue may require checking MX plus the TXT records used for policy and verification. A better DNS records lookup is not just about finding a value; it is about confirming that the whole path is coherent.
Worked Example: Checking MX and TXT Records Before an Email Change
A company moves email for example.com to a new provider and wants to know whether the domain is ready for the cutover. The DNS lookup shows that the new TXT policy record is already published, but the MX records still point to the old mail servers. That tells you the verification side may be in place while live mail routing has not switched yet, so the right next step is to correct the MX values or wait for TTL-driven cache expiry before testing inbound delivery again.
What This DNS Lookup Can and Cannot Confirm
This tool is best for checking what public DNS records are available for a domain at lookup time. It can help you validate configuration, spot missing records, and decide whether a website, mail setup, or delegation issue is likely tied to DNS.
What it cannot do on its own is prove that every region is already updated, replace a dedicated reverse DNS workflow, or guarantee that the downstream service will accept the configuration without further testing. That is why the most useful DNS lookup pages do more than return data: they help users interpret the result and decide what to verify next.