Proxy Format Guide: IP:Port:User:Pass & Proxy URLs

Proxy URL Builder
Build a URL from separate connection fields. The starting values are fictional examples. Choose a protocol your endpoint and client support.
Formatting runs in this browser, without connection tests or server submissions from this tool. Inputs stay in this page’s memory. Generated URLs include credentials; copying puts the URL on your clipboard. Clearing fields does not clear your clipboard.Compare live proxy packagesA proxy line contains connection details, but its order and separators depend on the importing tool. ip:port:user:pass is a list format. http://user:pass@host:port is a proxy URL. They can describe the same endpoint, but they are not interchangeable in every input field.
Check your software's import instructions before converting a list. An import failure, an authentication failure, and a target-site refusal need different fixes.
Use the Proxy URL Builder on this page when your client accepts a URL. Enter the host, port and original, unencoded credentials separately. The builder brackets IPv6 addresses and percent-encodes credential components; it does not test the endpoint, change the proxy protocol, or upload your inputs. Leave both credential fields blank if your setup does not use username/password authentication.
Common proxy formats at a glance
| Format | Example with fictional credentials | Check before importing |
|---|---|---|
| Host and port | 192.0.2.10:8000 | Does the tool use separate credential fields or IP authentication? |
| Colon-separated list | 192.0.2.10:8000:exampleuser:examplepass | Does the importer expect exactly this field order? |
| URL-style address | exampleuser:examplepass@192.0.2.10:8000 | Does the input accept URL user information without a scheme? |
| Proxy URL | http://exampleuser:examplepass@192.0.2.10:8000 | Is the proxy protocol HTTP, HTTPS, or SOCKS5? |
The address 192.0.2.10 is reserved for documentation. These examples are not working proxies. Use the actual endpoint and credentials from your product controls.
Convert a simple proxy line
For a tool that explicitly expects host:port:username:password, this fictional entry:
192.0.2.10:8000:exampleuser:examplepass
has the host 192.0.2.10, port 8000, username exampleuser, and password examplepass. If another tool requires an HTTP proxy URL, the same simple example becomes:
http://exampleuser:examplepass@192.0.2.10:8000
Keep the actual endpoint and credential values intact. A proxy may use a hostname instead of a numeric IP. Converting the presentation does not add protocol support or change the product's authentication method.
Special characters and IPv6 need extra care
A naive split on every colon can break credentials or IPv6 addresses. The example above assumes a simple host and credentials that contain no delimiter characters.
In a URL, characters that would act as delimiters may need percent-encoding within the relevant credential component. For example, a literal @ in a password is represented as %40 in a URL user-information field. Encode components using your client's documented method; do not encode an entire URL or assume a list importer will decode percent escapes.
Encoding fixes URL syntax, not every authentication restriction. HTTP Basic authentication cannot represent a colon in the username, even if that colon is percent-encoded in the URL. Check the authentication method and use the credentials your product supplies.
An IPv6 address contains colons. URL syntax uses brackets around an IPv6 host, but list importers can require another representation. Use the endpoint format documented by the provider and importing software. If separate host, port, username, and password fields are available, use them to avoid ambiguous parsing.
Match the protocol to the proxy
The scheme in a proxy URL describes the client-to-proxy connection:
http://selects an HTTP proxy.https://selects a TLS connection to an HTTPS proxy when the client supports it.socks5://selects SOCKS5, with DNS behavior depending on the client and options.- In curl,
socks5h://asks the proxy to resolve the destination hostname, whilesocks5://resolves it on the client. Other applications may use a separate DNS setting or may not accept that URL scheme.
An HTTPS destination does not automatically require an https:// proxy URL. An HTTP proxy can carry an HTTPS request through a CONNECT tunnel when supported. Changing a working HTTP endpoint's scheme to HTTPS or SOCKS5 does not make the proxy support that protocol.
Some applications have a separate protocol selector. Follow that application's instructions instead of adding a second protocol prefix to a field that expects only a host or list line.
Preserve generated session parameters
Residential product controls may generate usernames containing session or region settings. Copy the full value exactly. Deleting part of it can change routing or prevent authentication.
This fictional line still has one username field:
192.0.2.10:8000:exampleuser-session-demo-country-us:examplepass
The words in that example do not define Zenu's parameter syntax. Adjust session settings through the controls and instructions for your actual product. Read getting started with Zenu Proxies for help finding your order and available controls.
Diagnose the failure before changing the list
| Symptom | What it can indicate | First check |
|---|---|---|
| Import rejected | Unsupported layout, delimiter, or protocol | Compare one line with the tool's documented example |
| HTTP 407 | Missing or rejected proxy authentication | Verify credential fields, auth method, and package status |
| Connection timeout | Endpoint, port, local network, route, or service issue | Confirm the endpoint and test from the intended machine |
| HTTP 403 from the destination | The destination denied access | Stop and review the response and access rules |
| HTTP 429 from the destination | The destination rate-limited the request | Stop requests and respect retry guidance |
| Tester works, application fails | Different parser, protocol, machine, or request | Compare those settings before blaming the IP |
Check whether the proxy or destination generated the response. Do not repeatedly retry an access denial or rotate through addresses to defeat a restriction.
For IP-authenticated products, verify the allowed source IP using supported product controls. For username/password products, check capitalization, spaces, and the complete generated username. Do not weaken a password to make a faulty parser accept it; use the client's supported credential fields or encoding method.
Keep credentials private while testing
Full proxy URLs can expose usernames and passwords in screenshots, logs, shell history, and pasted commands. Use protected credential entry when available and mask secrets before sharing diagnostics. Public online checkers receive whatever proxy details you submit to them.
Zenu Proxy Tester runs checks locally. Start with import validation and a small connectivity check from the machine that will use the list. Results from your laptop may differ from another network or server.
Only make target-site requests you are permitted to send. A successful connection is an observation about that request, not a guarantee of future access or checkout success. See the pre-drop testing guide for a fuller checklist.
Choose your next step
- Plan your IP count or residential GB allowance, then compare current packages and billing units.
- Find your order and available dashboard controls.
- Compare local testing with online proxy checkers.
- Compare residential, ISP, and datacenter proxies.
Frequently asked questions
What is the difference between ip:port:user:pass and user:pass@ip:port?
They arrange the same connection details differently. The first is a proxy-list convention; the second is URL-style user information followed by the host and port. Use the exact format your software documents.
Does an HTTPS website require an https:// proxy URL?
No. An HTTP proxy can tunnel an HTTPS request using CONNECT if the proxy and client support it. The proxy URL scheme describes the connection to the proxy.
What does HTTP 407 mean?
HTTP 407 means proxy authentication is required or was not accepted. Check the credential fields, authentication method, and package status before treating it as a destination-site block.


