whatportis.com
suggest an edit →

Port 3128Squid Proxy HTTP

Port 3128 is commonly used by proxy servers, notably Squid, for handling HTTP web caching and proxy services. It enables improved web performance by caching frequently accessed content and provides anonymity and filtering capabilities for clients accessing the internet through the proxy..

inWeb ServicesSecurityNetwork Services
transport
tcp

single transport

in transit
cleartext

payload readable on path

assignment
unofficial

used by convention

risk
4/10

caution

lookups
45,832

rank 24 of 993 · top 2%

1 other service is registered on port 3128. compare all 2 →

Technical Details

what runs on :3128

Port 3128 is widely associated with the Squid proxy server, an open-source caching and forwarding HTTP proxy. It facilitates intermediate relaying and caching of website content requested by clients, which optimizes bandwidth usage and improves response times by serving cached data for repeated requests.

Squid running on port 3128 primarily intercepts HTTP requests, acting on behalf of the client to retrieve data from servers or deliver cached content. This provides several benefits such as reduced latency, efficient utilization of network resources, and centralized control over internet access. IT administrators often deploy Squid proxies to enforce content filtering, logging, or breadcrumb tracing for network activity.

While port 3128 is the default for Squid, it can be reconfigured, and multiple proxies may utilize this port owing to its ubiquity. Its operation is layer 7 (application layer) focused and primarily over TCP. The port does not natively handle Datagram-based protocols or stream control transmission, being optimized for reliable HTTP-based traffic over TCP connections.

Security Information

exposure of :3128

risk score

4/ 10caution

worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.

web services averages 3.9 across 112 ports — this one sits 0.1 above.

in transit

cleartext

credentials and payloads are readable by anyone on path

assignment

unofficial

used by convention, not registered — what answers here varies by deployment

reachable over

tcp

every listening transport is another surface to filter at the edge

security overview

Common vulnerabilities:

  • Open or misconfigured proxies on port 3128 can become open relays, allowing unauthorized users to proxy their traffic through vulnerable systems, which can lead to abuse such as spam or illegal activities.
  • Proxy servers may succumb to HTTP header injection, cache poisoning, or man-in-the-middle attacks if SSL interception is improperly handled.
  • Lack of authentication on the proxy opens avenues for anonymous usage and hiding malicious traffic origins.

Mitigations:

  • Implement strict access controls and authentication to limit proxy usage to authorized clients only.
  • Regularly audit proxy configurations to prevent open relay behavior and enforce content filtering policies.
  • Enable encryption (such as SSL/TLS termination) where applicable and monitor traffic patterns for anomalies.
  • Keep Squid and operating systems patched to reduce exposure to known vulnerabilities.
  • Employ network segmentation and firewall rules to restrict external access to port 3128, limiting proxy use to internal users or trusted IPs only.

Related Ports

all 112 in web services →

the 8 most looked-up other ports in web services — 112 ports carry that label.

portservicerisk
:8888Sun Answerbook & Alt HTTPcaution
:8000Intel Remote Desktop / Alternate HTTP Portsafe
:8888NewsEDGEcaution
:8888HTTP Alternative Portcaution
:8888GNUmp3d Streaming HTTPcaution
:9080Groove RPCcaution
:8881Atlasz Secure Servercaution
:80HTTPcaution

risk mix of the 8 listed

  • safe13%
  • caution88%

0 of 8 encrypted