Connection string converter

Paste the line your dashboard gives you. The converter splits it into host, port and credentials, then prints working snippets for the tools people actually use. Everything runs in your browser and nothing is sent anywhere.

The two ways access is granted

A line with a login carries its own credentials, so it works from any machine. A line without one relies on the address bound in your dashboard: the service recognises where the connection comes from and lets it through. A package includes two bound addresses and they can be changed at any time, which covers a laptop and a server at once. The difference matters most in containers, where the outbound address is often not the one you expect.

socks5 against socks5h

One letter decides who resolves domain names. Under socks5 the client resolves the name locally and only then opens the tunnel, so a request to your DNS server leaves the machine directly. Under socks5h the name travels inside the tunnel and the proxy resolves it. For collection work the second form is usually what you want, and it is available on every package that includes access over the SOCKS5 protocol.

Checking the line before it reaches your code

Copy the curl snippet and run it once. A status code and a timing figure appear in a second, and both tell you more than any settings screen. If the code is 407 the credentials or the binding are wrong; if the request hangs, the port is closed on the way out. Only after that does it make sense to wire the line into a scraper or a browser profile.

Formats the converter understands

Dashboards disagree about format, so the parser takes the four common shapes: host:port, host:port:login:password, a full URL with a scheme, and the variant where credentials trail the host after an at sign. Lists are usually delivered as a file or a link and can be pulled straight into a scraper. Addresses themselves come from a private pool reserved for customers of the service.