Port 3128/tcp: Squid HTTP Proxy (de facto; registered as ndl-aas)
Category: Web & Application. Range: registered. Status: de facto standard.
What runs here
Port 3128/tcp is the long-standing default listening port for the Squid caching web proxy, adopted in the 1990s and still Squid's out-of-the-box http_port default today. Its actual IANA registration, however, is for an unrelated service, ndl-aas (an Active API Server port); 3128 became the proxy convention purely through Squid's own defaults and widespread adoption, never a formal IANA proxy assignment.
Why it matters
Traffic to 3128 overwhelmingly means an HTTP forward proxy is in use, which cuts both ways for DFIR: it is how organizations legitimately enforce web filtering and logging, and it is also a common pivot mechanism attackers abuse. An open or misconfigured proxy lets an outside actor relay traffic through it, and an internal host reaching an unauthorized external proxy on 3128 can indicate an attempt to bypass egress or DNS controls.
Where you see it
Legitimately: corporate or ISP web proxy egress, cached web browsing through a Squid deployment. Anomalously/maliciously: an open or misconfigured Squid proxy abused by outside actors to relay traffic and mask source IP, an internal host configured to reach an unauthorized external proxy to evade filtering, or attacker infrastructure running a proxy on 3128 as part of a redirector chain.
What to look for
| Signal | What it means |
|---|---|
| CONNECT method usage | An HTTP CONNECT request tunneling arbitrary TCP, commonly to port 443, is the key thing to inspect; it reveals the true destination the proxy is relaying to. |
| Proxy-Authorization header | Presence and validity of proxy authentication helps distinguish sanctioned use from open-proxy abuse. |
Related ports
- 80/tcp: HTTP (Hypertext Transfer Protocol)
- 443/tcp: HTTPS (HTTP over TLS/SSL)
- 1080/tcp: SOCKS Proxy
- 8080/tcp: HTTP Alternate (http-alt)