Learn how to use SOCKS and SOCKS5 protocol with Bright Data proxy networks
SOCKS5
.
HTTP
and HTTPS
, some of the tools or utilities require SOCKS5
for their operations.
In Bright Data, we do not distinguish between HTTP
, HTTPS
and SOCKS5 proxies
: all our proxies support all three protocols. You can switch between protocols while using the same proxy.
HTTP
and HTTPS
proxy solutions are usually the best fit for scraping websites, offering lowest cost and highest performance. However, if the the task still requires SOCKS5
Bright Data can provide quality proxies around the globe.
SOCKS5
proxy connections are supported on all Bright Data proxy networks: Datacenter, ISP, Residential and Mobile.
Bright data support HTTP/S version 2.0 only via SOCKS.
We do not support tunneling HTTP/2 versiob 3.0 via SOCKS.
SOCKS5
over Bright Data Residential proxy is supported only towards HTTPS
targets, HTTP
targets will be supported soon.Bright Data uses port 22228 for SOCKS5
SOCKS5
make sure to use brd.superproxy.io:22228
and not the standard port<Tooltip tip="Port 33335 replacing port 22225 deprecated on Sep 2026, click to read more">33335 </Tooltip>
for HTTP
and HTTPS
protocols.
SOCKS5
requests only with hostnames/domain names relayed as target. Requests sent with explicit IPs or local IP resolution, are blocked.
Hence, configure your code, client or calling application to:
1024
for datacenter and ISP proxies.
8080
, 8443
, 5678
, 1962
, 2000
, 4443
, 4433
, 4430
, 4444
and 1969
for Residential & Mobile proxies.
curl
, Javascript
& Python
Use socks5h://brd.superproxy.io:22228 when issuing curl requests
curl
with Bright Data SOCKS5 proxies, you have to explicitly:-x
to your command line parametersbrd.superproxy.io:22228
-k
option to ignore SSL errors proxies or Setup SSL Certificatecurl
command:curl
curl
to troubleshoot your SOCKS5
requests, and adding curl
options -i
or -v
for printing header fields. Look for x-brd-error
, x-brd-err-code
and x-brd-err-msg
for elaborated error messages sent by Bright Data proxy networks.
To see our full error catalog (for HTTP
and HTTPS
as well) visit this page: Proxy errors troubleshooting
HTTP
and HTTPS
by relaying the user and password for the proxy access.
Some tools or utilities will give you place to input the credentials and port separately as parameters, as seen in the control panel, and some will require you to provide a url with the credentials delimited single parameter: userName:password@brd.superproxy.io:22228
.
-country-[country code]
to your SOCKS5 username.
Example for curl
command to get a SOCKS5 proxy in Italy (country code: it
):
example.com
) is resolved into an IP address
before
it is passed through the proxy. The proxy then routes traffic to the resolved IP address.