Each domain maps to established OWASP testing categories. Findings are returned with severity, evidence, affected endpoint, and remediation context.
The scan mode determines which parts of the application are reachable. Authenticated scans significantly expand coverage into protected areas that anonymous scanning cannot reach.
No credentials required
Tests the application surface reachable without authentication — ideal for an initial exposure assessment or verifying your public-facing security posture.
Deeper coverage behind login
Logs into the application using supplied credentials, then crawls and tests protected areas — surfacing access control, session, business logic, and API findings that an unauthenticated scan cannot reach.
Every finding is structured so engineers can reproduce, triage, and fix issues without needing a dedicated AppSec specialist to interpret the output.
Findings are classified as Critical, High, Medium, Low, or Informational — enabling teams to fix the highest-risk issues first without guesswork.
Each finding is tagged by security category (e.g. Injection, Headers, Auth) and linked to the specific asset and endpoint where it was detected.
Findings indicate whether they were discovered during a public or authenticated scan, clarifying scope and reproducing steps.
Each finding includes a short explanation of the risk and a remediation direction developers can act on without cross-referencing external documentation.
The dashboard surfaces findings over time across scan runs, showing new issues, resolved findings, and overall security posture trends.
View findings grouped by host or asset — useful for teams with multiple properties or environments running parallel scan programs.
A quick reference for what Vuln Pro Scan exercises across your application surface.
| Domain | Public scan | Auth scan | Key examples |
|---|---|---|---|
| Attack surface mapping | ✓ | ✓ | Admin panels, directory listings, verbose banners |
| Configuration issues | ✓ | ✓ | CORS, HTTP methods, debug endpoints |
| Authentication weaknesses | ✓ | ✓ | Rate limiting, enumeration, weak policy |
| Authorization & IDOR | — | ✓ | Horizontal privilege, missing function guards |
| Session management | ✓ | ✓ | Cookie flags, CSRF, session fixation |
| XSS / SQLi / Injection | ✓ | ✓ | Reflected, stored, DOM, blind SQLi |
| Sensitive data exposure | ✓ | ✓ | Stack traces, API keys in responses |
| Security headers | ✓ | — | CSP, HSTS, X-Frame-Options, Referrer-Policy |
| TLS & transport | ✓ | — | Weak ciphers, TLS 1.0/1.1, mixed content |
| API security | ✓ | ✓ | Unauthed endpoints, GraphQL introspection |
| Client-side security | ✓ | ✓ | DOM XSS, SRI missing, clickjacking |
| Business logic | — | ✓ | Mass assignment, workflow bypass |
Try a demo scan in minutes — no agents, no instrumentation. After you sign in with approved access, use the full product for authenticated scanning and deeper coverage.