Reverse DNS Lookup (rDNS): What It Is & How to Check It
what reverse DNS lookup is, why it matters for email deliverability and security, and how to perform an rDNS check on any IP address.
What Is Reverse DNS (rDNS)?
Forward DNS translates a domain name (like example.com) into an IP address. Reverse DNS (rDNS) does the opposite – it resolves an IP address back to a domain name via a PTR (Pointer) record.
For example, the IP 192.0.2.1 might reverse resolve to mail.example.com. Not every IP has a PTR record; many consumer IPs do not. But for mail servers and web servers, a correct rDNS entry is critical.
Why Is Reverse DNS Important?
Reverse DNS isn't something most website owners think about daily. However, it plays a vital role in several areas:
1. Email Deliverability (Anti‑Spam)
Most email servers check the sending IP’s rDNS before accepting a message. If an IP lacks a PTR record or its rDNS doesn’t match the domain in the “HELO” greeting, the email is often marked as spam or rejected outright. That’s why outgoing mail servers must have valid rDNS.
2. Security & Forensics
When investigating malicious traffic, logs only show IP addresses. A reverse DNS lookup helps identify the owner or hostname behind an IP – useful for tracking down spammers or attackers.
3. Network Troubleshooting
Tools like traceroute, log analyzers, and firewall reports often display hostnames via rDNS. Having proper PTR records makes logs much more readable.
4. FTP & Authentication Logs
Some FTP servers and security systems perform rDNS lookups to verify client identity before granting access.
How to Perform a Reverse DNS Lookup (Free)
You don’t need special software. Use command line or free online tools:
- Command line (Windows / Mac / Linux):
nslookup 8.8.8.8ordig -x 8.8.8.8 - Online tools: Many websites offer rDNS checks. Enter an IP and get the PTR record.
👉 WebCheckTools doesn’t have a dedicated rDNS tool yet, but you can start with our IP Lookup Tool to get your public IP address and ISP details – then use the command line to check rDNS yourself. Alternatively, bookmark the external resources below.
What a Reverse DNS Lookup Returns
A successful rDNS query returns a PTR record – a hostname associated with the IP. For example:
| IP Address | PTR Record (rDNS) |
|---|---|
| 8.8.8.8 | dns.google |
| 1.1.1.1 | one.one.one.one |
| 208.67.222.222 | resolver2.opendns.com |
If no PTR record exists, the lookup returns “NXDOMAIN” or simply no answer.
Who Sets Up Reverse DNS?
Unlike forward DNS (which you control via your registrar), reverse DNS is managed by the organisation that owns the IP address block – usually your Internet Service Provider (ISP) or hosting provider. To set or change rDNS for your mail server, you must contact your hosting company. Many VPS/dedicated server providers allow you to set rDNS through their control panel.
External Resources for Reverse DNS & Network Tools
For bulk rDNS checks, historical PTR records, and deeper network analysis, these external sites are excellent:
- woorldtv.com – offers batch rDNS lookup and email server testing tools.
- cartpostal.net – provides network diagnostic resources, including PTR record guides.
Frequently Asked Questions (FAQ)
Does rDNS affect my website SEO?
No. Google does not use rDNS for search rankings. It only matters for email delivery and server administration.
How long does it take for rDNS changes to propagate?
Usually a few hours, but sometimes up to 24–48 hours. Unlike forward DNS, many ISPs update PTR records slowly.
Can I use rDNS to identify a person’s location?
Not reliably. rDNS gives a hostname (e.g., host-12-34-56-78.exampleisp.net). That hostname might include city information, but it’s not guaranteed. Use IP geolocation (like our IP Lookup tool) for location.
Why does my home IP not have rDNS?
Consumer broadband IPs rarely have PTR records. ISPs reserve rDNS for business and mail server IPs. It’s normal.
What’s the difference between rDNS and a blacklist check?
rDNS identifies the hostname of an IP. A blacklist check tells you if that IP is flagged for spam. Both are useful for email reputation, but they serve different purposes.
How do I test if my mail server’s rDNS is correct?
Find your mail server’s public IP (e.g., nslookup mail.yourdomain.com), then run reverse lookup on that IP. The result should match your mail server’s hostname. Also, ensure your server’s HELO/EHLO greeting matches the PTR record.
Check Your Own IP’s rDNS
Every website owner or email administrator should verify their reverse DNS at least once. Misconfigured rDNS is a common reason for emails landing in spam.
Start by finding your public IP using our IP Lookup Tool. Then, run a reverse DNS query using nslookup YOUR_IP in your computer’s terminal, or use one of the external resources above. If the PTR record doesn’t match your domain, contact your hosting provider to fix it.
Good rDNS practices build email trust and make your server logs easier to read – a small effort for a big payoff.