Scraped from 25+ sources, checked every 30 minutes with 100 concurrent workers. Every proxy is scored 0–100 based on latency, throughput, reliability and anonymity.
| Host : Port | Protocol | Country | Anonymity | Latency | ↓ Down | ↑ Up | Score | Status |
|---|---|---|---|---|---|---|---|---|
| Loading proxies… | ||||||||
Every proxy receives a score from 0–100 based on five weighted factors, checked live every 15 minutes.
The destination server sees the proxy's IP as the client. No X-Forwarded-For, no Via, no Proxy-* headers. The server cannot tell a proxy is in use.
Your real IP is hidden, but the server can see proxy-related headers like Via or Proxy-Connection. The server knows you're behind a proxy, but not who you are.
The proxy passes your real IP in the X-Forwarded-For header. The destination sees both the proxy IP and your real IP. Provides no privacy protection.
Every proxy is verified using 100 simultaneous worker threads. We test liveness, measure latency, and detect anonymity level — all in parallel.
We scrape GitHub raw lists, JSON APIs (GeoNode, ProxyScrape), and HTML pages (free-proxy-list.net, socks-proxy.net) every 6 hours.
Every proxy gets a 0–100 score weighted by latency (30%), throughput (25%), reliability (30%), freshness (10%), and anonymity (5%).
We classify each proxy as Elite (hides your IP, no proxy headers), Anonymous (hides your IP), or Transparent (reveals your IP).
Working proxies are speed-tested by downloading through them via Cloudflare's speed endpoints. Real MB/s measurements, not estimates.
Full REST API with API key auth, per-key rate limiting, rich filters (protocol, country, anonymity, score, latency), and bulk download.
Scraping runs every 6 hours. Checking runs every 30 minutes. Dead proxies are tracked and re-verified, not deleted — so score history is preserved.
Built on Node.js 22.5+ with the built-in node:sqlite module. No external database server required. Runs anywhere Node runs.
The gold standard for proxying. SOCKS5 works at the transport layer — it tunnels any TCP/UDP traffic, not just HTTP. Supports authentication and handles DNS resolution at the proxy server (no DNS leaks).
An older version of SOCKS that only supports TCP. Faster to negotiate than SOCKS5 but lacks UDP, authentication, and IPv6 support. Still widely supported.
HTTP proxies intercept HTTP traffic using the CONNECT method. Simple to configure, widely supported by browsers and HTTP clients. Only proxies HTTP/HTTPS traffic.
Anonymity levels describe how much the proxy reveals about you to the destination server.
The full API is available at /api/* and requires an X-API-Key header.
The public endpoints below (/public/*) are key-free for use in scripts.
curl "http://localhost:3000/public/proxies?protocol=socks5&min_score=60&limit=50"
curl "http://localhost:3000/public/proxies/download?protocol=socks5" -o socks5.txt
curl -H "X-API-Key: px_..." \
"http://localhost:3000/api/proxies/random?protocol=socks5&anonymity=elite"
curl -H "X-API-Key: px_..." \
"http://localhost:3000/api/proxies/best?protocol=socks5&limit=10"
curl -X POST -H "X-API-Key: px_admin..." \
http://localhost:3000/api/admin/scrape
curl -X POST -H "X-API-Key: px_admin..." \
-d '{"status_filter":"untested"}' \
http://localhost:3000/api/admin/check
| Parameter | Values | Description |
|---|---|---|
| protocol | socks5, socks4, http, https | Filter by proxy protocol |
| anonymity | elite, anonymous, transparent | Minimum anonymity level |
| min_score | 0–100 | Minimum proxy score |
| max_latency_ms | integer (ms) | Maximum response latency |
| country | ISO 2-letter (US, DE, etc.) | Filter by proxy country |
| limit / offset | max 300 (public), 500 (API) | Pagination |