Testing guides
How to test the classes that pay
Each guide is the method I actually use: how to confirm the flaw, what to send, how to prove the impact, and where the cheap false positives come from. Published in full, because the method should be visible before anyone pays for it.
Written for pentesters and bug-bounty hunters, tested with Hugin
How to test for HTTP request smuggling
Request smuggling is a disagreement between two servers about where one request ends and the next begins. It is high-impact and easy to test for, if you know what to look for. This is the practical method, not the theory.
6 stepsHow to test for race conditions in web apps
A race condition is only exploitable if your requests land inside the same tiny window. Sending them one after another rarely works. This is how to collapse the window and turn "unexploitable" check-then-act logic into a proven finding.
5 stepsHow to test for blind SSRF
Most SSRF is blind. The server makes the request but never shows you the response. You cannot see it in the body, so you have to make the server call something you control. This is how.
5 stepsHow to test broken access control and IDOR
Broken access control is the most common high-impact bug class, and the one scanners handle worst, because it depends on what the app is supposed to allow. The method is systematic: two accounts, replay, compare.
5 stepsA bug bounty methodology that finds bugs
Most time lost on a target is lost before the first useful request, to poor scope reading and shallow mapping. This is the discipline that moves findings: scope, map, hypothesise, prove, then report.
6 stepsApply the method to your code
Hugin
The proxy and scanner I use daily. Community is free, one Rust binary, no account. Pro is €10/month when you want the offensive tier.