Reverse DNS

Reverse DNS lookup

Input

Resolve an IP address back to its hostname (PTR record). Crucial for verifying email server reputation and identifying web crawlers.

Terminal

Console ready. Execute a command to see output...

About Reverse DNS

Backwards Compatibility

Most DNS looks up Name -> IP. Reverse DNS (rDNS) looks up IP -> Name. This relies on PTR (Pointer) records.

Why it matters?

  • Email Security: Mail servers often reject emails from IPs without a valid PTR record.
  • Logging: Web servers use rDNS to log "googlebot.com" instead of a raw IP.
  • Network Verification: Verify that an IP truly belongs to the ISP it claims.

How to use Reverse DNS

  1. Enter an IP
    IPv4 (1.2.3.4) or IPv6. No domain names here, use DNS Lookup for that.
  2. Hit Lookup
    The PTR query runs from our server, bypassing your browser and OS cache.
  3. Read the result
    Each line is one PTR record. Most IPs return a single hostname, some return none, some return a generic ISP-style name.
  4. Cross-check
    Use Whois to confirm the IP owner, or IP Geolocation for the location and ASN.

Frequently Asked Questions

Mail servers often refuse mail from IPs without a valid PTR (or one that doesn't match the sender's domain), because legitimate mail infrastructure tends to have one and most spam does not. Server admins also use rDNS to identify crawlers (a hit from 66.249.x.x resolving to *.googlebot.com is the real Googlebot) and to humanize log entries. For everyday browsing the PTR is irrelevant.