HTTP proxy tester
Prepare HTTP and HTTPS proxy endpoints for your browser, scraper or API client. Check your list's format and learn what each connection result means.
- Up to 100 proxies/batch
- HTTP/S & SOCKS5
- Format checks run in your browser
host:port or host:port:username:password
http://username:password@host:port
Also supports https://, socks5:// and bracketed IPv6 addresses. URL schemes override your selected protocol. Percent-encode special characters in URL credentials.
Results
Results stream in here
Each proxy shows its status, exit IP, location and response time, and lands on the radar by speed. Paste a list and run a test, or preview an example report.
What a check tells you
Connection status
Distinguish a successful connection from a timeout or authentication error. Format validation alone cannot confirm connectivity.
Response time
Compare request latency in milliseconds. Distance, destination and network load all affect results.
Exit IP & location
See the IP exposed to the test destination. Geolocation is approximate and can differ between databases.
Testing HTTP and HTTPS proxies
Choose the proxy transport
Use HTTP for an unencrypted connection to the proxy or HTTPS when the proxy itself accepts TLS. An HTTP proxy may still support HTTPS websites through a CONNECT tunnel.
Check your authentication
HTTP proxies often use a username and password or an IP allowlist. A 407 response indicates that proxy authentication is required or was rejected. Check credentials and provider settings.
Compare response times fairly
Use the same destination and timeout when comparing endpoints. Response time depends on the proxy location, the destination and current network conditions; it is not a bandwidth measurement.
Validate your list locally, then select Test proxies when the page shows Live testing online. A separate worker checks connectivity, response time and exit IP. If the service is offline, you can still validate formats and view clearly labelled example results.
Use one proxy per line: host:port, host:port:username:password, or protocol://username:password@host:port. Explicit HTTP, HTTPS and SOCKS5 URL schemes take precedence over the selected protocol. Put IPv6 addresses in square brackets and percent-encode special characters in URL credentials.
Each batch accepts up to 100 entries and 32 KB. Duplicate entries are removed. Live tests allow up to 5 batches per minute, 20 per 10 minutes and 2,000 proxy checks per hour per public IP, with one active batch at a time. Shared connections share these limits.
Format validation runs locally without uploading your list. Starting a live test sends your endpoints and credentials to the testing service. Queue payloads are encrypted, expire after 15 minutes and are removed after processing. Credentials are never included in results or CSV exports, and the list is not saved in browser storage.
Yes, if it supports the CONNECT method. The client creates a tunnel through the HTTP proxy and negotiates TLS with the destination website. This differs from an HTTPS proxy, where the client-to-proxy connection itself uses TLS.
407 Proxy Authentication Required means the proxy needs authentication or did not accept the supplied credentials. Confirm the username, password and any IP allowlist configured by your provider.
Ready for your next proxy?
Residential, ISP and mobile proxies, or help configuring the endpoints you already have.