What is reverse DNS?
A reverse DNS lookup starts with an IP address and asks whether a PTR record maps that address back to a hostname. This is the opposite direction from ordinary DNS A or AAAA resolution, which starts with a hostname and returns one or more IP addresses.
PTR records are optional. Many residential addresses have generic provider hostnames, some server addresses have descriptive hostnames, and many addresses have no usable PTR record at all.
What can a PTR hostname tell you?
A PTR record can provide infrastructure context. It may suggest a mail server, hosting node, broadband pool, cloud region or provider naming convention. However, the hostname is configured by the network responsible for reverse DNS and should not be treated as proof of the person or website using the IP.
Why FCrDNS is stronger than PTR alone
Forward-confirmed reverse DNS takes the PTR hostname and resolves it forward again. Verification succeeds when the original IP appears in the hostname's A or AAAA results. This tests consistency in both directions and can expose a stale or mismatched PTR configuration.
Where reverse DNS is commonly used
Mail systems often examine reverse DNS as one part of server reputation and configuration checks. Network operators use PTR names in logs and inventory, while administrators use reverse lookups to make unfamiliar addresses easier to recognize during troubleshooting.
What reverse DNS does not prove
A successful PTR or FCrDNS result does not authenticate a user, prove ownership of a domain, or establish that a particular application is running on the address. Combine DNS with RDAP, ASN and application-level evidence when you need stronger context.