Tiers
- Lite
- Comprehensive
- Max
- Retest
Lite
Free-tier checks: passive, read-only, no domain verification needed.
Safe, read-only checks. Nothing to set up first.
- TLS/SSL configuration
- CORS misconfiguration
- Exposed source maps
- Insecure deserialization
- Cleartext credentials & weak tokens
- Missing CSRF protection
- Security headers
- Directory listing & CAPTCHA exposure
- Exposed secrets in JS/CSS
- Exposed password hashes
- Session fixation
- Dangerous HTTP methods enabled
- Missing SRI & mixed content
- Dependency CVE check
- Subdomain takeover
- Verbose error/stack-trace disclosure
- How securely your site encrypts traffic
- Whether other websites can improperly read your site's data
- Whether your original source code is accidentally public
- Whether your site unsafely trusts incoming data
- Whether passwords or login tokens are sent unprotected
- Whether forms can be tricked into acting without permission
- Whether standard browser security settings are turned on
- Whether folders or CAPTCHA answers are accidentally exposed
- Whether API keys or passwords are hidden in your site's code
- Whether password data is accidentally visible
- Whether an old login session can be reused by someone else
- Whether your server allows risky actions it shouldn't
- Whether outside scripts could be tampered with, or secure pages load insecure content
- Whether your site uses software with known security flaws
- Whether an abandoned subdomain could be hijacked
- Whether error messages reveal more than they should
Comprehensive
Lite, plus active scanning and every paid-tier check this install supports.
Everything in Lite, plus deeper tests that actively try to find real weaknesses.
- Everything in Lite
- SQL injection, XSS, command injection
- SSRF to cloud metadata services
- NoSQL injection
- Prototype pollution
- JWT attacks
- GraphQL attacks (introspection, DoS, CSRF)
- Content & directory discovery
- IDOR & broken access control
- Login brute-force check
- DOM-based XSS
- File upload bypass
- Business-logic / price tampering
- Weak or sequential session IDs
- Blind XXE
- Template-based vulnerability scanning
- Session not invalidated on logout
- Race conditions & missing idempotency
- Open redirect
- Everything in Lite
- Attempts to manipulate your database, inject malicious code, or run commands on your server
- Whether your server can be tricked into fetching sensitive internal data
- Database manipulation attacks against non-SQL databases
- A JavaScript-specific attack that can corrupt how your app behaves
- Weaknesses in how your site recognizes logged-in users
- Weaknesses in your site's API
- Hidden pages or files an attacker could find
- Whether one user can see or change another user's data
- Whether your login page blocks repeated password guessing
- Malicious code that runs inside a visitor's browser
- Whether dangerous file types can be uploaded
- Whether prices or quantities can be manipulated
- Whether login sessions are easy to guess
- A hidden attack through how your site reads XML files
- Checks against a library of known vulnerabilities
- Whether logging out actually ends your session
- Whether an action can be repeated to cheat the system, like redeeming a coupon twice
- Whether your site can be used to redirect visitors somewhere malicious
Max (coming soon)
Not available yet. Everything in Comprehensive, plus an AI scanner-and-validator swarm that actively investigates your site beyond a fixed checklist.
- Everything in Comprehensive
- AI-driven exploration of your attack surface, not limited to a fixed checklist
- Multi-step, chained-vulnerability reasoning a mechanical scanner can't do
- Findings independently re-checked by a validator pass before being reported
- Human approval required before any exploit-class action
Retest
Re-run only the check types that found something in a prior run, and diff against it.
No fixed checklist of its own: it inherits whichever Lite or Comprehensive checks that earlier run used, then shows what's resolved, new, or still open.
Why this matters
Average cost of a data breach
Days, on average, to identify and contain a breach
How long after a vulnerability is disclosed before attackers start scanning for it
Year-over-year growth in vulnerability exploitation as a breach entry point