Reverse IP Lookup

Find the domains that point to the same IP address: server neighbours, PTR, ISP and ASN. Enter an IP or a domain.

How to find all websites on one IP address

A reverse IP lookup lists the domains whose A records point to the same IP address — your neighbours on shared hosting or a server. Enter an IP or a domain; we resolve the domain for you. You also get the address's PTR record, ISP and ASN, plus a warning when the IP belongs to a CDN or cloud, where thousands of unrelated sites share it. The list comes from the HackerTarget dataset (public DNS data) and is never complete.

Domains hosted on one IP address

Accepts an IP or a domain

PTR, ISP and ASN of the address

Warning for Cloudflare and other CDN IPs

How to Use

Enter an IPv4 address or a website domain
Check the ISP and whether there is a CDN warning — for a Cloudflare IP the neighbour list is meaningless
Review the domains and confirm the important ones with Domain to IP

FAQ

It finds every domain that points to a given IP address. Normal DNS answers "what is this domain's IP"; reverse IP answers the opposite, "which domains use this IP". DNS itself cannot answer that, so services build datasets by resolving millions of domains and recording their A records.

The dataset only knows domains that have appeared in public DNS data: new, obscure and internal domains may be missing, and sites that moved away may linger. So the list is an estimate, not a full census of the server. The PTR record does not help either — an IP has one, and it usually names the host, not the sites.

Cloudflare and other CDNs serve their customers' sites from shared addresses: one IP fronts thousands of domains, and a site's address can change. Such a list says nothing about the real server, which is hidden behind the proxy. We flag CDN and cloud IPs with a warning.

Google has said repeatedly that sharing an IP with other sites does not affect rankings by itself. The real risk is email: if neighbours send spam, the shared IP ends up on DNSBLs and mail from your domain may go to spam. You can check that with the IP blacklist check.

Yes. The data comes from the free HackerTarget API, which has a daily quota; when it runs out we tell you so. Results for each IP are cached for 24 hours, so re-checking the same address does not use the quota. The lookup works for IPv4 only.

How a reverse IP lookup works

Normal DNS answers "what is this domain's IP". The reverse question — "which domains use this IP" — cannot be answered by DNS itself: no record lists every site on a server. The IP's PTR record does not help either; there is one per address and it usually holds a technical hosting name such as server12.hoster.net. So reverse IP services build their own datasets: they resolve millions of domains on a schedule, store their A records and search them by IP.

This tool takes its list from the HackerTarget dataset, built from forward and passive DNS data. Two things follow: new, obscure and internal domains may be missing, and sites that moved away long ago may still be listed. To confirm a particular domain, use Domain to IP.

How to read the result

Field	What it shows	What to look for
IP and PTR	The checked address and its reverse DNS record	A PTR like `static.1.2.3.4.hoster.com` is the host's server; a site name in the PTR more often means a dedicated server
Hostnames in the dataset	How many domains and subdomains point to the IP	Count subdomains in: `www`, `mail` and `shop` of one site are three rows
ISP and ASN	Who owns the network the IP is in	Details in ASN lookup and IP geolocation
CDN warning	The IP belongs to Cloudflare, Fastly, Akamai or a cloud	The neighbour list is meaningless then — see below

How many sites on one IP is normal?

1–5 domains — most likely a dedicated server or VPS with one owner.
Dozens to hundreds of domains — ordinary shared hosting. That is normal and does not affect Google rankings by itself.
Thousands of domains, or a Cloudflare/CDN IP — a shared proxy or cloud platform address. The site's real server is hidden, and the list shows random customers of the same platform, not your neighbours on the hardware.

When the IP belongs to a CDN, you usually cannot find the origin server through DNS — the proxy hides it on purpose. Subdomains that are not proxied (mail., ftp., cpanel.) sometimes give a hint, but there is no guarantee.

Why look up the sites on an IP

Hosting and email audits

Google has said repeatedly that sharing an IP with other sites does not hurt rankings by itself. The real risk is email: if neighbours send spam, the shared IP lands on blacklists and mail from your domain goes to spam. Run the address through the IP blacklist check.

Network footprints in link building

When dozens of donor sites sit on one IP or in one small network, that is a visible footprint of a site network run by one owner. Reverse IP together with ASN helps you spot such groups before buying links.

Competitors and security

Neighbours on a dedicated server reveal the owner's other projects. Phishing or malware sites on the same IP are a reason to check both the host and your own site.

Reverse IP and PTR from the command line

# The site's IP (forward lookup)
dig +short example.com

# The address's PTR record (reverse DNS)
dig -x 203.0.113.5 +short

# Domains on an IP from the HackerTarget dataset (free, daily quota)
curl "https://api.hackertarget.com/reverseiplookup/?q=203.0.113.5"

A single PTR is not a list of sites: it only shows the name the network owner assigned to the address. You can check the PTR and whether it matches the forward record with reverse DNS lookup.

Limitations

IPv4 only: the dataset does not cover IPv6.
The free API has a daily quota. When it runs out, the tool tells you instead of showing an empty list.
Results for each IP are cached for 24 hours: re-checking the same address does not use quota, but it also will not see changes within that day.
For a domain with several IPs, the first IPv4 is checked. The other addresses are shown as links so you can check them separately.