Reverse DNS Lookup

Find the hostname associated with any IPv4 or IPv6 address via PTR record lookup

Try:

Frequently Asked Questions

Reverse DNS (rDNS) is the process of resolving an IP address back to a hostname. While standard DNS lookup resolves a domain name to an IP address (forward lookup), reverse DNS does the opposite — it queries a PTR (Pointer) record in the special in-addr.arpa domain (for IPv4) or ip6.arpa (for IPv6) to find the associated hostname.
A PTR (Pointer) record maps an IP address to a domain name. PTR records are stored in the reverse DNS zone and are used by mail servers to verify the identity of sending servers, network diagnostics, and system logging. For example, the IP 8.8.8.8 resolves to dns.google via a PTR record.
Not all IP addresses have PTR records configured. PTR records must be set up by the IP block owner (typically an ISP or hosting provider). Consumer IP addresses often don't have PTR records. Servers and mail servers usually do — mail servers without valid reverse DNS are often flagged as spam.
Forward-confirmed reverse DNS (FCrDNS) is when the hostname resolved via PTR record also resolves back to the same IP via an A record. For example: 8.8.8.8 → dns.google → 8.8.8.8. This confirmation is used by email servers to verify that a server's IP and hostname are consistent, which is a strong spam prevention signal.
Email servers often check the reverse DNS of the connecting server's IP. If the PTR record doesn't exist or doesn't match the sending domain, the email is more likely to be flagged as spam. For email deliverability, it's important that your mail server's IP has a PTR record pointing to a hostname that resolves back to that same IP (FCrDNS).
Yes. This tool supports both IPv4 and IPv6 reverse DNS lookups. For IPv6, the lookup queries the ip6.arpa zone instead of in-addr.arpa. IPv6 PTR records are less commonly configured than IPv4 ones.
An A record maps a hostname to an IP address (forward DNS). A PTR record maps an IP address back to a hostname (reverse DNS). PTR records are stored in the in-addr.arpa zone and managed by the IP block owner (your ISP or hosting provider), not your domain registrar.
Many mail servers perform a reverse DNS check on the IP of any connecting server. If your mail server's IP has no PTR record, or the PTR record does not match the server's hostname, the receiving mail server may reject the email or assign it a high spam score. Gmail, Outlook, and Yahoo Mail all factor reverse DNS into their deliverability decisions.
PTR records are controlled by the owner of the IP block — not your domain registrar. Contact your ISP or hosting provider (DigitalOcean, Hetzner, AWS, etc.). Most cloud providers offer a self-service option under server or network settings (look for "Reverse DNS" or "PTR Record"). Set the PTR value to your mail server's FQDN, then create a matching A record in your DNS zone.
For IPv6, reverse DNS uses the ip6.arpa domain with a nibble format: the full 128-bit address is expanded to 32 hex digits, reversed nibble by nibble, and each digit separated by dots. IPv6 PTR records are less commonly set than IPv4 — even many server operators skip them — but they are equally important for mail deliverability.

About This Reverse DNS Lookup Tool

This free Reverse DNS (rDNS) Lookup tool performs a PTR record lookup for any public IPv4 or IPv6 address. It also attempts a forward confirmation lookup — verifying that the resolved hostname maps back to the original IP. Private, loopback, and reserved IP addresses are blocked for security.

Well-known DNS Server IPs

IPProviderHostname
8.8.8.8Googledns.google
1.1.1.1Cloudflareone.one.one.one
9.9.9.9Quad9dns9.quad9.net
208.67.222.222OpenDNSresolver1.opendns.com

Related Articles

In-depth guides and technical articles.

View all →
Why Reverse DNS Alone Never Confirms or Denies a Threat — Residential Proxies, Reliability Decay, and SOC Triage
No serious threat intelligence platform relies on reverse DNS alone — residential proxy networks now produce PTR records indistinguishable from genuine residential ISP connections, defeating the simple "datacenter IP = higher risk" heuristic. Here's how reverse DNS combines with other signals in IP reputation scoring, why reverse DNS data decays in forensic reliability over weeks and months, and why FCrDNS doesn't protect against attackers who legitimately own a deceptively-named domain.
How to Read a PTR Record Like a Network Investigator — Email Forensics, ISP Naming Patterns, and FCrDNS
A PTR record can say anything — anyone who controls a server can configure their reverse DNS to claim any hostname. FCrDNS (Forward-Confirmed Reverse DNS) verifies authenticity by checking that the PTR hostname resolves back to the original IP. Here's how to read ISP and datacenter naming conventions in PTR records, how reverse DNS reveals email header forgery, and why PTR record changes can indicate BGP hijacking.
Reverse DNS Is an Assertion, Not a Proof — Here's What FCrDNS Actually Verifies
A PTR record saying "mail.example.com" for an IP doesn't prove that IP is operated by example.com — it proves whoever controls the reverse DNS zone for that IP chose to set that name. Here's the fundamental asymmetry between forward and reverse DNS, why "forward-confirmed reverse DNS" (FCrDNS) provides substantially more confidence than PTR alone, how Google uses FCrDNS to verify Googlebot traffic, and when PTR records are legitimately useful for logging even without cryptographic verification.
Reverse DNS for IPv4 vs IPv6: Why ip6.arpa Delegation Works So Differently from in-addr.arpa
IPv4 and IPv6 reverse DNS use the same in-addr.arpa/ip6.arpa concept — but IPv6's vastly larger address space means most addresses simply don't have PTR records, by practical necessity rather than oversight. Here's how each zone's delegation works, who controls PTR record configuration, and why "no PTR record" is a much more common and unremarkable result for IPv6.
IP Geolocation: How It Works, Why City-Level Accuracy Is Unreliable, and the VPN Problem
IP geolocation is 95–99% accurate at country level and 50–80% accurate at city level — and VPN users are always wrong by design. Here's how geolocation databases work, the legitimate business uses, the VPN problem for geo-dependent services, and what an IP lookup actually reveals beyond location.