SOCKS5
SOCKS version 5Best for: Apps that are not browsers
- Connect, from You
- Any bytes, from You
- Reply, from Internet
Compare protocols
Best for: Apps that are not browsers
Best for: Filtering and caching web use
An HTTP proxy understands web requests: it can cache, filter and log plain HTTP, and tunnels HTTPS with the CONNECT method. A SOCKS5 proxy does not read the traffic at all. It just relays any TCP connection, and UDP too, for any app. Neither one encrypts your traffic by itself.
Tick everything that is true for you.
Your pick shows here
Tick one or more lines and we weigh them for you.
| What differs | SOCKS5 | HTTP proxy |
|---|---|---|
| Traffic it carries | Any TCP, plus UDP (UDP ASSOCIATE) | HTTP, and HTTPS through CONNECT |
| Reads the content | No | Plain HTTP yes; HTTPS no |
| Caching and URL filtering | No | Yes, for plain HTTP |
| Common ports | 1080 | 3128 and 8080 |
| Login | Username and password (RFC 1929) | Proxy-Authorization header, after a 407 reply |
| Encryption | None of its own | None of its own |
| Name lookups | Client or proxy can resolve the name | The proxy resolves the host name |
| Standard | RFC 1928 | RFC 9110 (CONNECT method) |
Each page plays the real packets on a map, step by step, with every header explained.
Each line describes one of the two. Which one?
Question 1 of 7
Traffic it carries
Any TCP, plus UDP (UDP ASSOCIATE)
Neither encrypts traffic. Safety comes from using HTTPS or another encrypted protocol inside the proxy, and from trusting whoever runs it.
No. A VPN usually covers all traffic from the device and encrypts it. A SOCKS5 proxy only carries apps set to use it, and it does not encrypt.
SOCKS5 does less work because it never reads the content. An HTTP proxy can be faster for repeat downloads when it serves them from its cache.
It asks an HTTP proxy to open a raw TCP tunnel to a host and port. Browsers use it for HTTPS, so the proxy passes the encrypted bytes without reading them.