Free Proxy Tester
Test HTTP, SOCKS4 & SOCKS5 proxies in bulk. Check exit IP, latency, geolocation, ISP, and anonymity level — all server-side so your real IP stays private.
Need reliable proxies that actually pass?
196+ countries · 99.97% uptime · from $0.99/GB · residential & mobile IPs
What is a Proxy Checker?
A proxy checker (also called a proxy tester or proxy server checker) is a tool that verifies whether a proxy server is functional, measures its response speed, and reveals key details about the connection — including the exit IP address, geographic location, internet service provider (ISP), and anonymity level.
When you send traffic through a proxy, the destination website sees the proxy's IP address instead of yours. A proxy tester confirms this is actually happening and that the proxy isn't leaking your real IP address — which is what determines the anonymity level.
How to Use the Proxy Tester
Choose Single or Bulk mode
Use Single mode to test one proxy with detailed output. Use Bulk mode to paste a list and test them all simultaneously.
Enter your proxies
Supported formats: host:port, host:port:user:pass, user:pass@host:port, or prefixed with http://, socks4://, or socks5://
Configure settings
Set the number of threads (concurrent tests), timeout in seconds, and optionally a delay between tests for rotating proxy pools.
Run and filter
Click Test All and watch results populate in real time. Filter by Alive or Dead, then export working proxies as TXT or CSV.
Understanding Proxy Anonymity Levels
Elite
Also called "high anonymity" proxies. The destination server cannot tell a proxy is being used — no proxy-related headers are forwarded.
Anonymous
The server knows a proxy is in use (via headers like "Via") but your real IP address is not revealed.
Transparent
The server can see both that a proxy is in use AND your real IP via X-Forwarded-For. Provides no privacy.
Supported Proxy Formats
Why Test Proxies Server-Side?
Browser-based proxy testers have a fundamental limitation: browsers cannot route arbitrary HTTP requests through an external proxy server via JavaScript. The only way to truly test a proxy is to make the request from a server that can be configured to use that proxy.
Our tool runs all proxy tests server-side using Node.js with CONNECT tunneling (via HTTPS targets). This ensures the proxy is actually being used for the test traffic — not bypassed. Your real IP is never part of the test request.
Your Proxy Credentials Are End-to-End Encrypted
When you enter a username and password, they are encrypted in your browser before the request leaves your device — using ECDH P-256 + AES-256-GCM, the same cryptographic primitives used in TLS. The server receives only an encrypted blob; the plaintext credentials exist only in memory during the test and are never written to any log.
🔑
Encrypted before sending
Your browser generates a one-time keypair per request and encrypts credentials locally. Only the encrypted envelope travels over the network.
🚫
Invisible to Cloudflare
The Cloudflare edge layer only ever sees the encrypted blob — even if request bodies were logged, credentials would be unreadable.
🧹
Never stored or logged
The backend decrypts credentials in memory, runs the proxy test, then discards them. No database writes, no log entries, no traces.
Tips for Accurate Results
- ›Use HTTPS targets (which we do by default) to force CONNECT tunneling — HTTP requests can bypass the proxy agent in some configurations.
- ›For rotating proxy pools, add a delay of 1–2 seconds between tests to allow the pool to assign different exit nodes.
- ›If proxies time out, try increasing the timeout. Residential and mobile proxies often have higher latency than datacenter proxies.
- ›Set threads to 1 when testing rotating proxies if you want to guarantee sequential rotation.
- ›Export alive proxies as TXT to get a clean list ready to use in your tools or bots.