Auto-refreshed hourly · HTTP · HTTPS · SOCKS4 · SOCKS5
Free proxy list
A live, automatically harvested public proxy list. Filter by protocol, country, anonymity and latency, then copy or export the exact subset you need as CSV, TXT or JSON. Free proxies are unreliable by nature — use them for testing, not production.
0
Proxies listed
0
Seen this cycle
0
Countries
—
Last refresh
| IP:Port | Protocol | Country | Anonymity | Latency | Uptime | HTTPS | Status | Last seen |
|---|---|---|---|---|---|---|---|---|
| Loading the latest harvest… | ||||||||
How this free proxy list is built
Every hour an automated job queries each configured public source — plain-text lists, CSV feeds and JSON APIs (with or without an API key) — normalises the results into a single schema, and upserts them keyed on IP, port and protocol. Entries that stop appearing are flagged offline after the retention window and purged a week later, so the table reflects what was actually reachable in the most recent harvest rather than a stale archive.
Fields are only populated when the upstream source provides them. Latency and uptime come from the source's own probes, anonymity levels are reported as published (transparent, anonymous, elite), and the HTTPS column marks endpoints that accept CONNECT tunnels. Treat all of it as indicative: public proxies change behaviour minute to minute.
Free vs paid — what actually changes
A free proxy is a shared, unaccountable hop. Expect single-digit to 30% success rates on protected targets, no session control, no geo precision beyond country, and no support when it breaks. That is workable for a quick geo check or a classroom demo. It is not workable for scraping, ad verification, sneaker or multi-account work, where a burned IP costs more than a month of bandwidth.
When reliability starts to matter, move to a benchmarked network: rotating residential proxies for consumer sites, ISP proxies for long-lived logins, mobile proxies for app-only endpoints, or datacenter proxies for tolerant bulk crawling. Compare them side by side on the comparison hub or grab a discounted trial from the deals page.
Safety rules for public proxies
- Never authenticate, pay or submit personal data through a free proxy.
- Prefer HTTPS targets so the operator cannot read or modify the payload.
- Rotate aggressively — assume any single IP dies within hours.
- Respect target robots.txt and rate limits; see our compliance guide.
Free proxy FAQ
How often is this free proxy list updated?+
Every hour. An automated job re-scrapes each configured source, upserts the results, marks IPs that stopped appearing as offline and deletes entries that have been gone for a week. The timestamp above the table shows the last successful refresh.
Are free proxies safe to use?+
Treat every free proxy as untrusted infrastructure. The operator can log traffic, inject content into plain HTTP responses and rate-limit you at will. Never send logins, payment data or anything sensitive through a free proxy — use them for throwaway checks, geo spot-testing and learning only.
What is the difference between HTTP, HTTPS, SOCKS4 and SOCKS5 here?+
HTTP proxies forward web requests and rewrite headers. HTTPS entries accept CONNECT tunnels, so TLS passes through unread. SOCKS4 carries arbitrary TCP without authentication support; SOCKS5 adds UDP, IPv6 and authentication, and does not touch your headers — which is why it fingerprints better.
Why do free proxies keep dying?+
Most are misconfigured servers or short-lived boxes. Uptime of a few hours is normal, success rates below 30% on protected targets are typical, and the same IPs are already burned on major sites because thousands of people use them simultaneously.
Can I export the list?+
Yes. Use the export buttons to download the current filtered view as CSV, plain text (ip:port per line) or JSON. The export respects every active filter, so you can grab, for example, only elite SOCKS5 IPs in Germany.
When should I pay for proxies instead?+
As soon as reliability matters. Any production scraping, ad verification, multi-account or e-commerce workload needs consistent success rates and support — that means residential, ISP or mobile proxies from a benchmarked provider rather than a public list.