Reverse IP Lookup

Find the hostname (PTR record) behind an IP address.

What a reverse IP lookup returns

DNS can map a name to an address, and it can also map an address back to a name. The second direction uses PTR records stored under the special domains in-addr.arpa for IPv4 (RFC 1035) and ip6.arpa for IPv6 (RFC 3596). To find the PTR record for 8.8.8.8, a resolver reverses the octets and asks for 8.8.8.8.in-addr.arpa. This tool asks our server's resolver to do exactly that, through PHP's gethostbyaddr function, and shows the one hostname it gets back. On 11 October 2026, 8.8.8.8 returned dns.google and 1.1.1.1 returned one.one.one.one.

A PTR lookup returns a single name chosen by whoever controls the address. It is not a list of websites. An address on a shared hosting server may serve hundreds of domains, yet its PTR record names the server itself: 82.25.87.1, the server behind edeskcloud.com, returns us-bos-web1978.main-hosting.eu. Finding every domain that points at an address needs a passive DNS database built from years of recorded queries, which this tool does not have and does not claim to search.

When an address has no PTR record the tool reports "No PTR record found". That is common and not a fault: 172.66.147.243, the Cloudflare address that example.com resolves to, has none. If you only have a domain name, resolve it first with the DNS checker and then look the address up here.

Why so many addresses have generic or missing names

PTR records are published by the organisation that holds the address block, normally an ISP, a hosting company or a cloud provider, not by the owner of the website running on it. IANA delegates address space to the five regional registries, they allocate it to networks, and each network decides what, if anything, to put in its reverse zone (IANA number resources). RFC 1912 advises that every reachable host should have a PTR record matching its A record, but that is operational advice and nobody enforces it.

Three outcomes are typical. Large providers generate names from the address itself, which produces labels such as ec2-52-14-123-45.us-east-2.compute.amazonaws.com. Hosting companies name the server rather than the customer's site. Residential and mobile ranges carry machine-generated names or none at all. A custom PTR such as mail.yourdomain.com exists only when the server operator has asked the provider for it, or has set it in a cloud console that allows it.

Pattern What it indicates Example
ec2-*Amazon EC2 instance with the default nameec2-52-14-123-45.us-east-2.compute.amazonaws.com
*.bc.googleusercontent.comGoogle Cloud instance with the default name45.123.14.52.bc.googleusercontent.com
Host or server nameShared or managed hosting server; many sites share itus-bos-web1978.main-hosting.eu
mail.* or smtp.*A mail server whose operator set a custom PTRmail.example.com
Address embedded in the nameISP-generated name, no custom PTRhost-203-0-113-50.example-isp.net
*.static.* or *.dynamic.*ISP naming that hints whether the address is fixed50.113.0.203.static.example-isp.net
No PTR record foundThe address owner published nothing in the reverse zone172.66.147.243

Reverse DNS and outgoing mail

The place where PTR records matter most is email. A receiving mail server looks up the PTR record of the connecting address, then resolves that name forward and checks that it leads back to the same address. This forward-confirmed reverse DNS is part of Google's published requirements for anyone sending to Gmail: its Email sender guidelines ask senders to publish valid reverse DNS for their sending addresses, pointing to their own domain, and require the sending IP to match the address of the hostname in the PTR record. Mail from an address with no PTR record, or with one that does not resolve back, is far more likely to be rejected or filed as spam.

To check your own mail server, look up its address here, then resolve the hostname you get back in the DNS checker and confirm the A or AAAA record matches. If the name is generic or missing, ask the company that supplies the address to set a PTR record for the hostname your mail server announces in its HELO greeting, and make sure that hostname has a matching A record first. The IP address lookup shows which organisation and autonomous system the address belongs to, which tells you whom to ask.

Frequently Asked Questions

Can this tool show which websites share an IP address?

No. A PTR lookup returns one name per address, and that name is usually the server's, not any of the sites on it. Services that list "domains on the same IP" work from large passive DNS archives that record which names have resolved to which addresses over time. This page performs a single live PTR query and nothing else.

Why does my server's address show my host's name instead of my domain?

Because the host owns the address and wrote the PTR record. Unless you have asked for a custom PTR, the reverse zone carries the provider's own server name. That is harmless for a website; the hosting checker shows the A, NS and MX records visitors actually use. It matters only if the same address sends mail.

How do I set or change a PTR record?

Through whoever assigned you the address, not your domain registrar. Cloud providers such as AWS, Google Cloud, Azure, DigitalOcean and Hetzner let you set it in their console or API, often by naming the server after the hostname you want. With a VPS or dedicated host, open a support ticket. Create the matching A record first, because providers commonly check it before accepting the PTR.

Does a missing PTR record break my website?

No. Browsers never perform reverse lookups, so visitors are unaffected. The effects show up elsewhere: mail from that address is treated with suspicion, some SSH servers and logging tools pause while they wait for a reverse lookup to time out, and traceroute output shows bare addresses instead of names.