What the Reverse DNS Lookup does
Reverse DNS (rDNS) is the mirror image of a normal DNS lookup: instead of turning a domain into an IP, it turns an IP address back into a hostname. It works by querying a special PTR record stored under the in-addr.arpa zone.
This is widely used as a trust signal. Mail servers, for example, check that a sending IP has a valid PTR record that matches its forward DNS before accepting mail — a missing or mismatched PTR is a classic reason legitimate email lands in spam.
How to read the results
- A returned hostname (e.g. dns.google) is the PTR record the IP's owner has published for that address.
- 'No PTR record' means the address block owner has not configured reverse DNS — common for residential and dynamic IPs.
- For proper mail setup, this hostname should also resolve forward (via an A record) back to the same IP.
Worked example
Input: 8.8.8.8
dns.google
Google's public DNS resolver at 8.8.8.8 publishes a clean PTR record (dns.google) that also resolves forward to the same IP — exactly the matched setup mail servers look for.
Common use cases
- Troubleshoot email deliverability — many providers require matching forward and reverse DNS.
- Identify the operator or hosting provider behind an unfamiliar IP in your server logs.
- Verify that your own mail server's IP has correct rDNS configured.
- Spot-check whether an IP belongs to a residential ISP or a data centre.