Start typing to search 227 tools.
Reverse DNS Lookup
Look up the PTR hostname for a public IPv4 or IPv6 address and verify whether the hostname resolves back to the same address.
What Reverse DNS Lookup does
Reverse DNS Lookup converts a public IP address into its published PTR hostname when reverse DNS is configured. The tool then resolves that hostname forward again and checks whether the original IP appears in the returned addresses. This forward-confirmed reverse DNS check is useful for mail infrastructure, network diagnostics, server naming, logging, and troubleshooting.
Reverse DNS is controlled by the owner of the IP address space, not by the ordinary domain-zone owner in the same way as A or AAAA records. Many valid public IP addresses intentionally have no PTR record, so a missing reverse hostname is a normal possible result rather than proof of an error.
How to use
- Enter the IP address. Use a public IPv4 or IPv6 address.
- Run Reverse DNS Lookup. Trexmi asks the server resolver for the PTR hostname.
- Review the PTR result. If no PTR exists, the report clearly shows that state.
- Check forward confirmation. When a hostname exists, Trexmi resolves it back to IP addresses.
- Compare addresses. A forward-confirmed result means the original IP is present in the forward DNS response.
Why use Reverse DNS Lookup?
Focused controls, predictable output, and a workflow designed around this exact transformation.
Find PTR hostnames
Convert a public IPv4 or IPv6 address into the reverse hostname published by the address owner.
Check FCrDNS
See whether the PTR hostname resolves forward to the same original IP address.
Inspect every address
Review all returned forward addresses rather than relying on one simplified hostname result.
See resolver timing
Use the lookup time as a simple diagnostic signal from the Trexmi server resolver.
Questions about Reverse DNS Lookup
Practical details about input, output, privacy, limits, and the best way to use this tool.
01 What is reverse DNS lookup?
Reverse DNS lookup starts with an IP address and retrieves a PTR record that can map the address to a hostname.
02 What is a PTR record?
A PTR record is the DNS record used in reverse zones to associate an IP address with a domain name.
03 Why does an IP have no reverse DNS?
The IP address owner may not have configured a PTR record. Many perfectly valid addresses do not publish reverse DNS.
04 What is forward-confirmed reverse DNS?
Forward-confirmed reverse DNS means the PTR hostname resolves forward and includes the original IP address among its A or AAAA results.
05 Can I change reverse DNS in my normal domain DNS panel?
Usually not. PTR records are normally managed by the ISP, hosting provider, cloud provider, or organization that controls the IP address block.
Read the HTTP Headers Guide
Connect DNS, redirects, HTTP headers, requests, responses, caching, security, and practical web diagnostics.
- Requests and response headers
- Redirect and cache diagnostics
- Security and API debugging
How Reverse DNS Lookup works
Reverse DNS Lookup begins with a public IP address rather than a hostname. IPv4 addresses are represented under the in-addr.arpa reverse namespace and IPv6 addresses under ip6.arpa. DNS resolvers can query those reverse names for PTR records.
The result is best understood as a published naming hint controlled through the reverse DNS delegation for the address block. It is not an ownership certificate and does not replace forward DNS, WHOIS/RDAP, TLS, or application-level checks.
PTR records and reverse zones
A PTR record maps the reverse representation of an IP address to a hostname. The organization controlling the address range or its provider usually manages the reverse zone. This is why changing an A record in an ordinary domain DNS zone does not automatically change the PTR record for the server IP.
For protocol details, see RFC 1035, which defines core DNS concepts including PTR records, and the IANA ARPA domain reference for reverse infrastructure context.
Forward-confirmed reverse DNS
After a PTR hostname is found, Trexmi performs a normal forward lookup of that hostname. If the original IP is among the resulting addresses, the report marks the result as forward-confirmed. This check is commonly called FCrDNS.
Forward confirmation does not by itself prove identity or authorization. It only shows that reverse and forward DNS agree for that mapping at the time of the lookup. Security decisions should use the authentication method designed for the protocol.
Reverse DNS for mail and servers
Mail operators often pay close attention to reverse DNS because receiving systems can use PTR names as one reputation and consistency signal. A mail server may also present a hostname in SMTP that administrators expect to align with reverse and forward DNS. Requirements differ between providers, so PTR consistency should be combined with SPF, DKIM, DMARC, TLS, and correct mail-server configuration.
Reverse names are also useful in logs and monitoring because a meaningful hostname can make infrastructure easier to identify. Do not assume every PTR string is trustworthy user-facing metadata; it comes from DNS and should be treated as network information.
Related Trexmi tools
Use DNS Lookup for forward A, AAAA, MX, NS, TXT, and other records, WHOIS Lookup for domain registration data, SSL Certificate Checker for TLS identity and expiry, and HTTP Header Checker when the IP ultimately serves a website that needs HTTP diagnostics.
Reverse DNS Lookup summary
Reverse DNS Lookup answers a focused network question: what PTR hostname is published for this public IP, and does that hostname resolve back to the same address? A found and forward-confirmed result is useful evidence of consistent DNS configuration. A missing PTR or failed confirmation is a reason to inspect the IP provider and DNS design, not an automatic indication that the address itself is broken.