DNS Lookup queries live DNS records for a hostname and selected record type. DNS resolution is a distributed lookup process in which recursive resolvers ask authoritative nameservers for records such as A, AAAA, CNAME, MX, TXT, NS, or CAA. Different record types answer different operational questions: address records route web traffic, MX records route mail, TXT records often prove ownership or define email policy, and NS records identify the authoritative servers for a zone. Results can differ by resolver because of caching, TTL, split-horizon DNS, or recent changes. This tool is useful for troubleshooting and documentation, but authoritative nameserver checks are best when confirming production truth.
Enter values in the left panel, keep units explicit, run the calculation, then copy or share the result. Invalid fields are highlighted immediately.
How to use this tool
Enter the hostname you want to check, such as example.com or mail.example.com.
Choose the record type: A, AAAA, CNAME, MX, TXT, NS, CAA, or another supported type.
Run the lookup and review returned values, errors, or empty answers.
Compare recursive lookup results with your DNS provider or authoritative nameserver before making a production change.
DNS Lookup
Result
Enter a host like example.com, then choose the record type you want to query.
Formula or method
A records map a hostname to IPv4 addresses.
AAAA records map a hostname to IPv6 addresses.
CNAME records alias one hostname to another canonical hostname.
MX records identify mail exchangers for a domain.
TXT records are often used for SPF, DKIM, DMARC, ownership verification, and service configuration.
NS records identify the authoritative nameservers for a zone.
Worked example
Checking email DNS before a cutover
Host: example.com
Record type: MX
Result: The lookup returns the mail exchanger hostnames visible to the resolver.
If the expected mail host is missing, check authoritative DNS, TTL, provider settings, and whether old records are still cached.
How to interpret the result
DNS answers are resolver-visible facts at a point in time. Use them to narrow the failure mode, then verify authoritative nameserver data before production changes.
A successful answer means the resolver returned a record, not that every user sees the same answer.
TTL controls how long resolvers may cache an answer, so recent changes can appear inconsistent.
Empty results can mean the record does not exist, the name is wrong, or a resolver could not reach the authoritative path.
For production truth, compare recursive resolver results with authoritative nameserver data from your DNS provider.
Common mistakes
Checking the apex domain when the record actually lives on a subdomain.
Expecting DNS propagation to be instant after a record change.
Confusing CNAME aliases with final A or AAAA address answers.
Treating one public resolver's answer as proof that every client will see the same value.
Formula References
IPv4/IPv6 addressing rules and common protocol arithmetic.
DNS/WHOIS/network calls depend on external resolvers and current network state.
Assumptions
The requested hostname and record type are correct.
The lookup path may use recursive resolver cache rather than querying the authoritative source directly.
Review note and limitations
Method - live DNS resolver lookup; results depend on resolver behavior, TTL, caching, and current network conditions.
Resolver cache, TTL, DNSSEC errors, split-horizon DNS, and local network policy can change what different clients see.
Does not replace DNS provider records or authoritative nameserver checks for critical changes.
Diagnostic aid only. Confirm production DNS with authoritative nameservers, provider settings, and current resolver behavior.
FAQ
What DNS record type should I check first?
For web traffic, start with A and AAAA records. For email delivery, start with MX and TXT records. For delegation, check NS records.
Why do DNS lookup results differ between tools?
Different tools may query different recursive resolvers, and each resolver can have different cached answers until TTLs expire.
Does this show authoritative DNS?
It shows the answer available through the lookup path used by the tool. For authoritative truth, compare with your DNS provider or authoritative nameserver.
Explore more versions
Tailored guides for specific audiences, regions, and scenarios.