Reverse DNS Lookup
Enter an IPv4 or IPv6 address to look up its PTR (reverse DNS) hostname, if one exists.
Input
Results
Overview
The Reverse DNS Lookup takes an IPv4 or IPv6 address and returns the hostname recorded for it in a PTR (pointer) record, if one exists. Where an ordinary DNS lookup turns a name into an address, reverse DNS goes the other way.
Reverse DNS appears in mail server reputation checks, log analysis, traceroute output, and incident response, where a hostname such as mail-out-17.provider.example tells you far more about an address than the number alone.
How It Works
Reverse lookups use special zones under in-addr.arpa (IPv4) and ip6.arpa (IPv6). For IPv4 the octets are reversed and the suffix is appended, so 203.0.113.10 is looked up as 10.113.0.203.in-addr.arpa. For IPv6 the address is expanded to its 32 hexadecimal digits, reversed digit by digit, and placed under ip6.arpa. The tool builds the right name, asks a DNS-over-HTTPS resolver for its PTR record, and shows the result.
The key fact for interpreting results is who controls the record. A PTR record lives in the reverse zone, which is delegated to whoever holds the IP block, usually an ISP or cloud provider, not to the owner of a domain name. Many addresses have no PTR record, and nothing forces a PTR to match the forward DNS of the name it returns.
How to Use the Reverse DNS Lookup
- Enter a public IPv4 or IPv6 address, for example
203.0.113.10. - Press Calculate.
- The result shows the hostname, or "No PTR record found." if none is published.
- To verify the name, look it up in the DNS Lookup and confirm that it resolves back to the same address.
Worked Example
How an address becomes a reverse name
You are reviewing a mail log and want the hostname behind 203.0.113.10. The sample result is illustrative, since reserved documentation addresses do not have real PTR records.
Input
IP address: 203.0.113.10
Illustrative output
IP Address: 203.0.113.10
Hostname (PTR): mail-out-10.provider.example
This output is an illustrative sample to show the layout and meaning of each field. Real results depend on the target and on when you run the check.
Behind the scenes the octets 203.0.113.10 are reversed to 10.113.0.203 and the in-addr.arpa suffix is added, so the name queried is 10.113.0.203.in-addr.arpa (the tool displays only the address and the resulting hostname). The PTR answer is the hostname the address's owner has chosen to publish.
That hostname is only a claim. To treat it as meaningful, do a forward-confirmed check: resolve mail-out-10.provider.example and see whether it returns 203.0.113.10. If it does, the name and address agree; if not, the PTR is not trustworthy evidence.
Interpreting Results
- A hostname is returned
- The address's owner published a PTR record. Hostnames often reveal the provider and role (mail relay, customer, cloud instance).
- "No PTR record found."
- A normal, common result: consumer lines and many cloud addresses have no PTR, or the owner has not configured one. It is not an error and says nothing about reputation by itself.
- Generic hostnames
- Names built from the address itself (like
203-0-113-10.isp.example) are automatically generated defaults and carry little information.
Troubleshooting
- "Invalid IPv4 or IPv6 address."
- Check the format. IPv4 needs four octets of 0–255; IPv6 uses colon-separated hexadecimal groups.
- "This target cannot be queried."
- Private, loopback, link-local and other non-public addresses are refused. Reverse lookups for internal addresses must be done against your own resolver.
- My mail server's PTR is missing and mail is being rejected.
- Ask the owner of the IP block (your ISP or cloud provider) to set a PTR record that matches your mail server's hostname, and make sure that hostname resolves back to the same IP.
- The hostname I expected is not shown.
- PTR records are set by the IP block owner, not through your domain's DNS. A domain's A record does not create a PTR.
Limitations and Accuracy
- Only the first PTR record is displayed (an address can have several).
- The tool does not perform the forward-confirmation check for you.
- Results come from a public resolver and may be cached. Internal and split-horizon reverse zones are not visible.
- Only public addresses are accepted.
Data Handling
Uses server-side requests. The IP address you enter is sent to this site's server function, which converts it to the reverse name and queries a DNS-over-HTTPS resolver.
Sent to: Cloudflare (cloudflare-dns.com).
Inputs travel as URL query parameters, so avoid entering confidential internal hostnames or personal data. See the Privacy Policy for how requests are handled.
Frequently Asked Questions
Is reverse DNS the same as a WHOIS lookup?
No. Reverse DNS returns a hostname chosen by the IP owner. WHOIS/RDAP describes registration data for a domain, and the IP version of that data, which lists the network's owner, is different again.
Why do mail servers care about PTR records?
Receiving servers often check that a sending IP has a PTR and that the name resolves back to the IP, as one of several signals separating legitimate servers from compromised or misconfigured ones.
Can an address have more than one PTR?
Technically yes, though one is conventional. This tool shows the first.