SOCKS - Socket Secure
What is SOCKS?
SOCKS stands for Socket Secure. It is a network protocol that routes network packets between a client and a server through a proxy server, allowing applications to bypass firewalls, hide IP addresses, or access restricted content. Unlike HTTP proxies, SOCKS is protocol-agnostic and works at a lower level.
Why is SOCKS useful?
Supports any type of traffic (HTTP, FTP, SMTP, etc.)
Works with TCP and UDP
Doesn’t interpret or modify the data being transferred
Helps with anonymity, firewall traversal, and geo-unblocking
How it works?
Client connects to SOCKS server – The application is configured to use a SOCKS proxy.
SOCKS server establishes connection – It opens a connection to the target server on behalf of the client.
Data is relayed – The SOCKS server forwards data between the client and the destination without inspecting it.
Connection ends – Once the session is complete, the proxy closes the connection.
Where is SOCKS used?
Torrenting and P2P apps – For anonymous and unrestricted access
Bypassing censorship – In restricted networks or countries
Gaming – To reduce latency or access region-locked servers
Secure tunneling – Often used with SSH for encrypted proxying
Why OSI Layer: Session Layer (Layer 5)?
It manages sessions between applications across networks
It is protocol-independent, unlike HTTP proxies
It establishes and maintains end-to-end connections for any type of traffic
Topics in this section,
In this section, you are going to learn
Terminology
Version Info
SOCKS |
RFC |
Year |
Core Idea / Contribution |
|---|---|---|---|
Version |
|||
SOCKS4 |
|||
Informal (no RFC) |
~1992 |
Introduced basic TCP proxying through firewalls. No authentication or UDP support. Developed by David Koblas at MIPS. |
|
SOCKS4a |
|||
Informal (no RFC) |
~1993 |
Extension of SOCKS4 to support domain name resolution by the proxy |
|
server. |
|||
SOCKS5 |
|||
RFC 1928 |
1996 |
Added support for authentication, UDP proxying, and IPv6. Designed as a general framework for secure client-server communication through firewalls . |
setup
setup
Client Greeting Packet
S.No |
Protocol Packets |
Description |
Size(bytes) |
|---|---|---|---|
1 |
Client Greeting |
Client initiates connection and lists supported authentication methods |
~3258 |
Version |
SOCKS version (0x05 for SOCKS5) |
1 |
|
Number of Methods |
Number of authentication methods supported |
1 |
|
Methods |
List of supported methods (e.g., 0x00 = No Auth, 0x02 = Username/Password) |
1-255 |
|
Server Method Selection Packet
S.No |
Protocol Packets |
Description |
Size(bytes) |
|---|---|---|---|
2 |
Server Method Selection |
Server selects an authentication method |
2 |
Version |
SOCKS version (0x05) |
1 |
|
Method |
Selected method (e.g., 0x00 = No Auth) |
1 |
|
Authentication(if required) Packet
S.No |
Protocol Packets |
Description |
Size(bytes) |
|---|---|---|---|
3 |
Authentication (if required) |
Optional step if server requires authentication (e.g., username/password) |
~5512 bytes |
Version |
Auth version (0x01) |
1 |
|
Username Length |
Length of username |
1 |
|
Username |
Username string |
variable |
|
Password Length |
Length of password |
1 |
|
Password |
Password string |
variable |
|
Client Connection Request Packet
S.No |
Protocol Packets |
Description |
Size(bytes) |
|---|---|---|---|
4 |
Client Connection Request |
Client requests a connection to a target server |
~10262 bytes |
Version |
SOCKS version (0x05) |
1 |
|
Command |
0x01 = CONNECT, 0x02 = BIND, 0x03 = UDP ASSOCIATE |
1 |
|
Reserved |
Must be 0x00 |
1 |
|
Address Type |
0x01 = IPv4, 0x03 = Domain, 0x04 = IPv6 |
1 |
|
Destination Address |
IP or domain name |
variable |
|
Destination Port |
Destination Port |
2 |
|
Server Connection Reply Packet
S.No |
Protocol Packets |
Description |
Size(bytes) |
|---|---|---|---|
5 |
Server Connection Reply |
Server responds to the connection request |
~10262 bytes |
Version |
SOCKS version (0x05) |
1 |
|
Reply Code |
0x00 = Success, others = errors |
1 |
|
Reserved |
Must be 0x00 |
1 |
|
Address Type |
0x01 = IPv4, 0x03 = Domain, 0x04 = IPv6 |
1 |
|
Bound Address |
Server-bound address |
variable |
|
Bound Port |
Server-bound port |
2 |
|
Data Transfer Packet
S.No |
Protocol Packets |
Description |
Size(bytes) |
|---|---|---|---|
6 |
Data Transfer |
After connection is established, data is transferred directly (TCP) or via UDP relay |
|
TCP Stream |
Encrypted or plain data stream |
variable |
|
UDP Packet Header (for UDP ASSOCIATE) |
Reserved (2 bytes), Fragment (1 byte), Address Type (1 byte), Destination Address, Port, Data |
variable |
|
s.no |
Use Case |
Description |
|---|---|---|
1 |
Bypass Geo-restrictions |
SOCKS proxies allow users to access content restricted by geographic location by routing traffic through servers in permitted regions. |
2 |
Secure Remote Access |
SOCKS5 supports authentication and encryption, making it suitable for |
secure access to internal networks from remote locations. |
||
3 |
Torrenting / P2P Sharing |
SOCKS5 is often used with torrent clients to anonymize traffic and bypass |
ISP throttling or restrictions. |
||
4 |
Web Scraping |
SOCKS proxies help rotate IPs and avoid bans when scraping data from |
websites, especially those with anti-bot measures. |
||
5 |
Firewall Traversal |
SOCKS proxies can tunnel traffic through firewalls, enabling applications |
to communicate across restricted networks |
||
6 |
Gaming |
Used to reduce latency or bypass regional restrictions in online games by |
routing traffic through optimized proxy servers. |
||
7 |
Email Clients |
SOCKS proxies can be configured in email clients to securely |
send/receive emails through restricted networks. |
||
8 |
VoIP Services |
Helps in routing VoIP traffic through proxies to maintain connectivity in |
restricted or monitored environments. |
||
9 |
Corporate Network Segmentation |
SOCKS proxies are used to isolate and control traffic between different segments of a corporate network. |
10 |
Anonymity and Privacy |
SOCKS proxies mask the user’s IP address, enhancing privacy and |
reducing tracking across the internet. |
S.no |
Feature |
Description |
|---|---|---|
1 |
Protocol Agnostic |
SOCKS operates at a lower level than HTTP, allowing it to handle any type |
of traffic (HTTP, FTP, SMTP, etc.). |
||
2 |
Supports TCP and UDP |
SOCKS5 supports both TCP and UDP protocols, enabling broader |
application support including DNS and streaming. |
||
3 |
Authentication Support |
SOCKS5 includes support for username/password authentication, |
enhancing security. |
||
4 |
IP Address Hiding |
It masks the clients IP address, providing anonymity and privacy. |
5 |
Firewall Traversal |
Enables traffic to pass through firewalls and NAT devices without needing |
special configuration. |
||
6 |
Domain Name Resolution |
SOCKS5 can resolve domain names on the proxy server side, useful for |
bypassing DNS-based restrictions. |
||
7 |
No Content Inspection |
Unlike HTTP proxies, SOCKS does not inspect or modify the data, |
making it more transparent and flexible. |
||
8 |
IPv6 Support |
SOCKS5 supports IPv6, making it compatible with modern network infrastructures. |
9 |
Flexible Application Use |
Can be used with browsers, torrent clients, SSH, and more due to its |
general-purpose design. |
||
10 |
Lightweight and Fast |
Minimal overhead makes SOCKS proxies efficient for high-speed |
connections and real-time applications. |
Protocol Agnostic - Testcases
# |
Test Case |
Description |
Expected Result |
|---|---|---|---|
1 |
Connect HTTP via SOCKS |
Route HTTP traffic through SOCKS proxy |
HTTP request succeeds |
2 |
Connect HTTPS via SOCKS |
Route HTTPS traffic through SOCKS |
Secure connection established |
3 |
Connect FTP via SOCKS |
Route FTP traffic through SOCKS |
FTP session established |
4 |
Connect SMTP via SOCKS |
Route SMTP traffic through SOCKS |
Email sent successfully |
5 |
Connect IMAP via SOCKS |
Route IMAP traffic through SOCKS |
Email retrieved successfully |
6 |
Connect POP3 via SOCKS |
Route POP3 traffic through SOCKS |
Mailbox accessed |
7 |
Connect SSH via SOCKS |
Route SSH session through SOCKS |
SSH session established |
8 |
Connect Telnet via SOCKS |
Route Telnet session through SOCKS |
Telnet session established |
9 |
Connect DNS via SOCKS |
Route DNS queries through SOCKS |
DNS resolution succeeds |
10 |
Connect WebSocket via SOCKS |
Route WebSocket traffic |
WebSocket connection established |
11 |
Connect MQTT via SOCKS |
Route MQTT IoT protocol |
MQTT messages delivered |
12 |
Connect RTSP via SOCKS |
Stream video via RTSP |
Stream plays successfully |
13 |
Connect SIP via SOCKS |
Route VoIP traffic |
Call setup succeeds |
14 |
Connect BitTorrent via SOCKS |
Route P2P traffic |
Torrent downloads |
15 |
Connect IRC via SOCKS |
Route IRC chat |
Messages sent and received |
16 |
Connect NTP via SOCKS |
Route time sync requests |
Time synchronized |
17 |
Connect SMB via SOCKS |
Access shared files |
File listing succeeds |
18 |
Connect RDP via SOCKS |
Remote desktop session |
RDP session established |
19 |
Connect VNC via SOCKS |
Remote control via VNC |
VNC session established |
20 |
Connect LDAP via SOCKS |
Directory service access |
LDAP query succeeds |
21 |
Connect SNMP via SOCKS |
Network monitoring traffic |
SNMP data retrieved |
22 |
Connect ICMP via SOCKS |
Attempt to route ping (ICMP) |
Not supported (expected failure) |
23 |
Connect Custom TCP App via SOCKS |
Route custom TCP application |
App functions correctly |
24 |
Connect Custom UDP App via SOCKS5 |
Route custom UDP application (SOCKS5 only) |
App functions correctly |
25 |
Connect HTTP/2 via SOCKS |
Route HTTP/2 traffic |
Connection succeeds |
26 |
Connect gRPC via SOCKS |
Route gRPC traffic |
RPCs succeed |
27 |
Connect QUIC via SOCKS |
Attempt to route QUIC (UDP-based) |
Works only with SOCKS5 UDP support |
28 |
Connect WebRTC via SOCKS |
Route WebRTC signaling |
Signaling succeeds |
29 |
Connect VPN via SOCKS |
Route VPN tunnel |
Tunnel established |
30 |
Connect Tor via SOCKS |
Use SOCKS to access Tor network |
Onion routing succeeds |
31 |
Connect IoT Device via SOCKS |
Route IoT device traffic |
Device communicates successfully |
32 |
Connect Game Server via SOCKS |
Route online game traffic |
Game connects and plays smoothly |
33 |
Connect Cloud Storage via SOCKS |
Access cloud storage |
Files uploaded/downloaded |
34 |
Connect Git via SOCKS |
Clone/push Git repository |
Git operations succeed |
35 |
Connect Docker Registry via SOCKS |
Pull/push Docker images |
Registry access succeeds |
36 |
Connect Kubernetes API via SOCKS |
Access K8s API server |
API calls succeed |
37 |
Connect REST API via SOCKS |
Call RESTful service |
API response received |
38 |
Connect GraphQL API via SOCKS |
Call GraphQL endpoint |
Query/mutation succeeds |
39 |
Connect SOAP API via SOCKS |
Call SOAP web service |
Response received |
40 |
Connect Email Client via SOCKS |
Use email client with SOCKS |
Email sent and received |
41 |
Connect Browser via SOCKS |
Browse web through SOCKS proxy |
Pages load correctly |
42 |
Connect CLI Tool via SOCKS |
Use CLI tool (e.g., curl, wget) |
Tool works through proxy |
43 |
Connect Mobile App via SOCKS |
Route mobile app traffic |
App functions normally |
44 |
Connect Desktop App via SOCKS |
Route desktop app traffic |
App functions normally |
45 |
Connect API Gateway via SOCKS |
Route gateway traffic |
Gateway forwards requests |
46 |
Connect CDN via SOCKS |
Access content delivery network |
Content loads quickly |
47 |
Connect Analytics Service via SOCKS |
Send analytics data |
Data transmitted |
48 |
Connect Payment Gateway via SOCKS |
Process payment transaction |
Payment succeeds |
49 |
Connect Blockchain Node via SOCKS |
Sync blockchain data |
Node syncs successfully |
50 |
Connect AI Model API via SOCKS |
Call AI/ML inference API |
Prediction returned |
Supports TCP and UDP - Testcases
# |
Test Case |
Description |
Expected Result |
|---|---|---|---|
1 |
Establish TCP Connection via SOCKS5 |
Connect to a TCP server (e.g., HTTP) |
TCP handshake succeeds |
2 |
Establish UDP Association via SOCKS5 |
Initiate UDP association |
UDP relay address returned |
3 |
Send UDP Packet via SOCKS5 |
Send a UDP packet through proxy |
Packet delivered |
4 |
Receive UDP Packet via SOCKS5 |
Receive a UDP packet through proxy |
Packet received |
5 |
Send TCP Stream via SOCKS5 |
Stream data over TCP |
Data transmitted reliably |
6 |
Send UDP Stream via SOCKS5 |
Stream data over UDP |
Data transmitted with low latency |
7 |
Route DNS over UDP |
Send DNS query via UDP |
DNS response received |
8 |
Route DNS over TCP |
Send DNS query via TCP |
DNS response received |
9 |
Route HTTP over TCP |
Access website via TCP |
Page loads successfully |
10 |
Route VoIP over UDP |
Send VoIP packets |
Call quality maintained |
11 |
Route Video Stream over UDP |
Stream video via UDP |
Stream plays smoothly |
12 |
Route File Transfer over TCP |
Transfer file via FTP |
File uploaded/downloaded |
13 |
Route Chat App over TCP |
Use chat app through SOCKS |
Messages delivered |
14 |
Route Game Traffic over UDP |
Play online game using UDP |
Game runs with low latency |
15 |
Route IoT Sensor Data over UDP |
Send sensor data via UDP |
Data received at server |
16 |
Route Email over TCP |
Send/receive email via SMTP/IMAP |
Email delivered |
17 |
Route MQTT over TCP |
Publish/subscribe to MQTT broker |
Messages exchanged |
18 |
Route MQTT over UDP |
Use MQTT-SN (UDP-based) |
Messages exchanged |
19 |
Route NTP over UDP |
Sync time via NTP |
Time updated |
20 |
Route SSH over TCP |
Connect to SSH server |
Session established |
21 |
Route RDP over TCP |
Remote desktop session |
Session established |
22 |
Route VNC over TCP |
Remote control session |
Session established |
23 |
Route IRC over TCP |
Join IRC chat |
Messages exchanged |
24 |
Route SNMP over UDP |
Monitor network devices |
SNMP data retrieved |
25 |
Route TFTP over UDP |
Transfer file via TFTP |
File transferred |
26 |
Route SIP over UDP |
Initiate VoIP call |
Call setup succeeds |
27 |
Route SIP over TCP |
Use TCP for SIP signaling |
Call setup succeeds |
28 |
Route RTSP over TCP |
Stream media via RTSP |
Stream plays |
29 |
Route RTSP over UDP |
Stream media via UDP |
Stream plays |
30 |
Route WebRTC Signaling over TCP |
Use TCP for signaling |
Connection established |
31 |
Route WebRTC Media over UDP |
Use UDP for media |
Media transmitted |
32 |
Route QUIC over UDP |
Use QUIC protocol |
Connection established |
33 |
Route gRPC over TCP |
Use gRPC with HTTP/2 |
RPCs succeed |
34 |
Route DNSCrypt over UDP |
Encrypt DNS queries |
Secure DNS resolution |
35 |
Route DNS-over-HTTPS over TCP |
Use DoH protocol |
DNS resolved securely |
36 |
Route DNS-over-TLS over TCP |
Use DoT protocol |
DNS resolved securely |
37 |
Route Custom TCP App |
Use custom TCP protocol |
App functions correctly |
38 |
Route Custom UDP App |
Use custom UDP protocol |
App functions correctly |
39 |
Handle TCP Connection Timeout |
Simulate TCP timeout |
Connection closed gracefully |
40 |
Handle UDP Packet Loss |
Simulate UDP packet loss |
Packet dropped, no retransmission |
41 |
Handle TCP Retransmission |
Simulate TCP packet loss |
Retransmission occurs |
42 |
Handle UDP Fragmentation |
Send large UDP packet |
Packet fragmented and reassembled |
43 |
Handle TCP Congestion Control |
Simulate network congestion |
TCP adjusts rate |
44 |
Handle UDP Jitter |
Simulate jitter in UDP stream |
Stream quality degrades |
45 |
Use TCP Keepalive |
Enable keepalive on TCP connection |
Idle connection maintained |
46 |
Use UDP Heartbeat |
Send periodic UDP heartbeat |
Connection monitored |
47 |
Use SOCKS5 with TCP Only |
Disable UDP support |
UDP traffic blocked |
48 |
Use SOCKS5 with UDP Only |
Disable TCP support |
TCP traffic blocked |
49 |
Use SOCKS4 (TCP Only) |
Attempt UDP traffic |
UDP not supported, request fails |
50 |
Use SOCKS5 with TCP and UDP Simultaneously |
Route both TCP and UDP concurrently |
Both traffic types handled correctly |
Authentication support - Testcases
# |
Test Case |
Description |
Expected Result |
|---|---|---|---|
1 |
Enable Username/Password Auth |
Configure SOCKS5 server to require authentication |
Auth prompt triggered |
2 |
Connect with Valid Credentials |
Provide correct username and password |
Connection established |
3 |
Connect with Invalid Username |
Use incorrect username |
Authentication fails |
4 |
Connect with Invalid Password |
Use incorrect password |
Authentication fails |
5 |
Connect with Empty Username |
Leave username blank |
Authentication fails |
6 |
Connect with Empty Password |
Leave password blank |
Authentication fails |
7 |
Connect with No Credentials |
Attempt connection without credentials |
Authentication required |
8 |
Connect with Long Username |
Use long username string |
Auth succeeds if within limits |
9 |
Connect with Long Password |
Use long password string |
Auth succeeds if within limits |
10 |
Connect with Special Characters |
Use special characters in credentials |
Auth succeeds if encoded correctly |
11 |
Connect with Unicode Characters |
Use Unicode in credentials |
Auth succeeds if supported |
12 |
Connect with Expired Credentials |
Use expired user account |
Authentication fails |
13 |
Connect with Locked Account |
Use locked user account |
Authentication fails |
14 |
Connect with Disabled Account |
Use disabled user account |
Authentication fails |
15 |
Connect with Case-Sensitive Username |
Use different case in username |
Auth fails if case-sensitive |
16 |
Connect with Case-Sensitive Password |
Use different case in password |
Auth fails if case-sensitive |
17 |
Connect with Whitespace in Username |
Include spaces in username |
Auth fails or trims based on config |
18 |
Connect with Whitespace in Password |
Include spaces in password |
Auth fails or trims based on config |
19 |
Brute Force Attempt |
Attempt multiple logins with wrong credentials |
IP blocked or rate-limited |
20 |
Rate Limiting on Auth |
Exceed login attempts in short time |
Further attempts delayed or blocked |
21 |
Log Successful Auth |
Log successful login |
Entry recorded in logs |
22 |
Log Failed Auth |
Log failed login attempt |
Entry recorded in logs |
23 |
Audit Auth Events |
Review authentication logs |
All events traceable |
24 |
Use Auth with TCP |
Authenticate TCP connection |
Auth required before data flow |
25 |
Use Auth with UDP |
Authenticate before UDP association |
Auth required before UDP relay |
26 |
Use Auth with HTTP |
Route HTTP traffic after auth |
HTTP request succeeds |
27 |
Use Auth with FTP |
Route FTP traffic after auth |
FTP session established |
28 |
Use Auth with SSH |
Route SSH session after auth |
SSH session established |
29 |
Use Auth with DNS |
Route DNS queries after auth |
DNS resolution succeeds |
30 |
Use Auth with Email |
Route SMTP/IMAP traffic after auth |
Email sent/received |
31 |
Use Auth with Web Browser |
Browse web through authenticated SOCKS proxy |
Pages load correctly |
32 |
Use Auth with CLI Tool |
Use curl/wget with SOCKS5 auth |
Tool works with credentials |
33 |
Use Auth with Mobile App |
Route mobile app traffic through SOCKS5 with auth |
App functions normally |
34 |
Use Auth with Desktop App |
Route desktop app traffic through SOCKS5 with auth |
App functions normally |
35 |
Use Auth with Proxy Auto-Config (PAC) |
Use PAC file to configure SOCKS5 with auth |
Proxy used with credentials |
36 |
Use Auth with Browser Extension |
Configure browser extension with SOCKS5 auth |
Extension connects successfully |
37 |
Use Auth with VPN Tunnel |
Route VPN traffic through authenticated SOCKS |
Tunnel established |
38 |
Use Auth with Load Balancer |
Route through load-balanced SOCKS proxies |
Auth handled per instance |
39 |
Use Auth with Failover Proxy |
Switch to backup proxy with auth |
Auth reattempted successfully |
40 |
Use Auth with Multi-User Support |
Support multiple user accounts |
Each user authenticated separately |
41 |
Use Auth with Session Timeout |
Session expires after inactivity |
Re-authentication required |
42 |
Use Auth with Credential Expiry |
Password expires after set period |
User prompted to update |
43 |
Use Auth with Password Policy |
Enforce strong password rules |
Weak passwords rejected |
44 |
Use Auth with Two-Factor Authentication |
Add 2FA to SOCKS auth (via wrapper) |
Second factor required |
45 |
Use Auth with LDAP |
Authenticate via LDAP backend |
LDAP credentials validated |
46 |
Use Auth with RADIUS |
Authenticate via RADIUS server |
RADIUS credentials validated |
47 |
Use Auth with PAM |
Authenticate via Pluggable Auth Modules |
PAM credentials validated |
48 |
Use Auth with Database Backend |
Authenticate against SQL/NoSQL database |
DB credentials validated |
49 |
Use Auth with Token-Based System |
Authenticate using token instead of password |
Token validated |
50 |
Use Auth with Anonymous Access Disabled |
Require auth for all users |
Anonymous access blocked |
IP Address Hiding - Testcases
# |
Test Case |
Description |
Expected Result |
|---|---|---|---|
1 |
Verify IP Masking on HTTP Request |
Send HTTP request through SOCKS proxy |
Server sees proxy IP, not client IP |
2 |
Verify IP Masking on HTTPS Request |
Send HTTPS request through SOCKS proxy |
Client IP hidden |
3 |
Verify IP Masking on FTP Session |
Connect to FTP server via SOCKS |
Server sees proxy IP |
4 |
Verify IP Masking on SMTP Session |
Send email via SOCKS |
Mail server sees proxy IP |
5 |
Verify IP Masking on SSH Session |
Connect to SSH server via SOCKS |
Server sees proxy IP |
6 |
Verify IP Masking on WebSocket |
Establish WebSocket connection |
Server sees proxy IP |
7 |
Verify IP Masking on DNS Query |
Send DNS query via SOCKS |
Resolver sees proxy IP |
8 |
Verify IP Masking on Streaming Service |
Access video stream via SOCKS |
Streaming server sees proxy IP |
9 |
Verify IP Masking on Game Server |
Play online game via SOCKS |
Game server sees proxy IP |
10 |
Verify IP Masking on API Request |
Call REST API via SOCKS |
API server sees proxy IP |
11 |
Verify IP Masking on Mobile App |
Route mobile app traffic through SOCKS |
App backend sees proxy IP |
12 |
Verify IP Masking on Desktop App |
Route desktop app traffic through SOCKS |
App backend sees proxy IP |
13 |
Verify IP Masking on CLI Tool |
Use curl/wget with SOCKS proxy |
Target sees proxy IP |
14 |
Verify IP Masking on Browser |
Browse web through SOCKS proxy |
Websites see proxy IP |
15 |
Verify IP Masking on Email Client |
Use IMAP/SMTP via SOCKS |
Mail server sees proxy IP |
16 |
Verify IP Masking on VPN Tunnel |
Route VPN traffic through SOCKS |
VPN server sees proxy IP |
17 |
Verify IP Masking on Cloud Storage |
Access cloud storage via SOCKS |
Storage service sees proxy IP |
18 |
Verify IP Masking on Git Repository |
Clone/push via SOCKS |
Git server sees proxy IP |
19 |
Verify IP Masking on Docker Registry |
Pull/push images via SOCKS |
Registry sees proxy IP |
20 |
Verify IP Masking on Kubernetes API |
Access K8s API via SOCKS |
API server sees proxy IP |
21 |
Verify IP Masking on CDN Access |
Load content via SOCKS |
CDN sees proxy IP |
22 |
Verify IP Masking on Payment Gateway |
Process payment via SOCKS |
Gateway sees proxy IP |
23 |
Verify IP Masking on Analytics Service |
Send analytics data via SOCKS |
Service sees proxy IP |
24 |
Verify IP Masking on Blockchain Node |
Sync node via SOCKS |
Peer sees proxy IP |
25 |
Verify IP Masking on AI Model API |
Call AI inference API via SOCKS |
Server sees proxy IP |
26 |
Detect Real IP Leak via Headers |
Inspect headers for client IP |
No real IP present |
27 |
Detect Real IP Leak via WebRTC |
Test WebRTC IP leak |
Real IP hidden |
28 |
Detect Real IP Leak via DNS |
Test DNS leak |
DNS queries routed via proxy |
29 |
Detect Real IP Leak via JavaScript |
Run JS-based IP detection |
Proxy IP shown |
30 |
Detect Real IP Leak via Flash |
Run Flash-based IP detection |
Proxy IP shown |
31 |
Detect Real IP Leak via STUN |
Use STUN server to detect IP |
Real IP hidden |
32 |
Detect Real IP Leak via ICMP |
Ping from server to client |
No response (ICMP blocked) |
33 |
Detect Real IP Leak via TCP Fingerprint |
Analyze TCP/IP fingerprint |
Proxy fingerprint shown |
34 |
Detect Real IP Leak via TLS Fingerprint |
Analyze TLS handshake |
Proxy fingerprint shown |
35 |
Use SOCKS with Tor |
Route traffic through Tor SOCKS proxy |
Onion routing hides IP |
36 |
Use SOCKS with VPN |
Combine SOCKS with VPN |
IP hidden by VPN and proxy |
37 |
Use SOCKS with Proxy Chain |
Chain multiple proxies |
Final proxy IP visible |
38 |
Use SOCKS with Geo-IP Masking |
Use proxy in different region |
Server sees regional IP |
39 |
Use SOCKS with IP Rotation |
Rotate proxy IP periodically |
Server sees different IPs |
40 |
Use SOCKS with Anonymous Proxy |
Use proxy with no logs |
IP hidden and untraceable |
41 |
Use SOCKS with Authenticated Proxy |
Use proxy requiring login |
IP hidden after auth |
42 |
Use SOCKS with Public Proxy |
Use open SOCKS proxy |
IP hidden but may be logged |
43 |
Use SOCKS with Private Proxy |
Use dedicated SOCKS proxy |
IP hidden securely |
44 |
Use SOCKS with Proxy Auto-Config |
Configure PAC file for SOCKS |
IP hidden as per config |
45 |
Use SOCKS with Browser Extension |
Use SOCKS via browser extension |
IP hidden in browser |
46 |
Use SOCKS with CLI Proxy Tool |
Use tool like proxychains |
IP hidden in CLI apps |
47 |
Use SOCKS with App-Level Proxy |
Configure app to use SOCKS |
IP hidden for app traffic |
48 |
Use SOCKS with System-Level Proxy |
Set system-wide SOCKS proxy |
All traffic routed and IP hidden |
49 |
Use SOCKS with Firewall Rules |
Block direct traffic, allow proxy |
Only proxy IP visible |
50 |
Use SOCKS with Logging Disabled |
Disable proxy logs |
IP hidden and untraceable |
firewall traversal - Testcases
# |
Test Case |
Description |
Expected Result |
|---|---|---|---|
1 |
Connect Through Basic Firewall |
Route traffic through SOCKS behind a basic firewall |
Connection succeeds |
2 |
Connect Through NAT |
Route traffic from NATed client |
Connection succeeds |
3 |
Connect Through Corporate Firewall |
Use SOCKS in enterprise network |
Traffic allowed via proxy |
4 |
Connect Through Port-Restricted NAT |
Use SOCKS behind port-restricted NAT |
Connection succeeds |
5 |
Connect Through Symmetric NAT |
Use SOCKS behind symmetric NAT |
Connection succeeds |
6 |
Connect Through Firewall with No Outbound |
Block direct outbound, allow proxy |
Only proxy traffic allowed |
7 |
Connect Through Proxy-Aware Firewall |
Use SOCKS where firewall allows proxy ports |
Connection succeeds |
8 |
Connect Through Deep Packet Inspection |
Use SOCKS to bypass DPI |
Traffic not blocked |
9 |
Connect Through Application Firewall |
Use SOCKS to tunnel non-HTTP traffic |
Traffic allowed |
10 |
Connect Through Transparent Proxy |
Use SOCKS behind transparent proxy |
SOCKS traffic routed correctly |
11 |
Connect Through HTTP-Only Firewall |
Use SOCKS to tunnel non-HTTP protocols |
Non-HTTP traffic allowed |
12 |
Connect Through DNS-Only Firewall |
Use SOCKS to bypass DNS-only restriction |
Full access restored |
13 |
Connect Through Port 80 Only Firewall |
Use SOCKS on port 80 |
Connection succeeds |
14 |
Connect Through Port 443 Only Firewall |
Use SOCKS on port 443 |
Connection succeeds |
15 |
Connect Through IP Whitelist Firewall |
Use SOCKS proxy on whitelisted IP |
Traffic allowed |
16 |
Connect Through MAC Address Filter |
Use SOCKS to bypass MAC filtering |
Connection succeeds |
17 |
Connect Through Geo-Blocked Firewall |
Use SOCKS proxy in allowed region |
Geo-block bypassed |
18 |
Connect Through Content Filter |
Use SOCKS to access blocked content |
Content accessible |
19 |
Connect Through School Network |
Use SOCKS in restricted school network |
Access granted |
20 |
Connect Through Hotel Wi-Fi |
Use SOCKS on captive portal network |
Traffic routed after login |
21 |
Connect Through ISP-Level Firewall |
Use SOCKS to bypass ISP restrictions |
Access restored |
22 |
Connect Through Mobile Carrier Firewall |
Use SOCKS on mobile data |
Traffic routed successfully |
23 |
Connect Through Airport Wi-Fi |
Use SOCKS in public Wi-Fi |
Connection succeeds |
24 |
Connect Through Government Firewall |
Use SOCKS to bypass national firewall |
Access granted |
25 |
Connect Through Cloud Firewall |
Use SOCKS in cloud-hosted VM |
Outbound traffic allowed |
26 |
Connect Through Container Firewall Rules |
Use SOCKS inside Docker container |
Traffic routed correctly |
27 |
Connect Through Kubernetes Network Policy |
Use SOCKS in K8s pod with egress rules |
Traffic allowed via proxy |
28 |
Connect Through VPN Firewall |
Use SOCKS inside VPN tunnel |
Traffic routed securely |
29 |
Connect Through IDS/IPS |
Use SOCKS to avoid intrusion detection |
Traffic not flagged |
30 |
Connect Through Zero Trust Gateway |
Use SOCKS with identity-based access |
Authenticated traffic allowed |
31 |
Connect Through Firewall with Logging |
Use SOCKS to reduce log visibility |
Client IP hidden |
32 |
Connect Through Firewall with Rate Limits |
Use SOCKS to manage traffic flow |
Rate limits respected |
33 |
Connect Through Firewall with Time Limits |
Use SOCKS outside allowed hours |
Access granted via proxy |
34 |
Connect Through Firewall with App Control |
Use SOCKS to tunnel blocked apps |
App functions normally |
35 |
Connect Through Firewall with DPI Blocking |
Use SOCKS to tunnel encrypted traffic |
DPI bypassed |
36 |
Connect Through Firewall with TLS Blocking |
Use SOCKS to tunnel TLS |
TLS handshake succeeds |
37 |
Connect Through Firewall with UDP Block |
Use SOCKS to tunnel UDP |
UDP traffic allowed |
38 |
Connect Through Firewall with TCP Block |
Use SOCKS to tunnel TCP |
TCP traffic allowed |
39 |
Connect Through Firewall with ICMP Block |
Use SOCKS to maintain connectivity |
SOCKS unaffected by ICMP block |
40 |
Connect Through Firewall with Proxy Chain |
Use SOCKS in chained proxy setup |
Traffic routed through all proxies |
41 |
Connect Through Firewall with PAC File |
Use PAC file to configure SOCKS |
Proxy used as defined |
42 |
Connect Through Firewall with DNS Leak |
Use SOCKS to route DNS |
DNS leak prevented |
43 |
Connect Through Firewall with IP Leak |
Use SOCKS to mask IP |
Real IP hidden |
44 |
Connect Through Firewall with Port Scan |
Use SOCKS to avoid detection |
Proxy port not flagged |
45 |
Connect Through Firewall with NAT Timeout |
Maintain long-lived connection |
SOCKS keeps session alive |
46 |
Connect Through Firewall with Session Expiry |
Reconnect after session timeout |
SOCKS re-establishes connection |
47 |
Connect Through Firewall with Proxy Auth |
Use SOCKS with authentication |
Authenticated and allowed |
48 |
Connect Through Firewall with IPv6 Block |
Use SOCKS over IPv4 |
IPv6 block bypassed |
49 |
Connect Through Firewall with IPv4 Block |
Use SOCKS over IPv6 |
IPv4 block bypassed |
50 |
Connect Through Firewall with No Proxy |
Attempt direct connection |
Fails without SOCKS, succeeds with SOCKS |
Domain Name Resolution - Testcases
# |
Test Case |
Description |
Expected Result |
|---|---|---|---|
1 |
Enable Remote DNS Resolution |
Configure client to let proxy resolve domain names |
DNS resolved by proxy |
2 |
Disable Remote DNS Resolution |
Configure client to resolve locally |
DNS resolved by client |
3 |
Resolve Public Domain via Proxy |
Access example.com through SOCKS5 |
Proxy resolves domain |
4 |
Resolve Blocked Domain via Proxy |
Access geo-blocked domain |
Proxy resolves and connects |
5 |
Resolve Internal Domain via Proxy |
Access internal company domain |
Proxy resolves if configured |
6 |
Resolve CDN Domain via Proxy |
Access CDN-hosted content |
Proxy resolves and fetches |
7 |
Resolve Domain with Multiple A Records |
Handle round-robin DNS |
Proxy selects one IP |
8 |
Resolve Domain with CNAME |
Resolve domain with CNAME record |
Final IP resolved |
9 |
Resolve Domain with TTL |
Respect DNS TTL |
Cache expires as expected |
10 |
Resolve Domain with DNSSEC |
Use DNSSEC-enabled domain |
Resolution succeeds if supported |
11 |
Resolve Domain with IPv6 |
Resolve AAAA record |
IPv6 address returned |
12 |
Resolve Domain with IPv4 |
Resolve A record |
IPv4 address returned |
13 |
Resolve Domain with Mixed Records |
Handle both A and AAAA |
One or both returned |
14 |
Resolve Domain with Wildcard |
Resolve subdomain using wildcard |
Correct IP returned |
15 |
Resolve Domain with SRV Record |
Use service-specific DNS |
SRV resolved if supported |
16 |
Resolve Domain with TXT Record |
Query TXT record |
TXT data returned |
17 |
Resolve Domain with MX Record |
Query mail server |
MX record resolved |
18 |
Resolve Domain with Long Name |
Resolve domain with long FQDN |
Resolution succeeds |
19 |
Resolve Domain with Unicode |
Use IDN (e.g., bcher.de) |
Correct IP returned |
20 |
Resolve Domain with Hyphen |
Use domain with hyphen |
Resolution succeeds |
21 |
Resolve Domain with Numbers |
Use domain with numeric characters |
Resolution succeeds |
22 |
Resolve Domain with Underscore |
Use domain with underscore (invalid) |
Resolution fails |
23 |
Resolve Domain with Invalid TLD |
Use non-existent TLD |
Resolution fails |
24 |
Resolve Domain with Expired DNS |
Use expired domain |
Resolution fails |
25 |
Resolve Domain with DNS Poisoning |
Test against spoofed DNS |
Proxy resolves correctly |
26 |
Resolve Domain with DNS Leak |
Ensure DNS query does not leak locally |
No local DNS traffic |
27 |
Resolve Domain with DNS Cache Poisoning |
Test proxy DNS cache integrity |
Correct IP returned |
28 |
Resolve Domain with DNS Timeout |
Simulate slow DNS response |
Timeout handled gracefully |
29 |
Resolve Domain with DNS Retry |
Retry on failed DNS attempt |
Retry succeeds |
30 |
Resolve Domain with DNS Failover |
Use secondary DNS if primary fails |
Resolution succeeds |
31 |
Resolve Domain with DNS over TCP |
Use TCP for DNS query |
Resolution succeeds |
32 |
Resolve Domain with DNS over UDP |
Use UDP for DNS query |
Resolution succeeds |
33 |
Resolve Domain with DNS over TLS |
Use DoT for secure resolution |
Resolution succeeds |
34 |
Resolve Domain with DNS over HTTPS |
Use DoH for secure resolution |
Resolution succeeds |
35 |
Resolve Domain with Proxy Rotation |
Use rotating proxies for resolution |
Different IPs used |
36 |
Resolve Domain with Proxy Authentication |
Use authenticated SOCKS proxy |
DNS resolved after auth |
37 |
Resolve Domain with Proxy Chain |
Use chained proxies |
DNS resolved by final proxy |
38 |
Resolve Domain with PAC File |
Use PAC file to route DNS via proxy |
Resolution follows PAC rules |
39 |
Resolve Domain with Browser Extension |
Use SOCKS via browser extension |
DNS resolved remotely |
40 |
Resolve Domain with CLI Tool |
Use curl/wget with SOCKS5 DNS |
Resolution succeeds |
41 |
Resolve Domain with Mobile App |
Route app DNS via SOCKS |
App connects successfully |
42 |
Resolve Domain with Desktop App |
Route desktop app DNS via SOCKS |
App connects successfully |
43 |
Resolve Domain with DNS Logging Enabled |
Log DNS queries at proxy |
Logs show correct domain |
44 |
Resolve Domain with DNS Logging Disabled |
Disable DNS logging |
No logs generated |
45 |
Resolve Domain with DNS Firewall |
Bypass DNS-based firewall |
Blocked domain accessible |
46 |
Resolve Domain with Geo-Blocked DNS |
Access region-restricted domain |
Proxy resolves successfully |
47 |
Resolve Domain with CDN Optimization |
Use proxy near CDN edge |
Faster content delivery |
48 |
Resolve Domain with DNS Load Balancing |
Handle DNS-based load balancing |
One IP selected |
49 |
Resolve Domain with DNS Failover Service |
Use failover DNS service |
Backup IP used |
50 |
Resolve Domain with DNS Proxy |
Use SOCKS proxy as DNS forwarder |
All queries routed through proxy |
No Content Inspection - Testcases
# |
Test Case |
Description |
Expected Result |
|---|---|---|---|
1 |
Transmit Encrypted Data via SOCKS |
Send TLS-encrypted data through SOCKS |
Data passes unaltered |
2 |
Transmit Plaintext Data via SOCKS |
Send unencrypted data |
Data passes unaltered |
3 |
Transmit Binary Data via SOCKS |
Send binary file |
File received intact |
4 |
Transmit JSON via SOCKS |
Send JSON payload |
JSON not parsed or modified |
5 |
Transmit XML via SOCKS |
Send XML document |
XML not parsed or modified |
6 |
Transmit HTML via SOCKS |
Send HTML content |
HTML not inspected |
7 |
Transmit Executable via SOCKS |
Send .exe file |
File delivered without inspection |
8 |
Transmit Media File via SOCKS |
Send video/audio file |
File delivered intact |
9 |
Transmit Compressed File via SOCKS |
Send .zip or .tar.gz |
Archive not unpacked or scanned |
10 |
Transmit Malware Sample via SOCKS |
Send known malware file |
Proxy does not block or scan |
11 |
Transmit Large File via SOCKS |
Send large file |
No throttling or inspection |
12 |
Transmit Chat Message via SOCKS |
Send instant message |
Message not logged or filtered |
13 |
Transmit VoIP Packet via SOCKS |
Send voice data |
Packet not decoded |
14 |
Transmit Game Packet via SOCKS |
Send game traffic |
Data not interpreted |
15 |
Transmit Email via SOCKS |
Send SMTP/IMAP traffic |
Content not scanned |
16 |
Transmit DNS Query via SOCKS |
Send DNS request |
Query not logged or filtered |
17 |
Transmit FTP Command via SOCKS |
Send FTP control message |
Command not parsed |
18 |
Transmit SSH Session via SOCKS |
Send SSH traffic |
Session not inspected |
19 |
Transmit WebSocket Frame via SOCKS |
Send WebSocket data |
Frame not decoded |
20 |
Transmit MQTT Message via SOCKS |
Send IoT message |
Message not interpreted |
21 |
Transmit gRPC Call via SOCKS |
Send Protobuf message |
Message not parsed |
22 |
Transmit SOAP Request via SOCKS |
Send SOAP XML |
Not inspected |
23 |
Transmit GraphQL Query via SOCKS |
Send GraphQL payload |
Not parsed |
24 |
Transmit SQL Query via SOCKS |
Send SQL over TCP |
Query not logged |
25 |
Transmit Authentication Token via SOCKS |
Send bearer token |
Token not intercepted |
26 |
Transmit OAuth Flow via SOCKS |
Complete OAuth2 exchange |
Tokens not inspected |
27 |
Transmit JWT via SOCKS |
Send JSON Web Token |
Token not decoded |
28 |
Transmit API Key via SOCKS |
Send API key in header |
Key not logged or filtered |
29 |
Transmit Credit Card Info via SOCKS |
Send payment data |
Data not inspected |
30 |
Transmit Personal Data via SOCKS |
Send PII (e.g., name, address) |
Data not logged |
31 |
Transmit Health Data via SOCKS |
Send HL7/FHIR data |
Data not inspected |
32 |
Transmit Blockchain Transaction via SOCKS |
Send transaction to node |
Transaction not parsed |
33 |
Transmit AI Model Input via SOCKS |
Send ML inference request |
Input not logged or analyzed |
34 |
Transmit Encrypted Email via SOCKS |
Send PGP-encrypted email |
Content not decrypted |
35 |
Transmit Encrypted Chat via SOCKS |
Send E2E encrypted message |
Message not inspected |
36 |
Transmit Encrypted File via SOCKS |
Send encrypted archive |
File not decrypted |
37 |
Transmit Encrypted Video via SOCKS |
Stream DRM-protected content |
Stream not inspected |
38 |
Transmit Encrypted Voice via SOCKS |
Send secure VoIP call |
Voice not decoded |
39 |
Transmit Encrypted DNS via SOCKS |
Use DoH or DoT |
Query not inspected |
40 |
Transmit Encrypted Tunnel via SOCKS |
Use VPN over SOCKS |
Tunnel not inspected |
41 |
Transmit Obfuscated Protocol via SOCKS |
Use protocol obfuscation |
Data not interpreted |
42 |
Transmit Unknown Protocol via SOCKS |
Use custom protocol |
Data passed transparently |
43 |
Transmit Fragmented Packet via SOCKS |
Send fragmented TCP/UDP packet |
Reassembled without inspection |
44 |
Transmit Malformed Packet via SOCKS |
Send malformed data |
Proxy does not block or analyze |
45 |
Transmit High-Frequency Data via SOCKS |
Send rapid data bursts |
No inspection or throttling |
46 |
Transmit Low-Frequency Data via SOCKS |
Send slow stream |
No timeout or inspection |
47 |
Transmit Data with Spoofed Headers |
Send fake headers |
Headers not validated |
48 |
Transmit Data with Embedded Scripts |
Send HTML/JS payload |
Scripts not filtered |
49 |
Transmit Data with Tracking Pixels |
Send tracking content |
Not blocked or modified |
50 |
Transmit Data with Ads |
Send ad content |
Ads not filtered |
IPv6 support - Testcases
# |
Test Case |
Description |
Expected Result |
|---|---|---|---|
1 |
Connect to IPv6 Website via SOCKS |
Access IPv6-only website |
Page loads successfully |
2 |
Connect to Dual-Stack Website via SOCKS |
Access site with both IPv4 and IPv6 |
IPv6 preferred if available |
3 |
Connect to IPv6 FTP Server via SOCKS |
Use IPv6 address for FTP |
FTP session established |
4 |
Connect to IPv6 Email Server via SOCKS |
Use IPv6 for SMTP/IMAP |
Email sent/received |
5 |
Connect to IPv6 SSH Server via SOCKS |
Use IPv6 for SSH |
Session established |
6 |
Connect to IPv6 DNS Server via SOCKS |
Resolve domain using IPv6 DNS |
DNS query succeeds |
7 |
Connect to IPv6 Game Server via SOCKS |
Use IPv6 for online gaming |
Game connects and plays smoothly |
8 |
Connect to IPv6 CDN via SOCKS |
Access CDN edge node via IPv6 |
Content delivered |
9 |
Connect to IPv6 API via SOCKS |
Call REST API hosted on IPv6 |
API response received |
10 |
Connect to IPv6 Cloud Service via SOCKS |
Access cloud-hosted service |
Connection succeeds |
11 |
Connect to IPv6 IoT Device via SOCKS |
Communicate with IPv6-enabled device |
Data exchanged |
12 |
Connect to IPv6 Blockchain Node via SOCKS |
Sync with IPv6 peer |
Node syncs successfully |
13 |
Connect to IPv6 VPN Server via SOCKS |
Establish VPN tunnel |
Tunnel established |
14 |
Connect to IPv6 WebSocket via SOCKS |
Use IPv6 for WebSocket |
Connection established |
15 |
Connect to IPv6 Streaming Service via SOCKS |
Stream video/audio |
Stream plays smoothly |
16 |
Connect to IPv6 IRC Server via SOCKS |
Join chat via IPv6 |
Messages exchanged |
17 |
Connect to IPv6 MQTT Broker via SOCKS |
Publish/subscribe via IPv6 |
Messages delivered |
18 |
Connect to IPv6 Kubernetes API via SOCKS |
Access K8s API server |
API calls succeed |
19 |
Connect to IPv6 Git Server via SOCKS |
Clone/push repo |
Git operations succeed |
20 |
Connect to IPv6 Docker Registry via SOCKS |
Pull/push images |
Registry access succeeds |
21 |
Use IPv6 DNS Resolution via SOCKS |
Resolve AAAA records |
IPv6 address returned |
22 |
Use IPv6 Reverse DNS via SOCKS |
Perform PTR lookup |
Hostname resolved |
23 |
Use IPv6 with PAC File |
Configure SOCKS proxy for IPv6 |
Proxy used correctly |
24 |
Use IPv6 with Browser Extension |
Route browser traffic via IPv6 SOCKS |
Pages load correctly |
25 |
Use IPv6 with CLI Tool |
Use curl/wget with IPv6 SOCKS |
Tool works correctly |
26 |
Use IPv6 with Mobile App |
Route app traffic via IPv6 SOCKS |
App functions normally |
27 |
Use IPv6 with Desktop App |
Route desktop app traffic via IPv6 SOCKS |
App functions normally |
28 |
Use IPv6 with Authenticated Proxy |
Authenticate and connect via IPv6 |
Auth succeeds |
29 |
Use IPv6 with Proxy Chain |
Chain multiple IPv6 proxies |
Traffic routed correctly |
30 |
Use IPv6 with Load Balancer |
Route through IPv6 load balancer |
Load distributed |
31 |
Use IPv6 with Failover Proxy |
Switch to backup IPv6 proxy |
Connection re-established |
32 |
Use IPv6 with DNS Leak Test |
Ensure DNS queries use IPv6 |
No IPv4 DNS leak |
33 |
Use IPv6 with IP Leak Test |
Ensure real IPv4 address is hidden |
Only IPv6 proxy IP visible |
34 |
Use IPv6 with Firewall |
Bypass IPv6 firewall restrictions |
Access granted |
35 |
Use IPv6 with NAT64 |
Connect from IPv6-only client to IPv4 server |
Translation succeeds |
36 |
Use IPv6 with Dual-Stack Client |
Prefer IPv6 when available |
IPv6 used |
37 |
Use IPv6 with Dual-Stack Server |
Prefer IPv6 when available |
IPv6 used |
38 |
Use IPv6 with IPv6-Only Client |
Connect from IPv6-only device |
Connection succeeds |
39 |
Use IPv6 with IPv6-Only Server |
Connect to IPv6-only service |
Connection succeeds |
40 |
Use IPv6 with IPv6-Only Proxy |
Use SOCKS proxy with only IPv6 address |
Traffic routed successfully |
41 |
Use IPv6 with IPv6-Only DNS |
Use DNS resolver with only IPv6 |
Resolution succeeds |
42 |
Use IPv6 with IPv6-Only Network |
Operate in IPv6-only environment |
All services reachable |
43 |
Use IPv6 with IPv6 Firewall Rules |
Allow proxy traffic through IPv6 firewall |
Traffic allowed |
44 |
Use IPv6 with IPv6 Logging |
Log IPv6 addresses in proxy logs |
Logs show IPv6 addresses |
45 |
Use IPv6 with IPv6 Monitoring |
Monitor IPv6 traffic |
IPv6 flows visible |
46 |
Use IPv6 with IPv6 Rate Limiting |
Apply rate limits to IPv6 clients |
Limits enforced |
47 |
Use IPv6 with IPv6 GeoIP |
Detect proxy location via IPv6 |
Correct region shown |
48 |
Use IPv6 with IPv6 CDN Edge |
Connect to nearest IPv6 CDN node |
Fast content delivery |
49 |
Use IPv6 with IPv6 DNSSEC |
Secure DNS resolution over IPv6 |
DNSSEC validated |
50 |
Use IPv6 with IPv6 Privacy Extensions |
Use temporary IPv6 addresses |
Real address hidden |
Flexible Application Use - Testcases
# |
Test Case |
Description |
Expected Result |
|---|---|---|---|
1 |
Use SOCKS with Web Browser |
Configure browser to use SOCKS proxy |
Web pages load via proxy |
2 |
Use SOCKS with Torrent Client |
Route torrent traffic through SOCKS |
Torrents download/upload |
3 |
Use SOCKS with SSH Client |
Connect to remote server via SOCKS |
SSH session established |
4 |
Use SOCKS with FTP Client |
Transfer files via SOCKS proxy |
FTP session succeeds |
5 |
Use SOCKS with Email Client |
Send/receive email via SOCKS |
Email operations succeed |
6 |
Use SOCKS with IRC Client |
Join IRC channels via SOCKS |
Messages exchanged |
7 |
Use SOCKS with VPN Client |
Tunnel VPN through SOCKS |
VPN connects successfully |
8 |
Use SOCKS with WebSocket App |
Establish WebSocket via SOCKS |
Connection stable |
9 |
Use SOCKS with REST API Client |
Call API endpoints via SOCKS |
API responses received |
10 |
Use SOCKS with Git Client |
Clone/push repo via SOCKS |
Git operations succeed |
11 |
Use SOCKS with Docker |
Pull/push images via SOCKS |
Registry access succeeds |
12 |
Use SOCKS with Kubernetes CLI |
Access K8s API via SOCKS |
kubectl commands succeed |
13 |
Use SOCKS with CLI Tools |
Use curl/wget with SOCKS |
Tools fetch data |
14 |
Use SOCKS with Game Client |
Connect to game server via SOCKS |
Game plays smoothly |
15 |
Use SOCKS with Streaming App |
Stream video/audio via SOCKS |
Stream plays without buffering |
16 |
Use SOCKS with Messaging App |
Send/receive messages via SOCKS |
Messages delivered |
17 |
Use SOCKS with IoT Device |
Communicate via SOCKS |
Data exchanged |
18 |
Use SOCKS with Blockchain Node |
Sync blockchain via SOCKS |
Node syncs successfully |
19 |
Use SOCKS with Remote Desktop |
Connect to RDP/VNC via SOCKS |
Session established |
20 |
Use SOCKS with Cloud Storage |
Upload/download files via SOCKS |
File transfer succeeds |
21 |
Use SOCKS with Mobile Browser |
Route mobile browser via SOCKS |
Pages load correctly |
22 |
Use SOCKS with Mobile App |
Route app traffic via SOCKS |
App functions normally |
23 |
Use SOCKS with Desktop App |
Route desktop app via SOCKS |
App functions normally |
24 |
Use SOCKS with Authenticated Proxy |
Authenticate and connect |
Auth succeeds |
25 |
Use SOCKS with Proxy Chains |
Chain multiple proxies |
Traffic routed correctly |
26 |
Use SOCKS with Load Balancer |
Route through load balancer |
Load distributed |
27 |
Use SOCKS with Failover Proxy |
Switch to backup proxy |
Connection re-established |
28 |
Use SOCKS with DNS Resolver |
Resolve domains via SOCKS |
DNS queries succeed |
29 |
Use SOCKS with DNS Leak Test |
Ensure DNS uses SOCKS |
No DNS leak |
30 |
Use SOCKS with IP Leak Test |
Hide real IP |
Only proxy IP visible |
31 |
Use SOCKS with PAC File |
Configure proxy via PAC |
Proxy used correctly |
32 |
Use SOCKS with Browser Extension |
Route via extension |
Traffic proxied |
33 |
Use SOCKS with Email over IMAP |
Access mailbox via SOCKS |
Mailbox loads |
34 |
Use SOCKS with SMTP |
Send email via SOCKS |
Email sent |
35 |
Use SOCKS with NTP |
Sync time via SOCKS |
Time syncs correctly |
36 |
Use SOCKS with SNMP |
Monitor devices via SOCKS |
Data retrieved |
37 |
Use SOCKS with MQTT |
Publish/subscribe via SOCKS |
Messages delivered |
38 |
Use SOCKS with WebDAV |
Access remote files via SOCKS |
Files accessible |
39 |
Use SOCKS with SMB |
Access shared folders via SOCKS |
Shares mounted |
40 |
Use SOCKS with RDP Gateway |
Connect via SOCKS |
Session established |
41 |
Use SOCKS with Telnet |
Connect to server via SOCKS |
Telnet session works |
42 |
Use SOCKS with SIP |
Make VoIP calls via SOCKS |
Call connects |
43 |
Use SOCKS with Video Conferencing |
Join meetings via SOCKS |
Video/audio stable |
44 |
Use SOCKS with CDN |
Access content via SOCKS |
Content delivered |
45 |
Use SOCKS with API Gateway |
Route API calls via SOCKS |
Gateway responds |
46 |
Use SOCKS with Monitoring Tools |
Monitor via SOCKS |
Metrics collected |
47 |
Use SOCKS with Logging Tools |
Log traffic via SOCKS |
Logs show proxy usage |
48 |
Use SOCKS with Rate Limiting |
Apply limits via SOCKS |
Limits enforced |
49 |
Use SOCKS with GeoIP |
Detect location via SOCKS |
Proxy location shown |
50 |
Use SOCKS with Privacy Tools |
Anonymize traffic |
Identity protected |
Lightweight and fast - Testcases
# |
Test Case |
Description |
Expected Result |
|---|---|---|---|
1 |
Measure Latency Over SOCKS |
Ping server via SOCKS |
Low latency observed |
2 |
Measure Throughput Over SOCKS |
Download large file |
High throughput maintained |
3 |
Stream 4K Video via SOCKS |
Use proxy for UHD stream |
Smooth playback |
4 |
Play Online Game via SOCKS |
Route game traffic |
No lag or jitter |
5 |
Conduct Video Call via SOCKS |
Use proxy for Zoom/Meet |
Clear audio/video |
6 |
Conduct Voice Call via SOCKS |
Use VoIP app |
No audio delay |
7 |
Use SOCKS with Real-Time Stock App |
Stream market data |
Data updates instantly |
8 |
Use SOCKS with Live Sports App |
Stream live match |
No buffering |
9 |
Use SOCKS with Live Chat |
Send/receive messages |
Instant delivery |
10 |
Use SOCKS with Real-Time Multiplayer Game |
Join match |
No lag spikes |
11 |
Use SOCKS with Real-Time Collaboration Tool |
Edit docs with others |
Changes sync instantly |
12 |
Use SOCKS with IoT Sensor Feed |
Stream sensor data |
Data updates in real-time |
13 |
Use SOCKS with Live Coding Interview |
Share code in real-time |
No delay |
14 |
Use SOCKS with Remote Desktop |
Control PC remotely |
Smooth interaction |
15 |
Use SOCKS with Live Auction App |
Place bids in real-time |
Bids register instantly |
16 |
Use SOCKS with Financial Trading App |
Execute trades |
Orders placed instantly |
17 |
Use SOCKS with Live Map App |
Track location |
Updates in real-time |
18 |
Use SOCKS with Live Weather App |
Get weather updates |
Data refreshes quickly |
19 |
Use SOCKS with Live News Feed |
Stream headlines |
News loads instantly |
20 |
Use SOCKS with CDN |
Fetch content from edge |
Fast delivery |
21 |
Use SOCKS with WebSocket |
Maintain real-time connection |
No disconnects |
22 |
Use SOCKS with MQTT Broker |
Publish/subscribe |
Messages delivered instantly |
23 |
Use SOCKS with RTMP Stream |
Broadcast live video |
Stream stable |
24 |
Use SOCKS with RTSP Stream |
View IP camera |
Video loads quickly |
25 |
Use SOCKS with Online Whiteboard |
Draw collaboratively |
No lag |
26 |
Use SOCKS with Online IDE |
Code in browser |
Fast response |
27 |
Use SOCKS with Git Push |
Push large repo |
Fast upload |
28 |
Use SOCKS with Git Clone |
Clone large repo |
Fast download |
29 |
Use SOCKS with Docker Pull |
Pull large image |
Image downloads quickly |
30 |
Use SOCKS with Cloud Sync |
Sync files to cloud |
Sync completes quickly |
31 |
Use SOCKS with Email Sync |
Sync inbox |
Emails load instantly |
32 |
Use SOCKS with DNS Resolution |
Resolve domains |
Fast response |
33 |
Use SOCKS with CDN Edge Node |
Connect to nearest node |
Low latency |
34 |
Use SOCKS with Load Balancer |
Distribute traffic |
Fast routing |
35 |
Use SOCKS with API Gateway |
Call APIs |
Fast response |
36 |
Use SOCKS with Mobile App |
Use proxy on mobile |
App remains responsive |
37 |
Use SOCKS with Desktop App |
Use proxy on desktop |
App remains responsive |
38 |
Use SOCKS with CLI Tool |
Use curl/wget |
Fast data retrieval |
39 |
Use SOCKS with Authenticated Proxy |
Authenticate quickly |
No delay |
40 |
Use SOCKS with Proxy Chain |
Chain proxies |
Minimal added latency |
41 |
Use SOCKS with Failover Proxy |
Switch proxies |
Fast recovery |
42 |
Use SOCKS with CDN Failover |
Switch CDN nodes |
No delay in content |
43 |
Use SOCKS with Rate-Limited App |
Maintain speed under limits |
No throttling |
44 |
Use SOCKS with High-Speed Network |
Test on gigabit link |
Full speed utilized |
45 |
Use SOCKS with IPv6 |
Route via IPv6 |
No performance drop |
46 |
Use SOCKS with IPv4 |
Route via IPv4 |
No performance drop |
47 |
Use SOCKS with Encrypted Traffic |
Use TLS/SSL |
No noticeable slowdown |
48 |
Use SOCKS with Compressed Traffic |
Use gzip/brotli |
Fast decompression |
49 |
Use SOCKS with CDN Prefetching |
Preload content |
Instant access |
50 |
Use SOCKS with Real-Time Monitoring |
Monitor systems |
Metrics update instantly |
Reference links