> 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/es/web-vulnerabilities/proxys-squid-attack/proxys-squid-techniques-pentesting-web.md).

# Técnicas de proxy Squid

## Proxies SQUID:

Si lanzamos un escaneo en el puerto 80, indica que está **filtrado** y no cerrado:

<figure><img src="/files/b3dc84627191eb18648e3d7496b88c98dc1fdf99" alt="" width="563"><figcaption></figcaption></figure>

### Método con FoxyProxy

Aquí está el sitio normal donde **no aparece nada**:

<figure><img src="/files/fc79eb6f9cd6538643b30e49b0c1ed780bd84541" alt="" width="560"><figcaption></figcaption></figure>

Creamos un nuevo proxy con la **IP de la máquina** y puerto **3128**:

<figure><img src="/files/4ad79cc51789cc643a56f1da0a429e8e772857f1" alt="" width="563"><figcaption></figcaption></figure>

Con **FoxyProxy**, aparece el contenido:

<figure><img src="/files/5ed988d5f0bfd08e5c171c22c896bfa8d6b61a05" alt="" width="563"><figcaption></figcaption></figure>

### Método en línea de comandos:

Enviamos con curl una solicitud al servidor web usando el proxy de la máquina a través del puerto **3128**:

<figure><img src="/files/97e45a6e814f7a0e10b3a38e6be9b163e118e9c8" alt="" width="562"><figcaption></figcaption></figure>

Si solicita **autenticación**, hazlo de la siguiente manera:

<figure><img src="/files/4114853d2cb93656836f6daaad38823650e04ef2" alt="" width="563"><figcaption></figcaption></figure>

## Reconocimiento de rutas (pasando por el proxy):

A veces, las **rutas solo aparecen** con el proxy, aquí tienes un ejemplo de cómo verlas:

```bash
gobuster dir -u http://192.168.71.131/ --proxy http://192.168.71.131:3128 -w /usr/share/SecLists/Discovery/Web-Content/directory-list-2.3-medium.txt -t 20

```

<figure><img src="/files/6d60fcb7014c5b8aa9cb5a469dfe7a3c80873357" alt="" width="563"><figcaption></figcaption></figure>

## Script de Python automatizado:

```python
#!/usr/bin/python3
import sys, signal, requests
def def_handler(sig, frame):
    print("/n/n[!] Saliendo.../n")
    sys.exit(1)
# Técnicas de proxy Squid
signal.signal(signal.SIGINT, def_handler)
main_url = "http://127.0.0.1"
squid_proxy = {'http': 'http://192.168.71.131:3128'}
def portDiscovery():
    common_tcp_port= {21, 22, 23, 25, 53, 80, 110, 111, 135, 139, 143, 443, 445, 993, 995, 1723, 3306, 3389, 5900, 8080, 8443, 8888, 5900, 6666, 6667, 6668, 6669, 7000, 10000, 32768, 32769, 32770, 32771, 32772, 32773, 32774, 32775, 32776, 32777, 32778, 32779, 49152, 49153, 49154, 49155, 49156, 49157, 49158, 49159, 49160, 49161, 49162}
    for tcp_port in common_tcp_port:
        r = requests.get(main_url + ':' + str(tcp_port), proxies=squid_proxy)
        if r.status_code != 503:
            print("/n[+] Puerto " + str(tcp_port) + "- ABIERTO")
if __name__ == '__main__':
    portDiscovery()

```

<figure><img src="/files/f1a92f09cdc79f21b4689341b77a8b50fbd71aa2" alt="" width="563"><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

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

```
GET https://hacking-notes.jord4n.pro/es/web-vulnerabilities/proxys-squid-attack/proxys-squid-techniques-pentesting-web.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
