REDSPARTAHOW IT WORKS
A clear path
from findings to fixes.
Define your scope, inspect the evidence and check your changes with focused web application scans.
Get startedFor applications you own or are authorized to test.
Define your scope
Choose your domain, set exclusions and add a dedicated test account when you need to assess pages behind a login.
Run a focused scan
Start the scan with your chosen configuration. Follow its progress as checks run.
See the evidence.
Inspect severity, affected URLs and observed evidence. Use the remediation guidance to plan a correction.
Apply your fix.
Make the correction in your application, then run a focused retest and review the new evidence.
Keep the evidence.
Export results as PDF, JSON, CSV or SARIF.
Before your first scan
Can I test pages behind a login?
Yes. Add dedicated test credentials for the pages you are authorized to assess. The pages reached depend on the login flow, permissions and scan scope.
What affects credit usage?
Usage depends on scan configuration, page count and authentication. An estimate is reserved at launch, then adjusted to actual scan usage. Scan counts shown in plans are estimates, not guaranteed allowances.
Does a clean scan mean my app is secure?
No. Automated checks describe what was observed within the tested scope. Review coverage limits and use a human assessment when more depth is needed.