Connecting a proxy: HTTP and SOCKS5
What the four credential lines in your dashboard mean and how to plug them into a browser, an antidetect tool or your own script.
After a purchase your dashboard shows four values: host, port, login and password. That is all any proxy-aware software needs.
Two protocols on one port
The same credentials work over HTTP and over SOCKS5, only the port number differs. HTTP is simpler and browsers understand it natively, while SOCKS5 carries any TCP traffic and suits applications that go beyond the web.
The connection string
Most programs accept a proxy as a single line holding the protocol, the login, the password, the host and the port. When there is only one field, the usual order is protocol first, then login and password separated by a colon, then the address and the port.
Checking it works
- Open any IP lookup service through the proxy and compare the address and country with what the dashboard shows.
- If the connection never opens, check the protocol: some software silently expects SOCKS5 where you pointed it at the HTTP port.
- An authorisation error almost always means a stray space copied into the login or the password.
You never see the carrier credentials and they are never passed on: the connection always runs through our gateway, and you get a separate login and password of your own.