Domain & DNS
DNS record lookup
Query A, AAAA, MX, TXT, NS, CNAME and SOA records.
Domain or IP
Enter a domain. For PTR choose it as the only type and enter an IP.
About this tool
A DNS lookup asks an authoritative or recursive resolver what records a domain publishes. Our tool runs a live query against Google, Cloudflare, or Quad9 and shows you every record with its TTL — the same data dig prints on the command line, formatted for quick scanning.
You can pull the common record types on a single page: A and AAAA for hosts, MX for mail routing, TXT for SPF/DKIM/verification strings, NS for delegation, SOA for zone metadata, plus CNAME, SRV, CAA, and reverse PTR. Pick only the types you need to keep the answer compact.
When to use this tool
- After a DNS change. Query multiple resolvers to confirm a new record is live before pointing traffic at it.
- Debugging email deliverability. Inspect
MX,SPF,DKIM, andDMARCrecords in one pass. - Verifying ownership. Pull the
TXTrecord a third-party service asked you to publish. - Reverse DNS. Run a
PTRquery on an IP to find the hostname a mail server or logger will attribute to it.
Why you may see different answers
Public resolvers cache records for the TTL you configured at your authoritative nameserver. Google may still serve the old value while Cloudflare already shows the new one. Switch the resolver to compare — the TTL column tells you when the cache will expire. For a global view across 20+ vantage points, see the propagation check linked below.Frequently asked questions
Which DNS resolver should I use?
All three (Google 8.8.8.8, Cloudflare 1.1.1.1, Quad9 9.9.9.9) are public, anycasted, and return authoritative-sourced answers. Cloudflare tends to be the fastest; Quad9 filters known-malicious names; Google has the most predictable behaviour across regions. Switch between them to see whether an issue is global or resolver-specific.
What is the TTL column?
Time-to-live in seconds — how long a downstream resolver is allowed to cache this record. A low TTL (60–300s) means changes propagate quickly; a high TTL (3600–86400s) means the record is stable. If you are about to change a record, lower its TTL first and wait for the old TTL to elapse before cutting over.
Do you query the authoritative nameserver directly?
No — we query the public resolver you select, the same way a browser or mail server would. That is usually what you want: it matches what the rest of the internet sees. If you need to verify what the authoritative server currently publishes, use a
+norecurse dig or a hosting-specific tool.
Why do PTR records look different?
A PTR lookup resolves an IP back to a hostname and uses the
.in-addr.arpa (IPv4) or .ip6.arpa (IPv6) reverse zone. To avoid mixing record types that live in different zones, pick PTR on its own and enter an IP address instead of a domain.
Is the result cached?
We cache resolver answers for five minutes so repeated lookups against the same domain and resolver do not waste upstream query budget. If you need to force a fresh query, switch the resolver or wait out the five-minute window. Authoritative TTLs are reported unchanged — our cache only affects how often our backend re-queries.