> 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/reconnaissance/web-fuzzing.md).

# Web Fuzzing

Web fuzzing methodology for discovering hidden directories, files, extensions, parameters, and exposed resources with tools such as Gobuster and Wfuzz.

Web fuzzing helps discover hidden directories, files, extensions, parameters, virtual hosts, and exposed resources during web application reconnaissance.

{% hint style="info" %}
There are many tools and methods for discovering directories and files on websites, either from the command line or through online resources. Here are the main approaches and the most useful tools:
{% endhint %}

## Gobuster:

> Gobuster is a fast and effective tool for performing brute force attacks on website directories and files.

### **Directories only:**

```bash
gobuster dir -u http://website.com/ -w /usr/share/SecLists/Discovery/Web-Content/directory-list-2.3-medium.txt -t 100
```

* **-u**: URL of the target site.
* **-w**: Path of the file containing the list of keywords (wordlist).
* **-t**: Number of threads used for searching.

### **Files with specific extensions:**

```bash
gobuster dir -u http://website.com/ -w /usr/share/SecLists/Discovery/Web-Content/quickhits.txt -t 100 -x html,php,txt
```

* **-x**: Specifies the extensions to search for.

### **Add specific filters to responses:**

* **-hh**: Filter by body size in bytes.
* **-hc**: Excludes responses with specific status codes (for example, 404).

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-4c25811e9b3a61359a8c49bca7ff28b2066fff21%2Fimage%20(1080).png?alt=media" alt=""><figcaption></figcaption></figure>

## Wfuzz:

> Wfuzz allows for advanced and configurable searches via brute force attacks, whether for directories or parameters in URLs.

### **Directories only:**

```bash
wfuzz -c -t 100 -w /usr/share/SecLists/Discovery/Web-Content/directory-list-2.3-medium.txt http://website.com/FUZZ
```

* **-c**: Shows output in color.
* **FUZZ**: Indicates where the keywords will be injected.

### **Files with specific extensions:**

```bash
wfuzz -c -t 100 -w /usr/share/SecLists/Discovery/Web-Content/quickhits.tx -z list,html-txt-php http://website.com/
```

* **-z**: Defines additional extensions to use in the search (list allows you to define multiple extensions).

### **Dynamic parameter values ​​(`?product_id=`) :**

```bash
wfuzz -c -t 100 -z range,1-200000 'http://website.com/shop/buy/detail?product_id=FUZZ'
```

* **-z range,1-200000**: Performs a brute force attack with a number range of 1 to 200,000.

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-ae48da319b179a5ff00e8c89406ae1c210dcfbc1%2Fimage%20(1079).png?alt=media" alt=""><figcaption></figcaption></figure>

## **Additional Methods:**

### Public-source discovery:

If you prefer visual public-source methods, use the maintained catalog in [OSINT and Research Tools](/hacking-tools/osint.md).


---

# 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/reconnaissance/web-fuzzing.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.
