Run a reverse DNS lookup
A reverse DNS lookup starts with an IP address and asks for the PTR records published for it. Enter a public IPv4 or IPv6 address, then run the query. The PTR query constructs the corresponding reverse name and sends a PTR question to your selected resolver: Google Public DNS or Cloudflare 1.1.1.1. The PTR query result includes the resolver, observation time, response code, returned records, and their remaining TTLs. It does not contact every website that might share the address.
Read more
Use the address alone. Do not include http, a port, a slash prefix, or an IPv6 interface suffix. A PTR query of 8.8.8.8 is a different question from a forward query for dns.google. If you already have a domain and want its published A or AAAA records, use DNS lookup. Forward and reverse records are maintained separately, even when an operator intentionally makes them consistent.
Understand reverse DNS lookup answers
For IPv4, the reverse name places the address's octets in reverse order under in-addr.arpa. For IPv6, each hexadecimal digit is reversed under ip6.arpa. The tool performs that transformation for you, including expansion of compressed IPv6 groups. A PTR query therefore asks a carefully constructed DNS question, not an open-ended search for text containing the address.
Read more
A PTR answer contains a domain name selected by the party controlling the reverse DNS delegation. It may describe a server, a customer circuit, a generic pool, or an operator's naming convention. Those names can be informative, but they are not verified descriptions of the person using the address. Treat a PTR query hostname as operator-published DNS data with a time and source, rather than a personal identity record.
No PTR record does not mean no device
A PTR query can return no answer for a perfectly active public address. Some operators do not publish PTR records for certain ranges, and a record may be absent during provisioning. Read the response code as well as the empty table. NOERROR without a PTR answer differs from NXDOMAIN, and both differ from a resolver failure such as SERVFAIL. An empty answer is not a port scan or a reachability test.
TTLs and cached answers
The TTL shows how long the returned record can remain in a cache, subject to resolver policy. A cached TTL usually differs from the original configured TTL. When comparing PTR query results, keep the hostname, resolver, and time together. A falling TTL is not necessarily a record change. A different hostname can reflect a changed record, different resolver state, or another difference worth checking with the authoritative source.
More than one answer
The protocol can return multiple records, and aliases may appear along the resolution path. A PTR query should display those records without arbitrarily selecting a single value and calling it “the owner.” If a service expects a particular PTR configuration, consult its requirements. Mail delivery policies, for example, may care about relationships between reverse names, forward addresses, and the identity presented by the sending mail server.
Limits of reverse DNS lookup
A PTR query is not a reverse IP website search. Shared hosting can serve many domains from one address, while its PTR record names only a generic host or another operator-chosen value. The returned record does not enumerate virtual hosts, TLS names, customers, or every domain with an A record pointing there. Products that claim to find hosted websites typically rely on separate historical or observational datasets.
Read more
This is not a DNS leak test
The query travels through our server to a named resolver. It does not observe which resolver your browser normally uses for unrelated names. A PTR query may help describe an already identified resolver address, but it does not discover that resolver by itself. A real DNS leak test needs session-specific queries and authoritative observation. Do not read this tool's “Google Public DNS” source label as a claim about your device's DNS settings.
Sources
The core DNS record format is described in RFC 1035, and IPv6 DNS representation in RFC 3596. The resolver response format comes from Google Public DNS documentation. These sources define how a PTR query works; they do not guarantee that any particular operator publishes a PTR record.
For a comparison with hosted-domain datasets, read reverse DNS vs reverse IP. The reverse DNS guide explains forward confirmation, dated domain associations and why a shared CDN address does not establish common website ownership.