A web vulnerability scannerthat proves what it finds.
Point it at a URL or a repo. Agents test your web app and APIs like an attacker,
then hand you validated findings and the pull request that fixes them.
What a web vulnerability scanner should do
What gets tested
Full coverage of the web and API attack surface, authenticated where it matters.
OWASP Top 10 and beyond
Injection, broken access control, SSRF, insecure deserialization, misconfiguration, and the logic flaws no list covers.
REST and GraphQL APIs
Agents read schemas and traffic, then probe authorization, object references, rate limits, and mutation abuse.
Authenticated scans
Log in with real accounts and roles to test what is behind the login, including privilege boundaries between users.
Attack chains
A low-severity leak plus a weak check becomes account takeover. Agents chain steps the way an attacker would.
Source-aware when you connect a repo
Connect GitHub and agents read the code while attacking the running app, so coverage goes deeper than black-box alone.
Free retest after the fix
Merge the fix and agents replay the exact exploit to confirm it is closed.
Built for engineers, not report readers
Sign up with GitHub, connect a domain, and get results the same day.
Proof of exploit on every finding
The exact request, response, and reproduction steps, so you never argue about whether it is real.
Fix PRs, not remediation text
Validated findings arrive as merge-ready pull requests that fit your existing review flow.
Continuous or one-time
Run a one-time pentest today, or put agents on every pull request and deploy with the continuous platform.
Web vulnerability scanner vs Strix
How a signature-based scanner compares to agents that exploit and validate.
Strix
Typical web scanner
Strix
Typical web scanner
Strix
Typical web scanner
Strix
Typical web scanner
Strix
Typical web scanner
Strix
Typical web scanner
Strix
Typical web scanner
Strix
Typical web scanner
Strix
Typical web scanner
From issue to fix in seconds
Find critical issues, auto-validate, and auto-fix with merge-ready PRs.
SSRF via URL Parameter in /api/proxy
TL;DR
The /api/proxy endpoint accepts a user-supplied URL without validation. An attacker can access internal services, read cloud metadata, and exfiltrate credentials.
Impact
Access to cloud metadata at 169.254.169.254, potential credential theft, and internal network scanning.
Location
Severity
CVSS
8.6Fix Effort
LowDiscovered
2h agoDiscover & Validate
Pentests your entire attack surface continuously. Reproduces each finding, confirms exploitability with proof, and prioritizes by real impact.
How do I fix it?
Validate and restrict the target URL using an allowlist of permitted hostnames. Reject private/internal IP ranges and enforce HTTPS-only.
| 23 | 23 | const targetUrl = req.query.url; |
| 24 | const resp = await fetch(targetUrl); | |
| 24 | const parsed = new URL(targetUrl); | |
| 25 | if (!ALLOWED_HOSTS.has(parsed.hostname)) { | |
| 26 | throw new ForbiddenError("blocked"); | |
| 27 | } | |
| 28 | const resp = await fetch(parsed.href); | |
| 25 | 29 | return res.json(await resp.json()); |
Auto-Fix
Generates a fix, retests to confirm the vulnerability is gone, and delivers a merge-ready PR. Review, merge, done.
Frequently asked questions
Common questions about web and API vulnerability scanning.
Keep exploring
Solutions
Start testing in minutes
Scan your web app and APIs, get proven findings and fix PRs. Free to start.


