Proxy URL Parser & Builder

socks5:// resolves the target hostname locally on your machine before opening the tunnel — leaking the domain to your ISP's DNS resolver. socks5h:// (the 'h' stands for hostname) tells the client to send the raw hostname to the proxy, which resolves it on the exit side. Always prefer socks5h:// for privacy or scraping.

Percent-encode any reserved character: @ becomes %40, : becomes %3A, / becomes %2F, # becomes %23. Example: password 'p@ss:1' becomes 'p%40ss%3A1' in the URL. The builder does this automatically when you type into the password field.

Yes. IPv6 hosts must be wrapped in square brackets — socks5h://user:pass@[2001:db8::1]:1080 — otherwise the colons collide with the port separator. The parser detects and preserves the brackets, and the builder auto-brackets any IPv6 address you enter into the host field.

All three accept the same shape: scheme://username:password@host:port. cURL uses --proxy or -x, Python requests uses the proxies={'http':...,'https':...} dict, and Node uses socks-proxy-agent. Build the URL once here and paste it into each client — no per-library reformat needed.

Yes. socks5h://host:port is a valid URL. The parser will populate host and port and leave username/password empty. Never use unauthenticated public SOCKS5 endpoints for anything sensitive — they are almost always honeypots or overloaded.

Rotating providers encode session/country parameters into the username. Example: socks5h://user-country-us-session-abc123:pass@gate.provider.com:7777. The parser preserves any user string verbatim. Check your provider's docs for the exact schema (some use dashes, some use colons).

Common causes: (1) missing scheme (socks5h:// prefix), (2) unencoded special characters in the password, (3) trailing whitespace, (4) forgotten IPv6 brackets. Paste the offending URL into the parser — it highlights the exact character or field that broke validation.

The parser encodes all fields into the URL by default, including credentials. Never share the URL over public chat if it contains real credentials. For teammate onboarding, share the URL with placeholder credentials and let them substitute their own from your password manager.

You cannot — HTTP and SOCKS5 are different wire protocols on different ports. If a provider offers both, they'll expose separate credentials (often the same user/pass, different host or port). Paste each URL into the parser separately to normalize them.

There is no standard reserved port — 1080 is a common convention for open proxies. Commercial providers typically use 7777, 9000, 10000, 22225, or custom ports per plan. Always use the exact port from your provider's dashboard; guessing will produce silent connection failures.

Yes — the tool warns whenever a URL uses socks5:// (local DNS resolution) instead of socks5h:// (remote resolution). Click 'Upgrade to socks5h' to rewrite the URL and copy the safer version. Most rotating residential providers require socks5h to avoid DNS leaks that break sticky sessions.

Providers rarely allow non-ASCII in credentials, but if yours does, percent-encode the UTF-8 bytes. Example: 用户 becomes %E7%94%A8%E6%88%B7. The builder does this automatically when you paste the raw string. If your client library rejects the URL, verify it supports UTF-8 percent-encoding.

No — parsing is syntactic. It verifies the URL is well-formed and normalizes fields, but it does not open a network connection. To test reachability, feed the parsed URL into the Latency Test tool or the cURL Generator's curl output and run it locally.

Store the full socks5h:// URL as a single secret (PROXY_URL) rather than splitting host/port/user/pass into four variables. This keeps the encoding invariant and lets you rotate credentials by updating one value. Reference it as $PROXY_URL in curl, requests or Node — the parser output is the exact shape you want.