Reverse DNS Lookup

What Is Reverse DNS?

Reverse DNS (rDNS) is the inverse of a normal "forward" DNS lookup. A forward query asks "what IP belongs to this hostname?"; reverse asks "what hostname belongs to this IP?" The answer comes from a PTR (pointer) record stored under the special in-addr.arpa (IPv4) or ip6.arpa (IPv6) zones, defined in RFC 1035 and RFC 3596.

Reverse DNS matters most for email: every reputable mail receiver checks whether the sending IP has a valid PTR record before deciding whether the message looks legitimate. Missing or generic PTRs are a direct signal of spam-grade infrastructure. This tool runs the lookup via Cloudflare's DoH resolver — works with both IPv4 and IPv6, no signup required.

How a PTR Record Maps Back to a Hostname

For an IPv4 address, the resolver reverses the octets and appends .in-addr.arpa. The IP 203.0.113.1 becomes the lookup name 1.113.0.203.in-addr.arpa; the resolver asks the authoritative name server for that zone (typically the IP block's owner — your hosting provider or ISP) and returns whatever PTR record is published.

For IPv6, every nibble is reversed and joined with dots, then .ip6.arpa is appended. The IP 2001:db8::1 becomes 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa. This tool handles the conversion automatically — just enter the IP.

Why Reverse DNS Matters for Email

Mail receivers use reverse DNS as a first-line spam signal. The checks include:

• Has a PTR at all. No PTR = greylisted or rejected outright at every major receiver. This is the single most common deliverability issue for self-hosted mail servers.
• Forward-Confirmed Reverse DNS (FCrDNS). Defined in RFC 7001, FCrDNS is the round-trip check: the sending IP's PTR resolves to a hostname, and that hostname's A or AAAA record resolves back to the same IP. Receivers including Gmail, Outlook, and Spamhaus require FCrDNS for trusted inbound mail.
• Generic PTR detection. Receivers flag PTRs that look like ISP-assigned dynamic DNS (e.g. ec2-203-0-113-1.compute-1.amazonaws.com, cpe-203-0-113-1.dyn.example-isp.net) as low-trust. A custom PTR like mail.example.com signals a managed mail server.
• Spamhaus PBL. The Policy Block List flags IP ranges that should not send mail directly — typically residential and dynamic IP space. A generic PTR is the strongest evidence for PBL inclusion.

Pair this lookup with our SPF checker and blacklist check for a full sender-IP audit.

How to Set Up Reverse DNS

Unlike forward DNS, you cannot publish a PTR for an IP you don't own. The authority lives with whoever owns the IP block:

• Cloud providers (AWS, GCP, Azure, DigitalOcean, Hetzner). Configure rDNS in the provider's console — usually a single text field on the IP or instance object. The change applies within minutes.
• Dedicated server providers and colocation. Open a support ticket. Most providers will set rDNS within 24 hours; some offer a self-service portal.
• Owned IP blocks. Run your own authoritative name server for the relevant .in-addr.arpa zone, or delegate the zone to your DNS provider. Most registrars offer rDNS delegation for assigned IPv4 /24s and IPv6 /48s.
• Residential or dynamic IPs. You generally cannot. Use a static IP from a hosting provider, or relay outbound mail through a transactional ESP that owns its sending IPs.

Common Reverse DNS Errors

• No PTR record at all. Most common on freshly provisioned cloud instances and untouched colocation IPs. Receivers treat this as if the sender hadn't bothered to configure their infrastructure.
• Generic auto-generated PTR. The cloud provider's default reverse hostname (e.g. ec2-203-0-113-1.compute-1.amazonaws.com). Override it per-IP to your mail hostname.
• FCrDNS mismatch. Your IP's PTR points at mail.example.com but mail.example.com doesn't have an A record back to the same IP. Common after migrations. Run this lookup, then check the forward record with the DNS lookup.
• PTR for the wrong IP. You configured rDNS for the IP that used to send mail before you migrated to a new outbound IP. The new IP has no PTR.
• IPv6 PTR forgotten. Many operators set up IPv4 PTRs but skip IPv6. Modern receivers (Gmail, Outlook) increasingly require both.

Command-Line Reverse DNS Lookup

• dig (Linux, macOS): dig -x 203.0.113.1 +short
• nslookup: nslookup 203.0.113.1
• host: host 203.0.113.1
• PowerShell: Resolve-DnsName -Name 203.0.113.1 -Type PTR
• ping (Windows / macOS): ping -a 203.0.113.1

FAQ

What does reverse DNS lookup do?

It resolves an IP address back to a hostname using PTR records under the in-addr.arpa (IPv4) or ip6.arpa (IPv6) zones. Mail receivers, security tools, and log analyzers all use reverse DNS to attach human-readable names to IP traffic.

How do I check the reverse DNS of an IP?

Enter the IPv4 or IPv6 address in the field above and click "Lookup." The tool converts the IP to its arpa form, queries Cloudflare's DoH resolver, and returns the PTR record. From the command line, run dig -x 203.0.113.1 +short.

How to do reverse DNS with nslookup?

On any operating system: nslookup 203.0.113.1. nslookup auto-detects an IP literal and switches to PTR mode. The first line of the response shows the PTR target.

What is an example of reverse DNS?

dig -x 8.8.8.8 +short returns dns.google. — Google's public DNS resolver IP maps back to its canonical hostname. That round-trip works because dns.google also has A records pointing at 8.8.8.8 — the FCrDNS check passes.

Why does my IP have no reverse DNS?

Either the owner of the IP block (your cloud provider, ISP, or colocation host) never configured a PTR for that IP, or your configuration didn't propagate yet. New cloud instances default to no PTR or to a generic auto-generated one. Set a custom PTR through your provider's console or a support ticket.

Is reverse DNS the same as a PTR record?

Reverse DNS is the lookup operation; PTR is the record type that stores the answer. Every reverse DNS query returns one or more PTR records (or NXDOMAIN if none exists).