​
Why Use SOCKS5 Proxies?

SOCKS5 proxies offer greater flexibility and efficiency for web scraping, data collection, and network security. Unlike HTTP and HTTPS proxies, which are limited to web traffic, SOCKS5 supports multiple protocols and unrestricted port usage.

Key advantages of SOCKS5 proxies:

  • Works with various types of network traffic, not just HTTP(S).

  • Enables remote DNS resolution for enhanced privacy.

  • Bypasses firewalls and restrictions with minimal latency.

  • Supports authentication for secure access.

For general web scraping, Toolip’s HTTP and HTTPS proxies may be a more cost-effective choice. However, if your project requires advanced compatibility, SOCKS5 is the ideal solution.

​
How to Set Up Toolip SOCKS5 Proxies

1

Configure SOCKS5 Port

Toolip uses port 31115 for SOCKS5 connections.

Ensure your application or service is set to connect via:

proxy.toolip.io:31115

The standard Toolip ports (31111-31114) used for HTTP and HTTPS are not compatible with SOCKS5.

2

Use Domain Names for Targeting

Toolip SOCKS5 proxies support only domain names (hostnames), not direct IP addresses.

To avoid connection issues, follow these guidelines:

  1. Use domain names (e.g., example.com) instead of numeric IP addresses.

  2. Ensure your application is set to resolve DNS remotely through the proxy.

If these rules are not followed, requests will be blocked.

3

Make Requests With `curl` Using SOCKS5

Always use socks5h://proxy.toolip.io:31115 to ensure remote DNS resolution.

When making requests with curl, use the -x flag to specify the SOCKS5 proxy and ensure remote DNS resolution with socks5h://.

Example command:

curl -i -x socks5h://proxy.toolip.io:31115 --proxy-user [USERNAME]:[PASSWORD] "https://toolip.io/welcome.txt"

  • The -x flag specifies the proxy.

  • The socks5h:// prefix forces remote DNS resolution.

  • Replace [USERNAME], [PASSWORD] with your Toolip credentials.

4

Troubleshooting `curl` Requests

If you encounter issues, use the -i or -v flag in curl for detailed debugging output:

curl -v -x socks5h://proxy.toolip.io:31115 --proxy-user [USERNAME]:[PASSWORD] "https://toolip.io/welcome.txt"

Look for headers like:

  • x-brd-error

  • x-brd-err-code

  • x-brd-err-msg

Use the error details in these headers to help diagnose the issue, and refer to our troubleshooting page for solutions.

5

SOCKS5 authentication

Toolip requires authentication for SOCKS5 proxy access.

You can authenticate in two ways:

  1. Enter your username and password in your application’s proxy settings.

  2. Use a single-line authentication format:

username:password@proxy.toolip.io:31115
6

Understand the Difference Between SOCKS5 and SOCKS5h

  • SOCKS5: The client resolves DNS locally before sending requests through the proxy.

  • SOCKS5h: DNS is resolved remotely by the proxy, ensuring greater privacy and preventing DNS leaks.

Choose the method that best aligns with your requirements for enhanced flexibility and security.

​
Summary - HTTP/HTTPS vs SOCKS5

FeatureHTTP/HTTPSSOCKS5
Protocol SupportOnly HTTP and HTTPSSupports all protocols (HTTP, FTP, SMTP, etc.)
Traffic TypeWeb traffic onlyAny type of network traffic
DNS ResolutionLocal (by client)Remote (with SOCKS5h)
Authentication SupportYesYes
SpeedGenerally faster for web browsingSlightly slower due to flexibility
Firewall BypassLimitedBetter at bypassing firewalls and restrictions
Use CaseWeb scraping, browsingAdvanced scraping, P2P, gaming, privacy tools
  • Use HTTP/HTTPS for general and standard web scraping and browsing.
  • Use SOCKS5 when you need protocol flexibility, remote DNS resolution, bypass network restrictions or you just feel that HTTP/HTTPS don’t do the job.
Toolip proxies do not support UDP protocol, our services are based on TCP only.