No Signup Unlimited Usage Real Data 100% Free Privacy First Fast Results Export Reports Mobile Friendly

Proxy Checker

Test up to 20 HTTP, HTTPS or SOCKS proxies at once: whether each one works, its speed, exit IP and country, anonymity level (transparent, anonymous or elite) and whether Google answers through it.

Fetching live data…

Quick answer

The Proxy Checker tests up to 20 HTTP, HTTPS, SOCKS5 or SOCKS4 proxies in one run and tells you, for each one, whether it works, how fast it answers, which IP address and country websites will see, how anonymous it is and whether Google accepts traffic from it. Paste the list in almost any format, with or without a username and password.

How it works

  1. Paste your proxies, one per line: ip:port, ip:port:user:pass, user:pass@ip:port or a URL such as socks5://user:pass@host:1080.
  2. Pick the protocol, or leave it on auto-detect: each proxy is tried over HTTP first and, if it does not answer, over SOCKS5.
  3. All proxies are tested at the same time. Each one fetches a small echo page that reports the address and headers it received, and makes one HTTPS request to Google’s generate_204 address.
  4. Exit addresses are looked up for country, city and type, and the results come back in a single table with a copyable list of the proxies that work.

What it checks

  • Status — working or dead, with the reason: timeout, refused connection, wrong password (407) or wrong protocol.
  • Speed — the full round trip through the proxy in milliseconds.
  • Exit IP and location — the address and country a website will see.
  • IP type — datacenter, residential or ISP, mobile, or a known proxy address.
  • Anonymity — elite (no trace of a proxy), anonymous (proxy headers but no real IP) or transparent (your real IP is forwarded).
  • Google access — whether Google answers normally or blocks the address.

Why it matters

A proxy that is slow, transparent or already blocked by Google will quietly spoil whatever you use it for: rank checks return CAPTCHAs, a geo-test shows the wrong country, or the proxy forwards the very address you wanted to hide. Free public lists are the worst case, as most entries die within hours and many are transparent. Paid proxies fail too, and most providers only replace or refund them within a short window after purchase, so testing on day one saves money.

How to act on the results

  • Dead with 407 — the username or password is wrong, or the provider expects your own IP to be whitelisted instead.
  • Dead with a handshake error — switch the protocol (HTTP and SOCKS5 ports are often different).
  • Transparent — do not use it for privacy or location tests; it reveals the original address.
  • Google blocked — fine for other sites, but expect CAPTCHAs on searches. For SERP checks, residential or ISP addresses usually fare better than datacenter ones.
  • Need another format — send the working list to the Proxy Format Converter to turn it into curl, Python or Playwright settings.

Frequently asked questions

Are my proxy passwords saved?

No. Credentials are used only for the requests in this test. They are not written to our logs, which record only how many lines you submitted, and the results table masks every password.

Why is a proxy slow here but fast for me?

The speed shown is measured from our server, so it includes the distance between our server and the proxy. A proxy close to you can be quicker from your machine. Compare proxies with each other in one run rather than reading the number as absolute.

Which addresses can I not test?

For safety the checker refuses private and reserved addresses, our own server, and ports used by non-proxy services such as SSH, mail or databases. It also limits each run to 20 proxies and a few runs every ten minutes. To see the address your own connection shows, use What Is My IP?.

Learn & Resources

Guides, tips and tutorials hand-picked for this tool — go from running a check to actually fixing it.