Can an automated scanner confirm every vulnerability?
An automated signal becomes a defensible finding only after validation of applicability, evidence and impact. LaunchProof keeps candidates, confirmed findings, false positives and retest outcomes separate.
What the engine observes
- Transparent public surface observations
- Deterministic normalization and deduplication
- Human escalation for high-impact conclusions
No product can guarantee to find every vulnerability. Active testing requires ownership verification, scope and explicit authorization.
What happens after a check?
Read the observations and their evidence first. Save the private report if useful. To go deeper, verify domain control and agree a precise scope, testing window and resource limits. High-impact candidates remain candidates until appropriate validation is complete.
Read verification policy ↗Related checks
Website security checker ↗Security headers checker ↗SSL & TLS checker ↗Content Security Policy checker ↗Cookie security checker ↗CORS signals checker ↗