Reverse DNS lookup

Find the PTR records published for a public IPv4 or IPv6 address. A PTR record is not a list of every website on that server.

Resolver
Remote DNS query, separate from your device’s DNS path.

One public IP address is converted to its reverse DNS name. Our server queries the resolver you choose; this does not detect your device’s DNS provider.

Example report

Illustrative data. Run a lookup for live results.

1 unique answer records returned

Example report

The selected resolver returned published DNS data. A DNS answer does not establish that a website is online or trustworthy.

Next step: Compare another record type or resolver if you are investigating a recent change.

PTR hostname
  • example-host.example.org.
DNS status
NOERROR
Public IPv4 or IPv6 address
1.1.1.1
Reverse query name
1.1.1.1.in-addr.arpa
TTL (seconds)
300
Resolver
Google Public DNS
Observed at
2026-01-15T14:23:00.000Z
Responses received: 1 of 1 queries.

From address to PTR question

  1. Public IP

    Accept one complete address, without a port or CIDR.

  2. Reverse the address

    Reverse IPv4 octets or expanded IPv6 hexadecimal digits.

  3. Named resolver

    Our server requests PTR data from your selected public resolver.

  4. Read the DNS response

    Keep the answer, response code, TTL and source together.

Operator-published PTR names do not enumerate every website hosted on an address.
On this page

Learn more about Reverse DNS lookup

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.

Reverse DNS lookup questions

Who can change my PTR record?

Usually the provider or organization controlling reverse delegation for the address can change it or give you a management interface. Your domain registrar may not be that organization. If a reverse DNS lookup shows an unwanted value, identify the relevant hosting or internet provider and ask about its PTR process. Be prepared to prove control of the address and any target hostname the provider requires.

Does matching forward and reverse DNS prove trust?

No. Consistency can be operationally useful, but an attacker can also control consistent records for infrastructure they operate. A reverse DNS lookup is one network signal. It does not validate website content, authenticate a person, or replace application security. Avoid allowing sensitive access solely because a returned hostname appears to contain the name of a trusted company.

Can I run a reverse DNS lookup for IPv6?

Yes. The tool expands the IPv6 address and reverses its individual hexadecimal digits to form the ip6.arpa name. You can enter compressed notation; you do not need to create the long reverse name yourself. A reverse DNS lookup for one IPv6 address still asks about that single address. It does not enumerate every address or every device inside the much larger assigned prefix.

Why does the hostname look generic?

Providers often generate names from an address, pool, or service category. A generic hostname may be entirely normal for a dynamic consumer connection. The PTR query reports what was published, not what a user might prefer to be called. If you need the public address currently used by your own browser, the homepage supplies that observation without relying on a hostname convention.

homepage

How should I share a reverse DNS lookup result?

Include the queried address, PTR answers, response code, resolver, and time. State the operational question you are trying to answer, such as a mail server's reverse configuration. Do not claim the hostname identifies a person or every website on the address. A PTR query report is most useful when the recipient can reproduce the exact query and understand what the result does and does not establish.

Does a missing PTR mean the address is offline?

No. A reverse record is published naming data, not a connection test. A host can answer application traffic without a PTR response. Distinguish a completed query with no answer from a resolver failure before deciding what to investigate.

Can I use a PTR name as proof of hosted websites?

No. A PTR is a reverse DNS declaration for an address. It is not an inventory of domains hosted there, especially on shared infrastructure. Forward records and external historical datasets answer different questions and need their own sources.

Why does the TTL shrink between lookups?

A recursive resolver can return an answer already in its cache, with less lifetime remaining. A decreasing TTL is not evidence of a record change. Keep the returned name, resolver and observation time when comparing results.