A defined collection boundary.
Responsible discovery starts with publicly reachable infrastructure and the metadata needed to understand it. It should not require bypassing authentication or attempting to gain access to private systems.
Responsibility
Understand infrastructure.
Respect its operators.
Internet discovery needs clear limits, accountable methods and a practical path for the people operating the systems we observe.
Context, not assumptions.
A shared certificate, address or hosting provider can be evidence of a relationship. It is not, by itself, proof of common ownership. Keep that distinction visible when reviewing findings.
Consider operational impact.
Collection needs limits, identifiable sources and a way to respond to operator concerns. Sensitive environments need particular care.
A path for operators.
Operators should be able to identify collection traffic, request an exclusion and challenge inaccurate information. Our opt-out flow is being prepared for these requests.
Collection Opt-OutCollection transparency
Scanner identifiers, collection schedules and the operational exclusion process will be published here before collection begins. The form currently available is a preview.
Trust & Transparency