> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/hacking-tools/web.md).

# Web Application Testing Tools

Web application testing tools and resources for proxy workflows, SQL injection automation, web vulnerability scanning, fuzzing, profiling, payload research, and WAF bypass support.

Use this category for web application testing workflows: proxying traffic, validating injection points, scanning web modules, discovering hidden content, profiling technologies, researching payloads, and reviewing WAF behavior.

## Tools and Resources

<table data-view="cards" data-full-width="false" data-search="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-bug" style="color:$primary;">:bug:</i></h3></td><td><h4>Burp Suite</h4></td><td>Burp Suite web penetration testing notes for Proxy interception, Repeater validation, Intruder automation, Comparer analysis, HTTP request manipulation, payload testing, authentication testing, vulnerability confirmation, and evidence collection.</td><td><a href="/hacking-tools/web/burpsuite.md">Burp Suite</a></td></tr><tr><td><h3><i class="fa-database" style="color:$primary;">:database:</i></h3></td><td><h4>SQLMap</h4></td><td>SQLMap penetration testing notes for SQL injection detection, DBMS fingerprinting, database enumeration, table and column discovery, data dumping, cookie-based testing, risk and level tuning, OS shell workflows, SQLite testing, and manual SQL injection validation.</td><td><a href="/hacking-tools/web/sqlmap.md">SQLMap</a></td></tr><tr><td><h3><i class="fa-shield-halved" style="color:$primary;">:shield-halved:</i></h3></td><td><h4>PHP Security Scanner</h4></td><td>Subscriber-only PHP static analysis workflow for dangerous functions, source-to-sink review, unsafe configuration, upload risk, deserialization, SSRF, and privilege escalation indicators.</td><td><a href="/hacking-tools/web/php-security-scanner.md">PHP Security Scanner</a></td></tr><tr><td><h3><i class="fa-globe" style="color:$primary;">:globe:</i></h3></td><td><h4>WMAP</h4></td><td>WMAP notes for running web vulnerability scans through Metasploit and reviewing discovered application issues.</td><td><a href="/hacking-tools/web/wmap-scan-web-vulnerabilities.md">WMAP Web Vulnerability Scanning</a></td></tr><tr><td><h3><i class="fa-globe" style="color:$primary;">:globe:</i></h3></td><td><h4>Web Recon and Bypass Resources</h4></td><td>Web reconnaissance and bypass resources for fuzzing, profiling, payload references, WAF detection, WAF bypass, and HackTricks web utilities.</td><td><a href="/hacking-tools/web/web-recon-and-bypass-resources.md">Web Recon and Bypass Resources</a></td></tr></tbody></table>

### Workflow

1. Profile the application and discover hidden content before running heavier checks.
2. Capture representative requests in Burp Suite and confirm parameter behavior manually.
3. Use SQLMap or WMAP only when the target behavior supports that testing path.
4. Research payloads, bypasses, and WAF behavior in the dedicated resources page.
5. Keep exact requests, payloads, responses, screenshots, and tool versions for reporting.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hacking-notes.jord4n.pro/hacking-tools/web.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.