Guide · Infrastructure
One address can legitimately serve thousands or millions of hostnames. Density changes both the technical workflow and the meaning of association.
Shared hosting, reverse proxies, CDNs, parking platforms, and multi-tenant infrastructure can place unrelated domains behind the same address.
Treat co-location as an infrastructure clue. Do not label domains as related entities without additional evidence.
A browser or desktop interface can become unresponsive if it tries to hold an exceptionally large set in one object. Chunked retrieval and incremental output reduce that risk.
When a broad result is too large, use a recency or year window, compare changes over time, and prioritize domains relevant to the investigation.
Evaluate with your own workflow
Use the protected public preview, review the coverage principles, and test the complete workflow with a short Proof Pass.