One hunt.End to end.
Every test, verdict, and dropped false-positive flows through one engine toward a single result: a short list of validated, report-ready vulnerabilities. Here's exactly how a hunt runs.
Three steps. The rest is automated.
Pick
Enter a target you're authorized to test and choose the scope — web, API, mobile, source. Black, grey, or white box. The engine decides the methodology.
Hunt
HUNTR maps the attack surface, tests it class by class, and validates every finding — dropping the false positives before they ever reach you.
Send
Each finding arrives report-ready, reproduction and impact drafted. You review, decide, and submit. Nothing goes out without you.
Nothing off the radar.
HUNTR sweeps the whole attack surface — every host, endpoint, and parameter across web, API, auth and logic — lighting up what's real and dropping the noise.
A real methodology — not a single scan.
Map the surface
Enumerates hosts, endpoints, parameters, and auth flows — building the real attack surface before a single payload is sent.
58 vuln classes
Drives targeted tests across injection, access-control, auth, SSRF, logic, and client-side — chosen for the surface it found.
Drop the noise
Every candidate is re-proven before it counts. False positives are discarded so your queue is signal, not a scanner dump.
Report-ready
Reproduction steps and impact come written with each finding, in the format your program expects. You review and submit.