SOCKS5 Protocol Guide
Overview
SOCKS5 proxies support any TCP/UDP traffic, not just HTTP. Use SOCKS5 for:
- Non-HTTP applications (email, FTP, gaming)
- UDP traffic (DNS, VoIP)
- Applications that need raw socket connections
Connection Details
| Setting | Value |
|---|---|
| Host | proxy.iploop.io |
| Port | 1080 |
| Username | customer-YOUR_ID-cc-XX |
| Password | YOUR_API_KEY |
Python Example
import requests
proxies = {
"http": "socks5h://customer-YOUR_ID-cc-US:[email protected]:1080",
"https": "socks5h://customer-YOUR_ID-cc-US:[email protected]:1080"
}
response = requests.get("https://ip.iploop.io/location", proxies=proxies)
print(response.json())
Use
socks5h:// (with 'h') to resolve DNS through the proxy. Use socks5:// for local DNS resolution.Node.js Example
const { SocksProxyAgent } = require("socks-proxy-agent");
const agent = new SocksProxyAgent(
"socks5://customer-YOUR_ID-cc-US:[email protected]:1080"
);
const response = await fetch("https://ip.iploop.io/location", { agent });
console.log(await response.json());
cURL Example
curl --socks5-hostname proxy.iploop.io:1080 \ --proxy-user "customer-YOUR_ID-cc-US:API_KEY" \ https://ip.iploop.io/location
SOCKS5 vs HTTP Proxy
| Feature | HTTP Proxy | SOCKS5 Proxy |
|---|---|---|
| Protocol support | HTTP/HTTPS only | Any TCP/UDP |
| Speed | Faster (less overhead) | Slightly slower |
| DNS resolution | Client-side | Proxy-side (socks5h) |
| Use case | Web scraping, APIs | Non-HTTP apps, full tunnel |