Proxy String Formats

Most tools need the same four values from Thunderproxy: gateway host, port, username, and password. The only difference is how the tool expects those values to be ordered.

Quick answer: use http://username:password@host:port when your app accepts a proxy URL. Use host:port:username:password or username:password@host:port only when the app specifically asks for that format.

Available formats

Thunderproxy shows common formats in Quick Access for rotating products and row/export actions for Static ISP.

Format	Example	Best for
URI	http://username:password@host:port	Apps that accept one proxy URL.
User/pass first	username:password@host:port	Tools that split credentials from protocol separately.
Host first	host:port:username:password	Browser profile tools, proxy managers, and legacy importers.

If a tool asks for separate fields, use the same values without punctuation:

Tool field	Thunderproxy value
Host, server, or proxy host	Gateway host
Port	Gateway port for the selected protocol
Username	Generated username or Static ISP row username
Password	Proxy password

URI format

Use URI format when a tool has a single proxy URL field.

http://username:password@host:port
Copy code

The http:// prefix describes how the client connects to the Thunderproxy gateway. It does not mean the target website must be HTTP. If the tool has a separate protocol selector, choose the same protocol and port shown in the dashboard.

Username format matters

For Rotating Residential and Rotating Datacenter, the username can include routing settings:

base-res-US_CALIFORNIA_LOSANGELES-sid-12345678
base-dc-DE-sid-12345678
Copy code

Copy the username after choosing location and rotating or sticky mode. If you change settings later, copy the updated username or export a new list.

For Static ISP, each proxy row has a fixed-format username:

base-stc-isp-sid-0
Copy code

Do not add rotating product suffixes to Static ISP usernames.

When to use each format

Use the dashboard's full proxy URI for quick tests, command-line tools, and SDKs that accept a proxy URL.

Use host-first format when importing many proxies into an app that expects one proxy per line.

Use separate host, port, username, and password fields when the app provides dedicated inputs. This is usually less error-prone than pasting one combined line into the wrong field.

Common mistakes

• Pasting host:port:username:password into a field that expects http://username:password@host:port.
• Keeping an old rotating username after changing country, state, city, protocol, or sticky session settings.
• Treating the gateway host as the exit IP. The gateway is the connection endpoint; the exit IP is what the target website sees after routing.
• Adding routing suffixes to Static ISP usernames.
• Using an HTTP port while the app is set to SOCKS5, or the reverse.

Next steps

• Test a proxy with cURL before adding it to production jobs.
• Choose HTTP or SOCKS5 when the app supports both.
• Troubleshoot authentication failures if a copied line returns a 407 error.