DNS Lookup
Look up A, AAAA, MX, TXT and NS records for any domain, straight from your browser. Fast, raw answers with TTLs.
Look up DNS records
Enter a domain and pick a record type. The query runs live against a public DNS-over-HTTPS resolver.
Results will appear here.
How this DNS lookup works
Every time you visit a website, your device first asks the domain name
system to translate a human name like example.com
into a machine address. This tool makes that same request on demand. It
sends a DNS-over-HTTPS query to a public resolver and prints the answer
exactly as it comes back — record type, value and the TTL (time to live)
that tells caches how long to keep it. Because the lookup runs in your
browser, your search never touches our servers.
How to read the results
| Record | What it tells you |
|---|---|
| A | IPv4 address the name resolves to. |
| AAAA | IPv6 address — useful for checking IPv6 readiness. |
| MX | Mail servers, with a priority number (lower is preferred). |
| TXT | Text records: SPF, DKIM, domain verification and more. |
| NS | Authoritative nameservers responsible for the zone. |
A high TTL means a record is cached for a long time, so changes take a while to appear everywhere. If a value looks wrong right after an edit, it is usually a caching delay rather than a real error — confirm with the propagation checker.
Frequently asked questions
What is a DNS lookup?
A DNS lookup asks the domain name system which records a name has — for example the A record that maps example.com to an IPv4 address. This tool queries a public DNS-over-HTTPS resolver from your browser and shows the raw answer.
What do A, AAAA, MX, TXT and NS records mean?
A points a name to an IPv4 address, AAAA to an IPv6 address, MX lists the mail servers for a domain, TXT holds free-form text (often SPF, DKIM or verification strings), and NS names the authoritative nameservers for the zone.
Why are my results different from another tool?
Different resolvers cache records for different lengths of time (the TTL), and recent changes may not have propagated everywhere. If a record looks stale, check it again after the TTL expires or use the propagation checker.
Is this lookup done from my computer?
Yes. The query runs in your browser against Google's public DNS-over-HTTPS endpoint, so no record passes through our servers. The resolver you query may sit in a different location than you, which can affect geo-based answers.
Records look right, connection still feels wrong?
DNS is only one layer. If pages load slowly or calls drop even though the records resolve, run the full check-up — it tests speed, latency, jitter and DNS together, then tells you what to fix.