Reverse DNS translates an IP address back to a hostname, the opposite of a standard forward DNS lookup. This mapping is stored in PTR (Pointer) records and plays a critical role in email deliverability. Mail servers that lack properly configured reverse DNS are routinely rejected or flagged as spam by every major inbox provider. Our free rDNS lookup tool checks the PTR record for any IPv4 or IPv6 address and validates forward-confirmed reverse DNS (FCrDNS).
How Reverse DNS Works
In forward DNS, you query a hostname and receive an IP address. In reverse DNS, you query an IP address and receive a hostname. This is accomplished through a special DNS zone: for IPv4, the address octets are reversed and appended to the in-addr.arpa domain. For example, looking up 192.0.2.1 translates to a query for 1.2.0.192.in-addr.arpa. IPv6 reverse DNS uses the ip6.arpa domain with each nibble expanded and reversed.
The PTR record returned must then resolve back to the original IP address via a forward A or AAAA lookup. This bidirectional confirmation is called forward-confirmed reverse DNS (FCrDNS) and is the standard that mail servers check.
Why rDNS Matters for Email Deliverability
RFC 1912 recommends that every internet-accessible host have a PTR record. For email infrastructure, this is not merely a recommendation; it is a practical requirement.
Gmail
Google's mail servers explicitly check for valid rDNS on connecting IPs. Messages from IPs without PTR records or with generic ISP hostnames (like 192-0-2-1.isp.example.net) receive a significant spam score penalty. Gmail's postmaster guidelines state that sending IPs should have valid reverse DNS entries that match the sending domain.
Microsoft Outlook
Outlook.com and Exchange Online Protection perform rDNS checks as part of their connection filtering. IPs without PTR records may be rejected at the SMTP connection level before the message content is even evaluated.
Yahoo
Yahoo Mail similarly validates rDNS as part of its anti-spam pipeline. Failed rDNS checks contribute to overall sender reputation scoring and can trigger temporary deferrals or permanent rejections.
What This Tool Checks
Enter an IPv4 or IPv6 address, and the tool performs the following checks:
- PTR Record Query. Retrieves the PTR record from the appropriate
in-addr.arpaorip6.arpazone. - Forward Confirmation. Resolves the returned hostname back to an IP address and verifies it matches the original query.
- Hostname Analysis. Evaluates whether the PTR hostname appears to be a generic ISP assignment or a properly configured mail server hostname.
- IP Reputation Cross-Reference. Links to the IP Reputation tool for a complete reputation assessment of the address.
Interpreting Your Results
Valid FCrDNS. The PTR record exists and the hostname resolves back to the queried IP. This is the ideal configuration for any mail-sending IP.
PTR exists but forward lookup fails. The reverse record points to a hostname that does not resolve back to the original IP. This is a misconfiguration that many mail servers treat as equivalent to having no rDNS at all.
No PTR record. The IP has no reverse DNS entry. If this IP sends email, deliverability will be severely impacted. Contact your hosting provider or ISP to request a PTR record.
Generic hostname. The PTR record returns a hostname that looks auto-generated by the ISP (patterns like host-192-0-2-1.example.net). While technically valid, this signals to receiving mail servers that the IP is not purpose-configured for sending email.
RFC 1912 Best Practices
RFC 1912 outlines DNS operational guidelines that remain the standard for rDNS configuration:
- Every internet-reachable IP should have a PTR record.
- The PTR hostname should forward-resolve to the same IP (FCrDNS).
- PTR hostnames should be meaningful, not auto-generated.
- For mail servers, the PTR record should ideally match or align with the HELO/EHLO hostname used during SMTP transactions.
Setting Up Correct rDNS
PTR records are managed by the entity that controls the IP address block, typically your hosting provider or ISP. You cannot set PTR records through your domain registrar's DNS panel. Contact your provider and request that the PTR record for your sending IP be set to a hostname under your control, then create a matching A record for that hostname.
Verify your configuration with this tool and cross-reference against your MX records and DNS configuration to ensure full alignment across your email infrastructure.
FAQ
What is reverse DNS and what is a PTR record?
Reverse DNS (rDNS) is the process of resolving an IP address back to a hostname, the opposite of a standard forward DNS lookup. The mapping is stored in a PTR (Pointer) record within the special in-addr.arpa (IPv4) or ip6.arpa (IPv6) DNS zones. PTR records are essential for identifying the hostname associated with a given IP address, and they are a requirement for any server sending email.
Why does reverse DNS matter for email deliverability?
Major mailbox providers including Gmail, Outlook, and Yahoo check for valid reverse DNS on every connecting mail server IP. If your sending IP lacks a PTR record or has a generic ISP-assigned hostname, your email is significantly more likely to be rejected or routed to spam. Properly configured rDNS is one of the baseline requirements for email deliverability alongside SPF, DKIM, and DMARC.
How do I set up reverse DNS for my mail server?
PTR records are managed by the entity that controls the IP address block, which is typically your hosting provider or ISP -- not your domain registrar. Contact your provider and request that the PTR record for your sending IP be set to a hostname under your domain. Then create a matching forward A record for that hostname pointing back to the IP. You can verify the configuration using our Reverse DNS Lookup tool.
What is FCrDNS (forward-confirmed reverse DNS)?
Forward-confirmed reverse DNS (FCrDNS) means that an IP address has a PTR record pointing to a hostname, and that hostname resolves back to the same IP address via a forward A or AAAA lookup. This bidirectional confirmation is the standard that mail servers check -- a PTR record alone is not sufficient if the forward lookup does not match. FCrDNS failures are treated by many receiving servers as equivalent to having no reverse DNS at all.
What does a generic PTR hostname mean for email sending?
A generic PTR hostname is an auto-generated name assigned by your ISP, typically following patterns like 192-0-2-1.isp.example.net. While technically a valid PTR record, generic hostnames signal to receiving mail servers that the IP is not purpose-configured for sending email. This can result in lower reputation scores and increased spam filtering. Setting a custom PTR hostname that matches your sending domain is a best practice.
Stay on top of your email infrastructure. Sign up for the InboxTooling newsletter for deliverability tips, tool updates, and best practices.