DNS Lookup
Look up A, AAAA, MX, TXT, NS, CAA and other records, from a public resolver or straight from the authoritative nameservers.
What this tool checks
- Records with TTLs for each requested type
- NXDOMAIN, empty answers, SERVFAIL and timeouts reported separately
- CNAME conflicts and records that point at private addresses
- Dangling aliases and possible subdomain takeovers on hosting services
- Optional direct queries to the zone's authoritative nameservers
How to read the results
- Pass
- The check succeeded based on the observed responses.
- Warning
- Works now, but is risky, unusual or worth reviewing.
- Fail
- A problem was observed directly in the responses.
- Inconclusive
- Not enough evidence — for example a server did not respond.
Frequently asked questions
- How do I check the MX records for a domain?
- Enter the domain above; MX is in the default set. Each mail server is listed with its preference number (lower values are tried first) and its TTL. On the command line, run dig example.com MX or nslookup -type=mx example.com.
- How do I look up a domain's TXT records?
- Run a lookup with TXT selected to see every TXT record at the name, including SPF and domain-verification tokens. DMARC and DKIM records live at other names (_dmarc and selector._domainkey), so check those with the SPF, DKIM & DMARC Checker.
- Is this the same as nslookup or dig?
- It answers the same questions without a terminal. Like dig, it can ask a public resolver such as 1.1.1.1 or go straight to the domain's authoritative nameservers, and it explains NXDOMAIN, empty answers and SERVFAIL instead of just printing them.
- Why does a DNS lookup still show my old record?
- Public resolvers keep a cached answer until its TTL runs out. Choose "Authoritative nameservers" as the source to see what your DNS provider serves now; if that is correct, the rest is caching and clears on its own.