A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, SRV and more - read live from authoritative resolvers, not from a cache.
Built for the moment something is not resolving and you need to see the actual records rather than guess at them.
A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, SRV, PTR, DS and DNSKEY in a single query, rather than one lookup per record type.
Answers come straight from Google DNS over HTTPS and Cloudflare DoH, so what you see is what resolvers are serving right now.
Copy any individual record value in one click, which is what you want when auditing, migrating or documenting a zone.
The types this tool returns, in plain language.
| Type | Name | What it is for |
|---|---|---|
| A | Address record (IPv4) | Maps a domain to an IPv4 address. The most fundamental record, and what points your domain at a web server. |
| AAAA | IPv6 address record | Maps a domain to an IPv6 address, used for dual-stack connectivity alongside A records. |
| MX | Mail exchange record | Names the mail servers that receive email for your domain. Priority values decide the order they are tried in. |
| NS | Nameserver record | Identifies the authoritative DNS servers for your domain. Set at your registrar, and they control everything else. |
| TXT | Text record | Arbitrary text. Used for SPF, DKIM and DMARC email authentication, domain ownership verification and service configuration. |
| CNAME | Canonical name record | An alias from one domain to another. Commonly used for www, CDN endpoints and third-party services. |
If your records look wrong and you cannot see why, open a chat and we will look with you.
It queries authoritative DNS servers for every configuration record attached to a domain - IP addresses, mail servers, nameservers, SPF records, CAA records and more.
Not every domain uses every type. A domain without IPv6 has no AAAA records, and one behind a CDN may have no SRV record. Empty simply means not configured.
This shows what records exist, from one authoritative resolver. A propagation check shows whether your changes have reached DNS servers worldwide. Use both.
Time To Live - how many seconds a resolver should cache a record before asking again. Shorter TTLs propagate changes faster; longer ones cut query load.
Yes. Enter any fully qualified name, such as mail.example.com or api.example.com.
