How it works

From an IP address to an export you can investigate.

A repeatable workflow makes reverse-IP results easier to operate, compare, and defend.

Step 1
Prepare
Step 2
Scan
Step 3
Review
Step 4
Verify

1. Prepare public IP addresses

Start from a question you are authorized to investigate. For one address, confirm that it is a valid public IPv4. For a list, use one address per line and remove duplicates, ports, URL syntax, comments, blank lines, and private ranges. Save a copy of the original input before cleaning it.

Representative evaluation matters. Include ordinary addresses, low-density addresses, and high-density shared infrastructure from your actual workflow instead of judging a provider by one unusual example.

2. Start the scan

Submit the address or list and allow the client to retrieve matching domain associations from the available index. The interface should show progress and separate input errors from service or connectivity errors. Avoid launching duplicate jobs against the same input and output location.

3. Review counts and sample names

Use the total result count to understand density, then inspect names before drawing conclusions. A large result can indicate shared hosting, a reverse proxy, a parking platform, or another multi-tenant service. A small result can reflect narrow hosting, limited observation coverage, or a recently changed address.

4. Save the result set

Choose a dedicated output location and keep it with the input list, scan date, and investigation notes. Progressive writing helps preserve useful work during long jobs. Do not manually edit the raw export before retaining an original copy.

5. Verify material relationships

Check current A or AAAA records where relevant, compare RDAP or registration context, review certificate evidence when appropriate, and consider shared infrastructure. Verification should match the question: current hosting, historical association, operational connection, and common ownership are different claims.

6. Document scope and limitations

Record what you scanned, when you scanned it, which product version you used, what the result represents, and which independent checks support your conclusion. State uncertainty directly. A defensible report distinguishes an observed association from an ownership or control claim.

Start with your own evidence

Check an IP before you choose a plan.

Run a protected public preview, then compare access based on your real workload.