A reverse DNS lookup determines the hostname associated with a specific IP address by querying Pointer (PTR) records stored in the Domain Name System. This free online utility queries global name servers to reveal the domain identity tied to any IPv4 or IPv6 address along with network and country details.
What is it
Reverse DNS is the inverse of standard forward DNS. While forward DNS translates human-readable hostnames like example.com into machine-readable IP addresses, reverse DNS translates an IP address back into a hostname using PTR records. Because standard IPv4 addresses are written in dotted-decimal notation, reverse DNS queries them by reversing the octets and appending a special top-level domain: in-addr.arpa. For example, the IP address 192.0.2.1 is queried as 1.2.0.192.in-addr.arpa. IPv6 addresses use a similarly inverted structure under the ip6.arpa domain. When you perform a lookup, the authoritative name server for that IP block responds with the assigned PTR record, identifying the server, gateway, or mail exchanger configured on the network.
Why it matters
Reverse DNS plays a critical role in email deliverability, network security auditing, and server administration. Email service providers routinely perform reverse DNS checks on incoming mail servers to verify that the connecting IP address resolves to a valid hostname. If the PTR record is missing, or if the hostname does not match the forward DNS record in a process called Forward-Confirmed reverse DNS (FCrDNS), receiving mail servers often mark the email as spam or reject it outright. Network administrators also rely on reverse DNS during log analysis and incident response. Seeing a raw IP address in a firewall or web server log provides little context, but a properly configured PTR record immediately identifies the origin, such as crawl-66-249-66-1.googlebot.com, making troubleshooting significantly faster.
How to use this tool
- Locate the input field on the Reverse DNS Lookup tool page.
- Enter the target IPv4 or IPv6 address you want to investigate.
- Press the Check button to initiate the lookup against global DNS servers.
- Review the returned PTR record, associated network details, and geolocation data.
How to read the results
When you query an IP address, the tool displays several key pieces of information to help you understand the network identity. Suppose you run a lookup for 93.184.216.34, which is the IP address for example.com.
- IP Address: Displays the exact IPv4 or IPv6 address you queried, confirming your input. For our example, it shows
93.184.216.34. - Hostname (PTR Record): Shows the domain name returned by the pointer record. A successful result might display
93-184-216-34.example.comor a generic hosting provider hostname. If no record exists, this field will remain blank or return a lookup error. - Network/CIDR: Displays the IP block or autonomous system associated with the address, indicating which organization manages the routing space.
- Country: Shows the geographical location of the IP address based on regional internet registry data, such as
United States.
Common problems and how to fix them
NXDOMAIN or No PTR Record Found
If the tool returns an error stating that no PTR record exists, it means the organization that owns the IP address has not configured a reverse DNS zone for it. If you own the IP address, you must contact your hosting provider, data center, or ISP to add the PTR record, as end-users typically cannot configure reverse DNS for public IP blocks themselves.
Forward-Confirmed Reverse DNS Mismatch
If mail servers reject your outgoing emails despite having a PTR record, you likely have a mismatch between your forward and reverse DNS. The PTR record must point to a hostname, and that same hostname must resolve back to the exact same IP address via an A or AAAA record. Ensure your DNS zone contains a matching record:
; Forward DNS
mail.example.com. IN A 192.0.2.25
; Reverse DNS (Managed by your ISP)
25.2.0.192.in-addr.arpa. IN PTR mail.example.com.
Delayed DNS Propagation
If you recently updated your PTR record with your hosting provider and the tool still shows old information, you are likely seeing the effects of DNS caching. PTR records utilize Time-to-Live (TTL) values, and resolvers across the internet may cache the previous result until the TTL expires.
Best practices
Always maintain valid and descriptive PTR records for any server that sends outbound emails, hosts public web applications, or runs network services. Ensure that your reverse DNS hostnames follow a professional naming convention rather than leaving them as default provider strings. Regularly audit your infrastructure by performing reverse DNS checks to verify that your IP addresses correctly map to your active domain names, preventing unexpected email delivery failures and security alert flags.