Protocols

The connection protocol (HTTP, HTTPS, or SOCKS5) can be specified in the tool or program you're using to connect with the proxies.

In the following cURL examples, the protocol is specified at the beginning of the proxy line, just replace the username and password with your proxy user credentials, and run them in your Terminal or Command Prompt.

HTTP

Here is a cURL example for the HTTP protocol:

curl -x "http://username:[email protected]:10001" "https://ip.decodo.com/json"

HTTPS

Using this protocol will encrypt your connection. Here is a cURL example for the HTTPS protocol:

curl -x "https://username:[email protected]:10001" "https://ip.decodo.com/json"

SOCKS5

Both UDP and TCP connections are supported via SOCKS5 with ISP Pay/GB proxies.

Here is a cURL example for the SOCKS5 protocol:

curl -x "socks5h:/uUsername:[email protected]:10001" "https://ip.decodo.com/json"

📘

The letter h in socks5h:// means that the hostname will be resolved on the proxy side, and not locally.

Ports

Easily understand which ports you can access when using our proxies, including details on the default accessible ports and restrictions.

Accessible Ports

With the Static Residential (ISP) proxies, only the following ports are accessible:

• 80
• 443
• 563
• 8443
• 43

Restricted Ports

Restricted ports include SMTP, IMAP, and other mailing and messaging related ports.

🚧

Please note that currently, restricted ports and any others not mentioned in the Accessible Ports list cannot be unblocked for Static Residential (ISP) proxies.