Practical guide
How to use the reverse ip lookup
The reverse IP lookup asks DNS for the PTR hostname associated with a public IP address. Network operators use PTR records to describe hosts and support services such as mail reputation, but many addresses have no reverse record.
Good reasons to use it
- Confirm the reverse hostname presented by a mail or application server.
- Add context to an unfamiliar IP address in a log.
- Check whether forward and reverse DNS align for an infrastructure hostname.
A reliable workflow
- Enter the public IP address.
- Run the lookup and record the returned PTR hostname, if any.
- Resolve that hostname forward when you need to compare both directions.
How to interpret the result
A PTR result is a label controlled by the IP address owner. It may describe a hosting pool rather than a customer domain. No result is common and does not by itself indicate a broken server, although some mail systems expect reverse DNS.
Frequently asked questions
Who can change a PTR record?
Usually the ISP, cloud provider or network owner that controls the IP range.
Should reverse and forward DNS match?
For some services—especially email—forward-confirmed reverse DNS is a useful trust signal, though requirements vary.