Domain IP & Shared Host Lookup
Enter a website address to find its IPs, then select an IP to discover other domains observed on that address.
Which domain would you like to check?
Enter a domain, HTTP(S) URL or public IP. URL paths and query parameters are excluded from lookups.
The domain or IP is sent to Google Public DNS, Cloudflare DNS (on retry) and HackerTarget for lookups.
Resolved IP addresses
If several IPs are returned, select an address to inspect.
DNS lookup time:
Domains observed on the same IP
Review observed names separately from their current DNS status.
Optional: origin IP information
The IP and shared-domain list above are already queried. Use this optional section only to research public origin clues or enter an owner-provided IP.
Enter an origin IP confirmed by the owner
| # | Domain | Current DNS status |
|---|---|---|
| — | ||
Current checks use Google Public DNS and retry with Cloudflare DNS on failure. Different IP / no address can also reflect CDN or location-dependent answers.
Source: HackerTarget observed data · IPv4 only · Free provider limits apply (currently 20 daily queries per connecting IP and a standard 50-result limit). If more data is returned, up to 5,000 domains are retained and searchable. Dataset coverage and response limits prevent exhaustive results. Provider coverage
Resolve domains and inspect shared-host observations
A records return IPv4 addresses and AAAA records return IPv6. Shared-host lookup finds candidates in a separate IP-to-hostname dataset. Current DNS checks whether those candidates still resolve to the selected IP.
How to use this tool
- Enter a domain or website address and start the lookup.
- Select the IPv4 address you want to inspect.
- Use Check current DNS matches to compare observed domains with current DNS answers.
- Filter the list, copy domain names or download a CSV.
Lookup coverage
- A and AAAA records, CNAMEs in the response, and PTR for the selected IP
- Search all returned IPv4 shared-host domains, with 50 per table page
- Current A and AAAA rechecks for observed domains
- No exhaustive domain list, internal website URLs or owner information
Frequently asked questions
Why do some .de, .nl, .kr or .com sites show unrelated domains?
Every valid suffix follows the same automatic DNS and reverse-IP flow. A proxy IP can return unrelated domains, so the proxy context is shown alongside the results. Optional origin research is available separately and never prevents the shared-domain list from loading.
Can I see every address using the IP?
A complete list of all domains cannot be guaranteed. DNS has no standard query that returns every website on an IP, and observed datasets have coverage and result limits. This tool shows available candidates.
Does a shared IP mean the same owner?
No. Unrelated sites can share an IP through shared hosting or a CDN. An identical IP does not establish common ownership or the same origin server.
Can results include historical connections?
Yes. Observed datasets may include previous connections. Use current DNS checks to compare A and AAAA answers. Results can also vary by time and resolver location.
Does it support IPv6?
Domain AAAA records and IPv6 PTR records are supported. The current shared-host provider supplies IPv4-based data, so shared-domain results are not available for IPv6.
How is PTR different from shared-host data?
PTR contains names published by an IP operator in reverse DNS. Shared-host data is a separate collection of observed hostnames. A single PTR name does not mean only one site uses the IP.
Why do I see a limit or lookup error?
Provider quotas, network availability or browser blocking settings can restrict requests. DNS resolution is independent of shared-host lookup. Missing shared-host results do not prove there are no other sites.
Is the entire URL sent to providers?
Only domains or public IPs are used. URL paths, queries and fragments are excluded; credential-bearing URLs are rejected. Google Public DNS, fallback Cloudflare DNS and HackerTarget may process normal connection information.
Last updated: October 24, 2026 · Google Public DNS · HackerTarget