IPv4 and IPv6 PTR names
IPv4 addresses are converted to in-addr.arpa names, while IPv6 addresses are expanded and converted to ip6.arpa names before lookup.
Network Tools
| IP | Version | PTR Name | Hostname | TTL | Resolver | Message | Copy |
|---|---|---|---|---|---|---|---|
| No reverse lookup has run yet. | |||||||
Run a lookup to see JSON output.
Reverse DNS
This IP to Hostname page converts IPv4 and IPv6 addresses into reverse DNS PTR names, then queries the selected DNS-over-HTTPS resolver for matching hostnames. It helps developers, DevOps teams, mail administrators, support staff and security analysts investigate server inventory, mail delivery, logs and suspicious traffic. Paste one IP per line, choose Cloudflare or Google as the resolver, set a timeout, then review the PTR name, returned hostname, TTL, resolver source and message. Results can be copied or exported as CSV or JSON for tickets and audit notes.
IPv4 addresses are converted to in-addr.arpa names, while IPv6 addresses are expanded and converted to ip6.arpa names before lookup.
Choose Cloudflare or Google DNS-over-HTTPS, then inspect the returned hostname, TTL, resolver source and message state for each IP address.
Copy resolved hostnames, switch to JSON output, or download CSV and JSON reports with PTR names and resolver messages included.
PTR records are often checked during email delivery troubleshooting. Pair the result with MX Lookup when reviewing mail routing.
Resolve known server IPs to their reverse hostnames when reconciling infrastructure lists, provider records or support handoffs.
Look up IPs found in access logs, firewall events or monitoring alerts to see whether a useful PTR hostname exists.
Use Hostname to IP after a PTR lookup when you need to compare reverse DNS with forward A or AAAA records.
Use one IPv4 or IPv6 address per line. IPv4-mapped IPv6 input is intentionally rejected, and addresses with spaces are not accepted.
8.8.8.8 becomes 8.8.8.8.in-addr.arpa. IPv6 addresses are expanded, reversed by nibble and queried under ip6.arpa.
A no-record message is normal for many addresses. PTR records are optional and managed by the IP owner or hosting provider, not by this tool.
Reverse DNS lookup reads PTR records only. It does not prove ownership, reputation, physical location, security status, uptime or open ports, and a PTR hostname may not match the forward DNS records for that hostname. DNS answers can vary by resolver cache, TTL, timing and record configuration, so the table reflects the selected resolver at lookup time. IP addresses are sent to the selected public DNS-over-HTTPS resolver to perform the query.
It converts IPv4 and IPv6 addresses into reverse DNS PTR names, queries the selected DNS-over-HTTPS resolver, and returns any PTR hostname, TTL, resolver and message details.
No. PTR records are optional and controlled by the IP owner or hosting provider. Many IP addresses return no reverse DNS hostname.
Yes. A PTR hostname does not have to match the hostname that points to the same IP. Use Hostname to IP when you need to check the forward A or AAAA records.
Yes. Standard IPv6 addresses are expanded into ip6.arpa PTR names before lookup. IPv4-mapped IPv6 input is not supported by this page.
Reverse DNS answers can vary by resolver cache, TTL, timing and record configuration. This page shows the answer from the resolver selected for the lookup.
No. PTR lookup only reads reverse DNS records. It does not prove ownership, reputation, physical location, security status, uptime or open ports.