Deep scan

Deep scans for your projects

Broader project coverage with passive checks first and bounded active checks. Project setup keeps deeper requests scoped to the intended origin and records what ran in the final coverage.

Choose the project

Start with the signed-in project and exact URL. LaunchLock checks current access before asking you to repeat ownership setup.

Approve the safe boundary

Deep access stays scoped to the selected project and exact origin with explicit consent controls.

Get the broader report

Allow more time for expanded route, service, and active-check coverage. The finished report adds the evidence and fixes found at that depth.

Start a Deep scan

LaunchLock checks the selected project and starts immediately when the required access is already available. If setup is needed, the ownership and consent steps appear below without losing your selected URL.

Owned projectNew project

Loading your projects…

What a Deep scan adds

Coverage: Quick coverage plus broader same-site route and service discovery, bounded active checks, and any configured project-specific tests that public passive scans cannot safely run.
Timing: Deep scans have a 15-minute hard scan budget. Duration depends on site size and completed coverage, and busy periods can add queue time before the run starts.
Coverage limits: Built-in checks run within the budget. ZAP and Nuclei are reported as skipped while guarded external-tool egress is disabled — they are never counted as passed when they did not run.
Safety: Active checks stay origin-scoped, bounded, rate-limited, and recorded in the scan coverage.

Every report lists what ran, what was skipped, and why — see the full check catalog or compare plans.

Loading deep scan…