Tool StudioLook up DNS records and reverse DNS (PTR) lookups for any domain or IP
Enter a domain or IP
e.g. example.com, or an IP address like 8.8.8.8 for reverse DNS.
Look it up
All 10 record types are checked at once, automatically.
View the results
See every matching record with its TTL.
Enter a domain to see its current DNS records — A, AAAA, CNAME, MX, NS, TXT, CAA, SOA, SRV, and PTR — all ten types queried at once, in parallel, rather than one at a time. Each query runs live against Cloudflare's public DNS-over-HTTPS resolver, automatically falling back to Google's if Cloudflare is unreachable on your network, so one resolver being blocked doesn't take the whole tool down. Every matching record shows its TTL (how long it's cached before resolvers re-check it) alongside its value. This checks one resolver's live view of a domain, not a multi-location propagation scan across many regions — useful for confirming a DNS change took effect from your own network's perspective, verifying mail or SSL configuration, or understanding what a domain is actually pointing to right now. Nothing you look up is sent to or stored on our own servers.
A maps a domain to an IPv4 address; AAAA does the same for IPv6. CNAME points a domain to another domain name instead of an IP directly (an alias). MX lists the mail servers responsible for a domain's email. TXT holds arbitrary text, commonly used for domain ownership verification, SPF, or DKIM email security. NS lists the authoritative name servers that actually answer DNS queries for the domain. CAA specifies which Certificate Authorities are allowed to issue SSL certificates for it. SOA (Start of Authority) holds the zone's primary name server, admin contact, and refresh/retry/expire timing. SRV points to the host and port for a specific service instead of a plain domain-to-IP mapping. PTR is reverse DNS — it maps an IP address back to a domain name, and is normally only set on reverse-zone (in-addr.arpa) names, not on ordinary domains.
No — this queries a single public resolver (Cloudflare, falling back to Google if that fails), which is what most lookup tools do. True propagation checking needs many geographic vantage points, which this tool doesn't attempt.
The domain may not have that record type set, or may not exist at all — try a different record type or double-check the spelling.
Some networks, VPNs, schools, and workplaces deliberately block DNS-over-HTTPS traffic. Try a different network, or use your operating system's built-in nslookup/dig command instead.
Time To Live — how many seconds a DNS resolver is allowed to cache a record before it has to ask again. A record with a 3600s TTL won't be re-checked by a resolver that already cached it for up to an hour, even if you change it in the meantime.
It depends heavily on TTL — a record with a 300-second TTL can be fully visible everywhere within minutes of a change, while one with a 24-hour TTL can take up to that long for every resolver's cache to expire and pick up the new value. 24-48 hours is a safe general expectation for a typical change.
The previous record is likely still cached somewhere with time left on its TTL — DNS changes aren't instant everywhere at once, they roll out gradually as each resolver's cache expires and re-queries.
Same underlying idea — querying DNS records for a domain — but nslookup and dig run locally on your machine against whatever resolver your OS or network is configured to use, while this queries a public resolver (Cloudflare, falling back to Google) directly from your browser, with no installation and no terminal needed.
PTR records answer a different question — "what domain does this IP resolve to?" — and are set on the IP's reverse-zone (in-addr.arpa) entry, not on the domain name itself. Looking up PTR for a regular domain like example.com correctly returns nothing; you'd look up PTR for the IP address instead.
It points clients to the specific host and port running a particular service — common for things like SIP (VoIP) or XMPP (chat) — rather than just resolving a domain to a plain IP address the way an A record does.
It marks the zone's Start of Authority — the primary name server, the admin's contact address, and timing values (refresh, retry, expire) that tell secondary name servers how to stay in sync. It's more relevant to whoever manages the DNS zone than to everyday troubleshooting.
Yes — enter the full subdomain (like mail.example.com) exactly as you would the main domain, and it's queried the same way.
No — TTL only controls DNS caching behavior, not how fast your site loads once a visitor's browser already has the IP address. A lower TTL means DNS changes take effect faster, at the cost of slightly more DNS query traffic overall.
Each tool queries its own resolver (or a specific set of them), and different resolvers can have cached a record at different times — especially right after a DNS change, before every cache has expired and refreshed. This is normal during the propagation window, not a sign either tool is wrong.
Cloudflare's DNS-over-HTTPS resolver first, falling back automatically to Google's if Cloudflare's is unreachable on your specific network — the same two providers many DNS tools rely on for their speed and reliability.
Yes — confirming your current A, MX, and NS records first gives you a clear baseline to compare against once you've made the switch, so you can tell right away whether the new configuration actually took effect.
No — WHOIS looks up who registered a domain and when; a DNS lookup like this one shows what a domain's DNS records currently resolve to. Both are useful for domain research, but they answer different questions.
Yes — type a plain IP address like 8.8.8.8 and the PTR record type automatically queries the correct reverse-lookup name for it, so there's no need to construct the in-addr.arpa format yourself.
See your browser name and version, rendering engine, operating system, and full user-agent string, along with language, viewport, and cookie settings. Free, works entirely in your browser.
See your screen resolution, browser viewport size, device pixel ratio, and estimated DPI, live. Free, works entirely in your browser.
Instantly see your public IP address. Detects IPv4 or IPv6, one-click copy. Free, no sign-up, no tracking beyond what your connection already reveals.
Test your internet connection speed instantly — ping, download, and upload, all measured live in your browser. No app install, no sign-up. Free, unlimited use.
Checks A, AAAA, CNAME, MX, NS, TXT, CAA, SOA, SRV, and PTR records all at once, against a single public resolver. Enter a domain to look up its records, or an IP address to automatically run a reverse DNS lookup for it — this is a DNS lookup, not a global propagation check across multiple locations. More on what each record type means in the FAQs below.