DNS
Resolvers can return different cached records depending on geography, TTL and propagation state.
Network & Web Tools
Pro diagnostic reportDNS Lookup Online Free
Look up A, AAAA, MX, TXT, CNAME, NS and SOA records for a public hostname.
Diagnose
Run a bounded public check.
Understand
See a health score and explanation.
Act
Follow prioritized recommendations.
About this tool
DNS translates hostnames into the records used by browsers, mail servers and other internet services. This lookup uses the server-side DNS resolver to display common public record types. It is useful for checking a new domain setup, mail routing, verification TXT values, nameserver changes and basic troubleshooting.
Common use cases
- ✓ Verify the IP address behind a domain.
- ✓ Check mail exchanger priority and hostnames.
- ✓ Review TXT records used by SPF or service verification.
- ✓ Confirm authoritative nameservers and SOA information.
How to use it
- Enter a public domain or hostname without a path.
- Choose the record type you want to inspect.
- Run the lookup and review every returned record.
- Compare the result with your DNS provider when a recent change is still propagating.
Important interpretation notes
- • DNS answers can differ by resolver, cache state and geographic location.
- • A successful DNS lookup does not prove that the website or mail service is working.
- • TXT results may contain security or verification data; avoid sharing sensitive values unnecessarily.
Professional interpretation guide
Understand and verify your dns lookup results
Use the result as a focused diagnostic signal. Verify important findings before changing DNS, hosting, security, caching or application configuration.
What the result tells you
- ✓ A and AAAA records map a hostname to IPv4 and IPv6 addresses.
- ✓ MX records identify mail servers.
- ✓ TXT records commonly hold verification, SPF and other policy data.
How to verify it
- Compare the answer with your DNS provider dashboard.
- Check authoritative nameservers when propagation is uncertain.
- Allow for TTL and resolver caching after a change.
Network diagnostics
Interpret results in the correct protocol layer
Network tools observe different layers: DNS resolves names, TCP establishes connections, TLS authenticates encrypted sessions and HTTP carries requests, redirects, headers and caching rules. A successful result at one layer does not prove that the complete website or application is healthy.
TLS
Certificate validity, hostname matching, trust chains and protocol support are separate checks.
HTTP
Status codes, redirect chains, headers and caching directives describe application behaviour.
Measurement context
Latency and reachability vary by location, network path, browser and time.
What the operation can change
- A cached DNS answer may differ from an authoritative nameserver response.
- A 200 status code can still return the wrong content or an application error page.
- A valid certificate does not prove the website itself is trustworthy.
- Security-header tools report configuration, not complete vulnerability coverage.
Domain-specific verification
- Repeat tests from another network or resolver when location matters.
- Check the final URL and every redirect hop.
- Confirm timestamps, certificate names and expiry dates.
- Use browser developer tools and server logs for production incidents.
Common mistakes to avoid
- • Expecting DNS changes to appear everywhere immediately.
- • Checking only one record type.
- • Assuming a successful lookup proves the web application is healthy.
Privacy and safe use
The queried hostname is sent to a DNS lookup service. Do not enter confidential internal hostnames unless disclosure is acceptable.
Limitations
- • Results can differ between resolvers because of caching and geography.
- • A DNS answer does not verify that the destination service is reachable or secure.
Continue the diagnostic workflow
Combine related checks instead of relying on one isolated result.
Related Network & Web Tools
Frequently asked questions
What is an A record?
An A record maps a hostname to an IPv4 address.
What is an AAAA record?
An AAAA record maps a hostname to an IPv6 address.
What is an MX record?
MX records identify mail servers and their priority for a domain.
Why do DNS changes take time?
Resolvers cache records according to TTL and may not refresh at the same moment.
Can this test DNS propagation worldwide?
No. This version uses the resolver available to the serverless function, not a global resolver network.
Does the lookup modify DNS?
No. It only reads public DNS records.