DAST
Strike (Live app testing) tests your live application for SQL injection, XSS, SSRF, auth bypass, CORS misconfiguration and known CVEs. Choose a quick, standard or deep scan, scan behind a login, and get AI fix guidance on what it finds.
What DAST finds
Error-based injection probes against discovered parameters and forms.
Reflected and DOM-based XSS probes that use a harmless marker, not a script payload.
SSRF probes with out-of-band DNS and HTTP callback detection on deep scans.
Header-injection bypass attempts and HTTP method checks on protected paths.
Overly permissive origin policies and credential-sharing misconfigurations.
Missing HSTS, CSP, X-Frame-Options and other response headers, plus cookie attributes.
Certificate validity and TLS configuration checks.
Template-based checks for known CVEs, exposed panels, default credentials and subdomain takeover.
DNS and HTTP interaction monitoring for blind vulnerabilities.
From URL to findings
- 1
Pick a target and depth
Choose a target you have verified you own and a scan depth: quick (about 2 minutes), standard (about 10 minutes) or deep (about 30 minutes).
- 2
Crawl and map
Spoorder crawls the application to discover pages, forms and endpoints, including areas behind a login when you supply credentials.
- 3
Active testing
Test payloads are sent to the discovered endpoints at the scan speed you choose. The scan log updates live while it runs.
- 4
Findings with evidence
Each finding carries its evidence, CWE and OWASP category. AI fix guidance can be generated per finding.
GET /api/users?id=1' OR '1'='1 HTTP/1.1
Host: target.example.com
Authorization: Bearer eyJ...Spoorder DAST vs a stand-alone scanner
| Criterion | Spoorder | a stand-alone scanner |
|---|---|---|
| Progress | Live scan log while the scan runs | Report after the scan completes |
| Remediation | AI fix guidance per finding | Reference link only |
| Compliance mapping | Findings mapped to framework controls | Separate manual step |
| Authenticated scanning | Bearer token, cookie, basic, API key, form login or client certificate | Often manual setup |
How does Spoorder DAST differ from a penetration test?
DAST is automated and repeatable, and a scan finishes in minutes. A pentest is manual, performed by a person, and usually runs over days. DAST gives you baseline coverage between manual assessments.
Will DAST scanning affect my production application?
DAST sends real HTTP requests to your application. For production, use the Safe scan speed (10 requests per second) and leave the Active Testing category off, because active testing sends real injection payloads and should only run with the system owner's permission. Scans run only against targets you have verified you own.
Can I scan authenticated endpoints?
Yes. Supply a bearer token, a session cookie, basic auth credentials, an API key header, a form login or a client certificate. Spoorder uses it for the whole scan so that pages behind the login are tested too.
How many credits does a DAST scan cost?
15 credits per DAST scan. The health check costs no credits.
What output formats are supported?
Findings are available in the dashboard and through the REST API as JSON. Each scan has a printable report you can save as PDF, and the sprdr CLI can export findings as SARIF.
Can I schedule DAST scans?
Yes. DAST scans can run daily, weekly or monthly per target. Builder includes 5 scheduled scans; Pro and above have no limit.
Start scanning
Start with a free health check. DAST is included from Builder ($69/mo).