Reverse IP Lookup

Enter an IP address to perform a reverse DNS (PTR) lookup and find its associated hostname. Useful for server identification, email deliverability audits, and network investigations.

Reverse IP Lookup
Copy

Forward DNS vs Reverse DNS

Most people are familiar with forward DNS — the process of resolving a domain name like example.com to an IP address like 93.184.216.34. Reverse DNS works in the opposite direction: given an IP address, it returns the associated hostname by querying PTR records stored in special reverse-DNS zones (under the in-addr.arpa domain for IPv4).

Why Reverse DNS Matters for Email Deliverability

When an email server receives a message, it often checks whether the sending server's IP address has a valid PTR record — and whether that PTR record points back to the sending server's hostname (a check called forward-confirmed reverse DNS, or FCrDNS). Mail servers without valid PTR records are frequently rejected or routed to spam folders. If you run a mail server, configuring rDNS is one of the most important email deliverability steps you can take.

Use Cases for Reverse IP Lookup

  • Email deliverability — verify your mail server IP has a matching PTR record
  • Server identification — identify the hostname of an unknown IP in network logs
  • Security investigation — trace the hostname behind a suspicious connection or attack source IP
  • ISP verification — confirm which hosting provider or ISP owns a particular IP block

Related Tools

Frequently Asked Questions

A reverse IP lookup performs a PTR DNS query to find the hostname mapped to an IP address. It is the inverse of a regular DNS lookup, which resolves a hostname to an IP.

Email servers verify that sending IPs have PTR records matching their hostname. Missing or mismatched PTR records often cause email to be flagged as spam or rejected outright. Correct rDNS configuration is a key email deliverability factor.