DNS Lookup: All Record Types, TTLs & 3 Resolvers
Look up A, AAAA, MX, TXT, CNAME, NS, SOA, CAA, SRV and PTR records
Check DNS records in one query
A DNS lookup asks the Domain Name System what it holds for a name: which IP addresses it points to, where its mail goes, which servers are authoritative for it and what verification strings it publishes. This tool works like nslookup or dig online — type a domain, choose a record type (or All types), choose a resolver, and you get a table of every answer with its TTL, plus the raw JSON and a copy-as-zone-file button.
Supported record types are A (IPv4 address), AAAA (IPv6 address), CNAME (alias to another name), MX (mail servers with priority), TXT (free text — SPF, DKIM, domain-verification tokens), NS (authoritative nameservers), SOA (zone serial and timers), CAA (which certificate authorities may issue for the domain), SRV (service records such as _sip._tcp.example.com) and PTR (reverse records — enter an IP address). "All types" runs every query in parallel rather than sending an ANY query, because most public resolvers now refuse ANY under RFC 8482 and return almost nothing.
The lookup runs on our server, not in your browser, using Node.js's DNS resolver pointed at the resolver you pick: Cloudflare (1.1.1.1), Google Public DNS (8.8.8.8) or Quad9 (9.9.9.9). Those are recursive resolvers, so the answer you see is what an ordinary user of that resolver would get — including cached answers. The name you query is sent to that resolver; we don't store it. For A and AAAA records the table shows the remaining TTL, which counts down while an answer sits in the resolver's cache. For SOA the minimum TTL governs how long a "no such record" answer is cached.
DNS propagation: what this checker can and can't tell you
"DNS propagation" is really cache expiry. When you change a record at your DNS host, the authoritative servers update almost immediately, but every resolver that already cached the old answer keeps serving it until its TTL runs out. That is why a change can be visible in one place and not another for minutes or hours.
This DNS checker queries from one location — our server — so it is not a worldwide propagation map. What it can do is show you three of the largest public resolvers side by side: switch the resolver drop-down and re-run. If Cloudflare shows the new IP and Google still shows the old one, Google's cache hasn't expired yet; the TTL column tells you roughly how long is left. If all three agree, most of the internet will follow shortly. If none shows your change, check the NS records first — a surprising number of "propagation" problems are edits made at a registrar or DNS provider that isn't actually authoritative for the domain.
A few common checks: a TXT record lookup confirms a Google Search Console, Microsoft 365 or SSL validation token is live; a CNAME lookup verifies that www or a custom subdomain points at your hosting platform; an NS lookup shows which provider controls the zone; an A record lookup confirms which server a domain resolves to before you migrate. For mail-specific checks — MX priorities with SPF and DMARC — use the MX lookup tool, and for IP-to-hostname queries use reverse DNS lookup.
How to use the DNS Lookup: All Record Types, TTLs & 3 Resolvers tool
- 1
Enter a domain
Type a domain or subdomain such as example.com or _sip._tcp.example.com. Enter an IP address to get its PTR record.
- 2
Pick a record type and resolver
Choose a single type or All types, then Cloudflare 1.1.1.1, Google 8.8.8.8 or Quad9 9.9.9.9.
- 3
Run the lookup
Press Lookup (or Enter). Each record is listed with its value and TTL where the resolver provides one.
- 4
Compare or share
Switch resolvers to compare cached answers, copy the result as zone-file lines, or copy a permalink that re-runs the lookup.
Frequently asked questions
Is this the same as nslookup or dig?
It answers the same questions: our server sends standard DNS queries to the resolver you choose and shows the answers in a table. It doesn't do iterative tracing from the root like dig +trace, but you can query NS and SOA to see who is authoritative.
Can it check DNS propagation worldwide?
Not worldwide. Queries come from one server location. You can compare Cloudflare, Google and Quad9 — three of the busiest public resolvers — and use the TTL to estimate when cached answers will expire.
Why does a record show no TTL?
Node's resolver only exposes TTLs for A and AAAA answers. Other record types still return correct values; the SOA record's minimum TTL tells you how long negative answers are cached.
Why don't you use an ANY query for All types?
Most public resolvers return a minimal or empty response to ANY (RFC 8482), so the tool runs each record type in parallel instead, which gives complete results.
Is my lookup logged?
The domain is sent to the resolver you choose to answer the query. Our tool doesn't store it; requests are rate-limited per IP address to prevent abuse.
Related on TechLogHub
Related Network Tools
cURL to Fetch Converter
Convert cURL commands to JavaScript fetch() calls instantly
cURL to Axios Converter
Convert cURL commands to Axios request code in seconds
Test API Online: REST Client with cURL Export
Send HTTP requests to CORS-enabled APIs from your browser and copy them as cURL
Mock REST API with Fake Users, Posts and Todos
Free fake REST API with users, posts, todos, comments and products for testing
HTTP Headers Viewer
View HTTP response headers for any URL
User-Agent Parser
Parse and decode user-agent strings
Get the next tool before you need it
One email a week: new and trending developer tools, fresh comparisons, and what shipped. Unsubscribe in one click.