An IP address runs a reverse DNS (PTR) lookup.
How to use
Enter a domain, URL or IP
Type example.com or a deeper name like mail.example.com. A full URL works too, because the protocol, path and port are removed. An IP address such as 8.8.8.8 runs a reverse DNS lookup.
Pick records and a resolver
Keep All common records or choose one type, then pick a resolver from the list. Add a DKIM selector if you know it. Press Lookup and the queries run in parallel.
Read, copy or export
Check the DNSSEC badge and the email panel, then the records with their TTLs. Copy one value, copy all, download CSV or TXT, or open the matching dig and nslookup commands.
Why DNS Lookup
- Query A, AAAA, CNAME, MX, TXT, NS, SOA, SRV and CAA at once, or pick one of 15 record types.
- Choose the resolver: Google, Cloudflare, Quad9, OpenDNS and more, or our own server.
- TTL for every record, DNSSEC status, and SPF, DMARC and DKIM checks for email.
- Enter an IP address for a reverse (PTR) lookup. Export everything as CSV or text.
DNS record types and what they do
These are the nine types in All common records mode, plus three more you can pick one at a time, with what each one controls and the kind of value you will see. Most problems with websites and email come down to one of the first five.
| Type | What it does | Example value |
|---|---|---|
| A | Points a name to an IPv4 address | 203.0.113.10 |
| AAAA | Points a name to an IPv6 address | 2001:db8::10 |
| CNAME | Makes a name an alias of another name | shop.example.com to shops.myshopify.com |
| MX | Names the servers that receive email, with priority | 10 mail.example.com |
| TXT | Free text for SPF, DMARC and ownership checks | v=spf1 include:_spf.google.com ~all |
| NS | Lists the nameservers that answer for the zone | ns1.example-dns.com |
| SOA | Zone settings: primary server, admin email, serial, timers | ns1.example-dns.com hostmaster 2024010101 |
| SRV | Points a service to a host and port | 10 5 5060 sip.example.com |
| CAA | Says which certificate authorities may issue SSL certificates | 0 issue "letsencrypt.org" |
| PTR | Reverse DNS: maps an IP address back to a hostname | 8.8.8.8 to dns.google |
| DS | DNSSEC link stored in the parent zone | 2371 13 2 1F987CC6... |
| DNSKEY | The zone's DNSSEC public keys | 257 3 13 mdsswUyr... |
The same checks with dig and nslookup
If you prefer a terminal, these commands run the same queries, and the tool shows the matching dig and nslookup lines under every result. dig ships with macOS and most Linux systems, and nslookup is built into Windows, macOS and Linux. Adding +short to dig prints only the values. Querying a public resolver such as 8.8.8.8 or 1.1.1.1 directly shows whether your change has reached it, which helps when your own ISP's cache is still serving the old record. To see the answer straight from the source, query one of the domain's own nameservers, which you can find with the NS lookup.
- A record: dig example.com A +short
- MX records: dig example.com MX +short, or nslookup -type=MX example.com
- TXT and SPF: dig example.com TXT +short
- DMARC: dig _dmarc.example.com TXT +short
- Nameservers: dig example.com NS +short
- Ask a specific resolver: dig @1.1.1.1 example.com A
- Reverse lookup of an IP: dig -x 203.0.113.10 +short