Reverse DNS Lookup
Resolve PTR records for public IPv4 and IPv6 addresses.
Reverse DNS (rDNS) answers the question “what hostname is associated with this IP?” using PTR records. Unlike forward lookups that start from a domain name, reverse lookups start from an address rewritten into the in-addr.arpa or ip6.arpa namespaces. Mail administrators care deeply about PTR coherence because many receiving systems treat missing or mismatched reverse DNS as a spam signal.
Who controls PTR records?
Typically your upstream ISP, cloud provider, or colocation network operates the reverse zone. Domain registrars do not automatically create PTR records when you buy a name. If you need mail-friendly reverse DNS, open a support request with the party that assigned the IP and align the PTR with a forward A/AAAA that points back correctly (forward-confirmed reverse DNS).
How to use this tool
- Paste a public IPv4 or IPv6 address.
- Review returned PTR hostnames.
- Forward-check those hostnames with A Lookup or AAAA Lookup.
- Compare with What's My IP when testing your own egress.
Security limits
Private, loopback, link-local, and metadata IPs are blocked. That protects the platform from SSRF-style probing while keeping the tool useful for real public addresses. Timeouts and rate limits keep free infrastructure sustainable.
Common misconceptions
A missing PTR does not always mean an IP is “bad” — many residential networks omit them. For outbound mail servers, however, investing in coherent PTR/A pairs remains one of the highest leverage deliverability hygiene steps. Related reading lives on the DNS Checkers blog email authentication series.
Cloud and BYOIP realities
On major clouds, PTR management may live in a separate console from forward DNS. Bring-your-own-IP programs add more paperwork but give you control of reverse zones that would otherwise stay with the provider. Before launching transactional mail, confirm PTR, matching A/AAAA, HELO/EHLO names, and authentication records in one checklist — reverse DNS alone never salvages a missing SPF.
Security teams also use PTR data during incident response to label noisy scanners. Remember that PTR can be spoofed in the sense that anyone controlling a reverse zone can publish arbitrary names; always forward-confirm. DNS Checkers blocking of private ranges keeps the tool focused on internet-facing addresses where PTR hygiene actually matters.
When mail still fails with a perfect PTR, move on to SMTP banners, blocklists, and authentication records — PTR is necessary hygiene for many receivers, not a complete deliverability program.
Educational footnote: reverse zones are ordinary DNS zones with unusual names. Once you see them that way, PTR tickets become less mysterious and more like any other record change request.
Frequently asked questions
Quick answers about propagation, resolvers, and how this checker works.
What is reverse DNS? +
Reverse DNS maps an IP address back to a hostname using PTR records in the in-addr.arpa or ip6.arpa zones.
Why do mail servers care about PTR? +
Many receiving MTAs check that the connecting IP has a PTR that forward-resolves sensibly, which reduces spam risk.
Who sets PTR records? +
Usually your IP provider or hosting company controls the reverse zone, not your domain registrar.
Can I look up private IPs? +
No. DNS Checkers blocks private, loopback, link-local, and cloud metadata addresses to prevent SSRF abuse.
Does a missing PTR mean the IP is bad? +
Not always. Many residential and some cloud IPs lack PTR records. It is more important for outbound mail servers.