PTR Checker

What are PTR Records?

PTR (Pointer) records are DNS entries used for reverse DNS lookups. While standard DNS maps domain names to IP addresses (forward lookup), PTR records do the opposite: they map IP addresses to domain names (reverse lookup). This allows anyone to query an IP address and discover what hostname is associated with it.

PTR records are stored in a special DNS zone based on the IP address. For IPv4, this zone uses the in-addr.arpa domain with the IP octets reversed. For example, the PTR record for IP 192.0.2.1 would be found at 1.2.0.192.in-addr.arpa.

Forward-Confirmed Reverse DNS (FCrDNS)

Forward-Confirmed Reverse DNS is a verification technique that checks whether forward and reverse DNS records match consistently:

1. Reverse lookup – Query the PTR record for the IP address to get the hostname.

2. Forward lookup – Query the A or AAAA record for that hostname.

3. Comparison – Verify the forward lookup returns the original IP address.

When both directions match, the IP address has FCrDNS. This bidirectional verification proves that whoever controls the domain also controls the IP address, establishing a trust relationship between the two.

FCrDNS failure occurs when either the PTR record is missing, the forward lookup fails, or the IP addresses do not match.

Why PTR Records Matter for Email

PTR records play a critical role in email deliverability:

• Spam filtering – Many mail servers check whether the sending IP has a valid PTR record. Missing or misconfigured PTR records can cause messages to be rejected or marked as spam.

• FCrDNS verification – Receiving servers often require FCrDNS to pass. A mismatch suggests the sender may not legitimately control their infrastructure.

• Reputation systems – IP reputation services use PTR records to associate sending behavior with domain identity. Proper PTR configuration helps build and maintain your sending reputation.

• SMTP requirements – RFC 5321 recommends that mail servers have PTR records. Some providers strictly enforce this requirement.

• Professional appearance – PTR records that match your sending domain present a more trustworthy identity than generic ISP hostnames or missing records.

What MailHealth Checks

Our PTR checker validates your mail server configuration by examining:

• PTR record existence – Confirms a PTR record is published for your mail server IP address.
• Hostname validity – Verifies the PTR record points to a properly formatted hostname.
• FCrDNS verification – Tests whether the hostname resolves back to the original IP address.
• Domain alignment – Checks if the PTR hostname relates to your sending domain.
• Common issues – Detects problems like generic ISP hostnames or localhost entries.

Properly configured PTR records demonstrate that you control your mail infrastructure and take email authentication seriously. They are a foundational element of email deliverability that complements SPF, DKIM, and DMARC.