Recognize your proxy format
These are placeholders, not working credentials. Copy the actual endpoint and protocol-specific port from your provider or dashboard.
HTTP proxy URL
http://USERNAME:PASSWORD@HOST:PORTSOCKS5 proxy URL
socks5://USERNAME:PASSWORD@HOST:PORTSeparate credential fields
HOST:PORT:USERNAME:PASSWORDFor HTTPS destinations, the dashboard’s HTTP proxy can establish a tunnel using an http:// proxy URL. Do not change it to https:// unless your provider supports TLS to the proxy itself. Colon-separated credentials also need a protocol selected in the client.
Test one connection first
- Configure your client with the correct endpoint, port and authentication fields.
- Start with Any country and Random rotation if using PhantomProxies.
- Make a single request to an IP-information endpoint using a short timeout.
- Compare the observed exit IP with your direct connection, then add country or sticky-session settings as needed.
Follow the proxy testing guide for examples and interpreting failures, or open the integration documentation.
Interpret results carefully
A successful IP check confirms that request worked. Geography is approximate, latency varies with the route and destination, and a residential device can disconnect during a sticky session. A working proxy does not guarantee access to every website.
Keep complete proxy URLs out of shared logs, screenshots and browser address bars because they contain your password. Use the dashboard to rotate exposed credentials.
