A domain or subdomain is not resolving where you expect it to.
DNS Lookup Tool
Check live DNS records for a domain or hostname.
Use this DNS lookup tool to inspect A, AAAA, CNAME, MX, TXT, NS, and other live DNS responses so you can confirm whether a record exists, compare it with your expected configuration, and move to the right troubleshooting step faster.
Inspect live DNS response for a domain before moving to the next DNS troubleshooting step.
Lookup result
example.com
NOERROR
Type Value TTL
No records were returned for this query by the resolver.
What this DNS tool does
DNS Lookup queries a domain or hostname and returns the DNS records currently visible for the selected type.
Use it to confirm whether a record exists, inspect the returned value, review TTL, and check whether DNS is returning a usable answer at all.
It does not confirm application behavior by itself. A correct DNS answer does not mean a website, mail server, or other service behind that record is working correctly.
When to use this tool
A website opens from one network but not another and you need to compare the DNS answer first.
A DNS change was made recently and the expected record is still not visible.
Mail, verification, or certificate checks depend on a TXT, CNAME, or other DNS record being present.
You suspect the record exists, but the returned value is wrong, stale, or incomplete.
You need a fast first check before moving to propagation, nameserver, DNSSEC, or application-layer tests.
How to use DNS Lookup
- Enter the domain or hostname you want to check.
- Select a record type if you want to narrow the lookup.
- Run the lookup and review the returned records, TTL, and DNS response status.
- Compare the live answer with the configuration you expected to publish.
- If the result is missing, wrong, or incomplete, move next to nameserver, propagation, DNSSEC, or service-level checks.
How to interpret DNS lookup results
Record found
Likely meaning: DNS returned one or more answers for the name and record type you queried.
Common causes: Usually means the record is published and visible from the resolver used for the lookup.
Next action: Compare the returned value, TTL, and target with your intended configuration.
No record found
Likely meaning: The lookup returned no answer for that record type.
Common causes: Common causes are wrong hostname, wrong record type, missing record, or the record being published in the wrong zone.
Next action: Recheck the exact name, then verify nameservers and propagation.
Record value unexpected
Likely meaning: A record exists, but the value does not match what you expected to publish.
Common causes: This often points to stale data, a wrong target, a partial migration, or edits made in the wrong DNS provider.
Next action: Compare the live answer against the authoritative zone and then check propagation.
Multiple records returned
Likely meaning: More than one answer exists for the same name and type.
Common causes: This can be valid for load balancing, MX, or TXT usage, but it can also reveal old records left behind.
Next action: Confirm whether multiple answers are expected. If not, remove stale or conflicting entries.
TTL looks different than expected
Likely meaning: The record exists, but the returned cache time is not what you thought it would be.
Common causes: Recent DNS changes, recursive caching, or provider-side TTL handling can all explain this.
Next action: Check the authoritative answer and allow caches to expire before retesting.
NXDOMAIN
Likely meaning: The queried name does not exist in DNS.
Common causes: Typos, missing subdomains, the wrong zone, or an expired domain are common reasons.
Next action: Confirm the exact hostname and make sure the record was published in the correct zone.
SERVFAIL
Likely meaning: The resolver could not complete the DNS query successfully.
Common causes: This often points to DNSSEC failures, broken delegation, or upstream nameserver problems.
Next action: Verify nameservers first, then run DNSSEC checks and compare authoritative behavior.
Timeout or no response
Likely meaning: The query did not complete within the expected time window.
Common causes: Authoritative server reachability issues, resolver problems, or network path issues can all cause this.
Next action: Retry from another resolver and check authoritative nameserver health.
Common DNS issues this tool helps uncover
Missing or incorrect record values
Record published in the wrong zone or wrong DNS provider
Recursive cache differences after recent DNS changes
Nameserver delegation mismatch between registrar and zone host
CNAME conflicts or invalid chaining
TXT formatting problems for SPF, verification, or DKIM-related checks
Resolver differences between networks or locations
DNSSEC misconfiguration causing broken resolution
Split-horizon DNS where internal and public answers are different
Next steps after DNS Lookup
Check DNS propagation
Use this when a new record should be live but some resolvers may still have older cached answers.
Verify nameservers
Use NS Lookup when the record may have been added in the wrong DNS zone or on the wrong provider.
Validate DNSSEC
If you see SERVFAIL or inconsistent resolution, check whether DNSSEC is breaking validation.
Move to service checks
If DNS looks correct, continue to Ping, HTTP Check, or MX Lookup depending on the service you are troubleshooting.
Related tools
NS Lookup
Check authoritative name servers and delegation for a domain.
DNS Propagation Check
Verify whether recent DNS changes are visible across resolvers.
DNSSEC Check
Validate whether a domain has DNSSEC configured correctly.
MX Lookup
Inspect mail exchange records and delivery destinations for a domain.
Ping
Check whether a host responds and measure round-trip latency.
HTTP Check
Review HTTP response status, headers, and redirect behavior.
DNS Lookup FAQ
What does this DNS Lookup tool check?
It checks live DNS responses for a domain or hostname and returns the records available for the selected type, such as A, AAAA, CNAME, MX, TXT, or NS.
What input should I enter?
Enter a domain or hostname such as example.com, www.example.com, mail.example.com, or selector._domainkey.example.com. Do not enter a full URL.
Why does the result sometimes differ by resolver or location?
Recursive resolvers cache DNS answers independently, and geographic or network-specific resolver behavior can show different results during propagation windows.
Why would a DNS lookup return no record found?
The record may not exist, may be published for a different hostname, may be in the wrong zone, or may not be visible yet from the resolver you used.
What should I check after DNS Lookup?
Most often you should verify nameservers, compare propagation status, and then move to the service-level tool that depends on the record.
How is DNS Lookup different from NS Lookup?
DNS Lookup checks the returned records for a name. NS Lookup focuses on which nameservers are authoritative for the domain and whether delegation looks correct.