PTR lookup

Reverse DNS Lookup

Resolve a public IP address back to the PTR hostnames that point at it, with parsed output and raw command views when available.

Reverse DNS is especially useful for mail, trust checks, hosting clues, and understanding whether an IP maps back to an expected hostname.

DNS & Names

Free public tool. No account required.

Summary

Location-sensitive tools compare Russia and Finland in one combined diagnostics report. Tools that are mostly location-independent stay single-result on purpose.

PTR hostnames

The parsed records show which hostnames resolve back from the IP, if any public PTR answer exists.

Raw command view

When the system dig or nslookup command returns useful text, the raw section preserves it for operators who prefer command output.

Empty-state clarity

A missing PTR record is reported clearly, which is often more useful than a blank output block.

Public IP address

Reverse DNS Lookup

Ready

This page expects a public IP address and runs a PTR lookup against it.

Location-sensitive tools compare Russia and Finland in one combined diagnostics report. Tools that are mostly location-independent stay single-result on purpose.

Examples

Report

Ready

Summary

Server-side diagnostic report

Report appears here

Run a check to generate a structured report with status, timings, technical details, and raw output where available.

SummaryAppears after the check finishes.
DNS recordsAppears after the check finishes.
Raw outputAppears after the check finishes.

01

What this tool checks

PTR hostnames

The parsed records show which hostnames resolve back from the IP, if any public PTR answer exists.

Raw command view

When the system dig or nslookup command returns useful text, the raw section preserves it for operators who prefer command output.

Empty-state clarity

A missing PTR record is reported clearly, which is often more useful than a blank output block.

02

How to use it

01

Paste the IP you want to inspect and run the PTR lookup.

02

Read the parsed hostname list first, then use the raw output if you need the exact command response.

03

Open IP Lookup next when you want ASN, nameserver, or RDAP context around the same address.

03

How to read the result

No PTR is common

A public IP does not have to publish reverse DNS. The absence of a PTR answer is common and not automatically a fault.

PTR is not forward confirmation

A PTR hostname can exist even when the forward A or AAAA record points somewhere else. You still need direct DNS checks for full confirmation.

Useful for reputation checks

Reverse DNS often helps you understand whether an address belongs to a CDN, mail provider, or cloud host before you dive into RDAP or ASN data.

Guides that help you get more from this tool

Interpret the output, understand common failure modes, and choose the next diagnostic step without leaving the product.

Reverse DNS FAQ

Why would I care about PTR records?

They are useful for email diagnostics, provider hints, and checking whether an address maps back to a hostname you actually recognize.

Can a PTR answer contain multiple hostnames?

Yes. The page renders every PTR hostname the resolver returned, not just the first one.

What should I open next after PTR?

Usually IP Lookup for ownership hints, or DNS Lookup if you want to compare the reverse result against forward records.

Related tools