Proxy Checker

Check proxies for scraping — status, speed, anonymity, geo, usage type and a real anti-bot test

Paste a proxy list and check each one in the browser: alive or dead, latency, anonymity and IP leaks, exit IP, geo/ASN and usage type. For a single proxy it also runs a real anti-bot test against Google, Cloudflare or your own target. Tells you whether to scrape with a proxy or drop it.

Proxies

How to use

  1. 1Paste your proxiesOne per line — `host port`, `host:port user pass`, or `socks5://user:pass@host:port`. You can also tick saved proxies from Request Tester.
  2. 2Run the checkOne proxy → deep check (geo, ASN, usage type, anti-bot). Several → fast basic check (status, speed, anonymity).
  3. 3Read the verdictGOOD — scrape with it; RISKY — works but likely to get blocked (try residential); REPLACE — dead or leaks your IP. Expand a row or run a deep check on it.

Examples

Bulk-test 10 fresh proxies
10 lines → basic check
Paste the list you just bought and see which are alive, fast and anonymous.
Deep-check one proxy
1 line → geo + anti-bot
A single proxy gets country, ISP, ASN, usage type and a live test against Google and Cloudflare.
Test against your real target
Target URL = your site
Enter the site you want to scrape — see whether the proxy clears its anti-bot or gets challenged.
Spot a transparent proxy
anonymity = transparent
A proxy that leaks your real IP is marked REPLACE — useless for scraping however fast it is.
Datacenter or residential
usage type = datacenter
ASN and usage type show what the target sees: a datacenter IP (blocked easily) or a residential one.

When to use for web scraping

Check proxies right after buying them, before they go into a scraper. One that pings can still be useless — transparent (leaks your real IP), a flagged datacenter IP that anti-bots block, or already dead. Catching that first saves you from debugging the scraper for the proxy's faults. The call is binary: keep or replace. Basic mode culls the obvious duds (dead, slow, transparent) across the list; deep mode tells you whether a specific proxy actually clears Cloudflare/Google or your target. Everything runs server-side, and the geo lookups go out through our proxies — your real IP isn't exposed.

FAQ

What does the GOOD / RISKY / REPLACE verdict mean?
GOOD — alive, anonymous and clean, safe to scrape with. RISKY — works but is a datacenter/flagged IP or got challenged by an anti-bot, so it may get blocked (try residential). REPLACE — dead, fails auth, or leaks your real IP.
Why is a single proxy checked more deeply than a list?
A single proxy also gets geo/ASN and a live anti-bot test (Google, Cloudflare, your target). For a list we run only the fast basics — for speed and rate limits — and you can deep-check any row afterwards.
What is an anonymity level?
Transparent leaks your real IP via headers (useless for scraping). Anonymous hides the IP but reveals a proxy is in use. Elite looks like a normal client — what you want.
Does checking expose my real IP?
No. The test runs from our servers through the proxy, and the geo lookups go out through our own proxies with failover, so your IP is never sent to third parties.
Which proxy formats are supported?
`host port`, `host:port`, optional `user pass`, and the URL form `http(s)://user:pass@host:port` / `socks4|socks5://…`. One proxy per line.

Related tools