Skip to content
AdminKit

Forward-confirmed reverse DNS

What is Forward-confirmed reverse DNS?

Forward-confirmed reverse DNS (FCrDNS) checks that a sending IP's PTR hostname resolves forward back to the same IP, a basic anti-spoofing signal receiving mail servers use before accepting mail. RFC 1912 flags a PTR/A mismatch as a common DNS error FCrDNS catches. AdminKit's reverse DNS and DNS lookup tools together let you run both halves of the check manually.

By AdminKit team, Netbase JSC · Updated

Forward-confirmed reverse DNS (FCrDNS) is a two-step check some receiving mail servers run on a connecting IP before accepting mail: look up the IP’s PTR record to get a claimed hostname, then look up that hostname’s own A or AAAA record and confirm it resolves back to the same IP. RFC 1912 (document record at the IETF Datatracker) flags a mismatched PTR and A record as a common DNS configuration error, and Google’s bulk sender guidelines require exactly this forward/reverse match for inbound mail. Mail servers implement the check directly: Postfix’s reject_unknown_client_hostname restriction rejects a client when its IP address-to-name lookup fails, when the name-to-address lookup fails, or when that name-to-address mapping does not match the client IP address. Those same bulk-sender rules also require a one-click List-Unsubscribe header for high-volume senders — a separate, recipient-facing reputation signal from the forward/reverse match itself. Checking only the PTR record has a gap, since whoever controls an IP block can publish any hostname there; confirming the forward record agrees closes that gap without needing a cryptographic signature, though it’s still a hygiene signal rather than proof of identity. FCrDNS predates SPF, DKIM and DMARC, and survives because it’s cheap and catches abuse infrastructure — compromised devices, throwaway cloud instances — that was never configured with matching forward and reverse records in the first place. AdminKit’s reverse DNS and DNS lookup tools together let you run both halves of an FCrDNS check manually. When the connecting IP is IPv6, that second lookup is specifically an AAAA record rather than an A record.

AdminKit groups forward-confirmed reverse DNS under its email authentication cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

What two lookups does an FCrDNS check require?

First a PTR lookup on the connecting IP to get a claimed hostname, then a forward A or AAAA lookup on that hostname to confirm it resolves back to the same IP.

What gap does confirming the forward record close?

Whoever controls an IP block can publish any PTR hostname there, so checking the PTR alone proves nothing; confirming the forward record agrees closes that gap without needing a cryptographic signature.

Does FCrDNS replace SPF, DKIM or DMARC?

No -- FCrDNS predates all three and is used alongside them as a cheap, separate hygiene signal, not a cryptographic proof of identity.