Use case · Domain investigation

Reverse IP lookup for domain and infrastructure investigation

Move from one known infrastructure clue to a broader candidate set that can be prioritized and verified.

Start
Known IP
Process
Scan and triage
Finish
Verify and report
Boundary
Authorized use

Start with a defensible pivot

Use an IP from current DNS, an authorized asset inventory, a documented historical record, or another lawful source. Record where the address came from and what time period the question concerns.

Triage the candidate names

Inspect result density and prioritize names based on the research question: recognizable patterns, relevant registrable domains, known infrastructure, or current resolution. Do not treat every name on a shared address as equally meaningful.

Verify current and historical context

Check current A or AAAA records, RDAP context, certificate evidence where appropriate, and historical records available to you. Distinguish “was observed,” “currently resolves,” “shares infrastructure,” and “is operated by” as separate levels of claim.

Document exclusions as well as findings

Record why high-noise platform names, unrelated tenants, or stale relationships were excluded. Keep the raw export so another analyst can review the filtering choices.

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.