Reverse DNS Lookup: Find the Domain Behind an IP Address

What Is Reverse DNS Lookup?

A reverse DNS (rDNS) lookup is the inverse of a standard DNS query. Instead of asking "what IP address does this domain name resolve to?", it asks "what domain name is associated with this IP address?" The answer comes from a special type of DNS record called a PTR (Pointer) record.

Regular DNS: example.com → 93.184.216.34
Reverse DNS: 93.184.216.34 → example.com

Reverse DNS uses a special domain structure in the in-addr.arpa namespace. To look up the PTR record for 93.184.216.34, the DNS query is made for 34.216.184.93.in-addr.arpa — note the IP address is reversed. For IPv6 addresses, the ip6.arpa zone is used with a similar reversal.

You can perform a reverse DNS lookup on any IP address using our IP lookup tool. Simply enter any IP to see its associated hostname, ISP, and location data.

How PTR Records Work

PTR records are the foundation of reverse DNS. Unlike A or CNAME records, which are managed by domain owners, PTR records are managed by whoever controls the IP address block — typically your ISP, cloud provider, or data center.

This means if you're running a mail server on a VPS, you don't set the PTR record in your domain's DNS zone. You ask your hosting provider (e.g., Linode, DigitalOcean, Hetzner) to configure the PTR record for your server's IP address in their reverse DNS zone.

Most VPS providers offer self-service PTR record configuration in their control panels. The configuration looks like:

34.216.184.93.in-addr.arpa.  3600  IN  PTR  mail.example.com.

Important: The PTR record's hostname should match (or be consistent with) a forward A record. This is called forward-confirmed reverse DNS (FCrDNS) — the domain in the PTR record should resolve back to the same IP. Many spam filters verify this as part of their email authentication checks.

Why Reverse DNS Matters for Email Deliverability

Email is the domain where reverse DNS matters most. Major mail providers — Gmail, Outlook, Yahoo — use rDNS as one of many signals to evaluate whether an incoming email is legitimate or spam.

A properly configured reverse DNS for your mail server IP signals credibility. Here's what mail servers check:

1. PTR record exists: The sending IP has a PTR record (some mail servers reject connections from IPs with no PTR record).
2. PTR hostname is valid: The PTR record points to a real, resolving hostname (not a generic ISP rDNS like pool-123-45-67-89.dynamic.example.net).
3. Forward-confirmed: The hostname in the PTR record resolves back to the sending IP (FCrDNS).

If you're experiencing email deliverability issues — messages landing in spam or being rejected — a missing or misconfigured PTR record is one of the first things to check. Also verify your SPF, DKIM, and DMARC records are correct, and check your IP's reputation using blocklist lookups.

Use our IP lookup tool to quickly see the rDNS hostname associated with any IP address.

Reverse DNS for Network Diagnostics

Beyond email, reverse DNS is invaluable for network diagnostics. When you run a traceroute or ping, the output typically includes the PTR hostname for each IP hop, making it much easier to identify network paths and pinpoint problem locations.

Compare these traceroute outputs:

Without PTR records:

1  10.0.0.1
2  203.0.113.1
3  198.51.100.45
4  192.0.2.67

With PTR records:

1  router.home (10.0.0.1)
2  ae-1.cr1.lax1.isp.net (203.0.113.1)
3  be-3.cr2.sjc1.isp.net (198.51.100.45)
4  edge1.cloudfront.net (192.0.2.67)

The second output immediately tells you the traffic is going through an ISP's LA and San Jose routers before hitting a CloudFront edge. This information is critical for diagnosing routing anomalies, latency spikes, and outages.

Use our ping tool to test connectivity and latency to any IP address or hostname.

How to Perform a Reverse DNS Lookup

There are several ways to perform a reverse DNS lookup:

Command line — dig:

# Reverse lookup for 1.1.1.1
dig -x 1.1.1.1

# Short answer only
dig -x 1.1.1.1 +short
# Returns: one.one.one.one.

Command line — nslookup:

nslookup 1.1.1.1
# Returns server name and address

Command line — host:

host 8.8.8.8
# 8.8.8.8.in-addr.arpa domain name pointer dns.google.

Online tools: Our IP lookup tool performs rDNS lookups automatically as part of any IP address query.

When interpreting results, keep in mind that not all IPs have PTR records configured. Consumer IP addresses assigned by ISPs often have generic rDNS entries like pool-71-168-38-83.dllstx.fios.verizon.net. Server IPs with custom PTR records pointing to meaningful hostnames are generally more trustworthy from a network administration perspective.

Frequently Asked Questions