# Gobuster

### Web Enumeration

```bash
gobuster dir -u http://example.com -w wordlist.txt -x php,txt,html -t 80
```

> `dir` Indica que se realizará un ataque de enumeración de directorios.
>
> `-u` <http://example.com>: Especifica la URL objetivo que se va a enumerar
>
> `-w` wordlist.txt: Indica que se utilizará el archivo wordlist.txt
>
> `-x` php,txt: Especifica las extensiones de archivo que se probarán durante el ataque.
>
> > En este caso, Gobuster intentará enumerar directorios con extensiones .php y .txt.
>
> `-t` Hilos a utilizar

### Sub-Domain Enumeration

```bash
gobuster vhost -u http://example.com -w wordlist.txt --append-domain -t 100
```

> `vhost` Utiliza VHOST para la fuerza bruta
>
> `-w` Ruta a la lista de palabras
>
> `-u` Especifica la URL
>
> `--append-domain` Para añadir el dominio base
>
> `-t` Hilos a utilizar

### Proxy

```
gobuster dir -u http://example.com -w wordlist.txt -x php,txt,html --proxy socks5://127.0.0.1:1080
```

> `--proxy socks5` Especifica el proxy a utilizar


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://eldeim.gitbook.io/brain_fuck/notes/others/tools/gobuster.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.