After configuring a proxy, verify it works before running production jobs. Two common checks: browser and cURL.
Method 1: Browser
- In the browser or a proxy extension, enter MaskProxy host, port, username, and password.
- Save, then open an IP lookup page and check egress IP and region.
- If the IP changed, browser traffic is going through the proxy.
If a username/password prompt appears, the server is reachable but auth was not saved correctly — recheck username, password, and proxy type.
Method 2: cURL
cURL is better for technical debugging because connection errors are explicit. HTTP example:
curl -x http://username:password@host:port https://api.ipify.org
For SOCKS5 (if your curl build supports it):
curl -x socks5h://username:password@host:port https://api.ipify.org
Sample host/port: gw.maskproxy.io / 1288 (follow My Proxy).
How to read results
- Returns an IP: proxy is up — next check region.
- Timeout: check local network, firewall, port, protocol, and target reachability.
- Region mismatch: cross-check multiple lookup sources; databases can lag.
Re-test lightly after every parameter change to catch mistakes before production traffic.