Free proxy list: examples and risks for business teams
The table below holds illustrative example rows for 18+ countries, generated for this page and regenerated every day. They are not live, working proxies, so do not try to connect through them. They show what a public list looks like, and the rest of the page explains why business teams should not depend on one.
| IP | Port | Type | Anonymity | Country | Uptime | Latency | Last check |
|---|---|---|---|---|---|---|---|
| 138.205.102.115 | 20049 | SOCKS4 | Anonymous | 🇨🇦 Canada | 75% | 797ms | 237m ago |
| 45.132.70.183 | 48222 | SOCKS4 | Transparent | 🇳🇱 Netherlands | 63% | 369ms | 96m ago |
| 181.13.194.31 | 42464 | HTTP | Anonymous | 🇺🇸 United States | 70% | 362ms | 8m ago |
| 125.105.13.43 | 31884 | HTTPS | Anonymous | 🇬🇧 United Kingdom | 50% | 491ms | 53m ago |
| 73.186.104.12 | 16674 | HTTP | Elite | 🇮🇳 India | 89% | 835ms | 105m ago |
| 49.200.174.119 | 11217 | SOCKS5 | Elite | 🇦🇺 Australia | 91% | 1060ms | 1m ago |
| 183.146.135.183 | 45807 | SOCKS5 | Elite | 🇷🇺 Russia | 54% | 283ms | 137m ago |
| 130.42.171.219 | 58194 | HTTPS | Anonymous | 🇯🇵 Japan | 92% | 1103ms | 47m ago |
| 136.36.129.142 | 15796 | HTTP | Transparent | 🇬🇧 United Kingdom | 74% | 805ms | 123m ago |
| 153.236.20.6 | 42615 | SOCKS4 | Transparent | 🇧🇷 Brazil | 75% | 1112ms | 147m ago |
| 18.96.19.127 | 4375 | HTTP | Anonymous | 🇯🇵 Japan | 83% | 1160ms | 159m ago |
| 217.219.96.242 | 29199 | HTTPS | Elite | 🇷🇺 Russia | 67% | 268ms | 9m ago |
| 82.180.117.186 | 7634 | HTTP | Elite | 🇮🇩 Indonesia | 51% | 370ms | 140m ago |
| 94.74.87.58 | 32632 | HTTP | Anonymous | 🇬🇧 United Kingdom | 61% | 713ms | 87m ago |
| 83.14.137.28 | 20741 | SOCKS5 | Anonymous | 🇩🇪 Germany | 54% | 1488ms | 171m ago |
| 73.7.6.55 | 17266 | HTTP | Transparent | 🇮🇩 Indonesia | 46% | 969ms | 139m ago |
| 218.10.85.53 | 23361 | HTTP | Transparent | 🇩🇪 Germany | 74% | 1074ms | 101m ago |
| 49.65.252.245 | 30852 | SOCKS5 | Anonymous | 🇺🇸 United States | 93% | 753ms | 3m ago |
| 9.35.3.231 | 44913 | HTTPS | Anonymous | 🇫🇷 France | 51% | 753ms | 191m ago |
| 46.94.14.97 | 21776 | SOCKS5 | Elite | 🇬🇧 United Kingdom | 82% | 728ms | 132m ago |
| 113.18.55.166 | 49316 | SOCKS5 | Transparent | 🇨🇦 Canada | 48% | 465ms | 118m ago |
| 139.122.161.98 | 64042 | HTTPS | Elite | 🇳🇱 Netherlands | 46% | 739ms | 119m ago |
| 76.168.71.40 | 10997 | SOCKS4 | Anonymous | 🇸🇬 Singapore | 48% | 849ms | 138m ago |
| 127.45.30.188 | 8157 | HTTPS | Anonymous | 🇵🇱 Poland | 93% | 363ms | 211m ago |
| 120.98.249.36 | 10361 | HTTPS | Transparent | 🇮🇹 Italy | 45% | 262ms | 192m ago |
| 10.208.196.96 | 45696 | HTTPS | Transparent | 🇲🇽 Mexico | 88% | 819ms | 111m ago |
| 139.178.175.140 | 63779 | HTTP | Transparent | 🇮🇳 India | 74% | 1139ms | 175m ago |
| 146.154.22.27 | 27111 | SOCKS5 | Anonymous | 🇮🇹 Italy | 60% | 1067ms | 91m ago |
| 4.3.175.191 | 33283 | SOCKS5 | Elite | 🇺🇸 United States | 60% | 819ms | 156m ago |
| 200.174.236.245 | 59944 | SOCKS4 | Anonymous | 🇨🇦 Canada | 72% | 1026ms | 81m ago |
| 88.123.253.152 | 55563 | HTTP | Elite | 🇦🇺 Australia | 83% | 210ms | 156m ago |
| 136.72.138.197 | 61353 | SOCKS5 | Anonymous | 🇩🇪 Germany | 95% | 509ms | 87m ago |
| 64.176.11.167 | 18971 | HTTP | Elite | 🇬🇧 United Kingdom | 52% | 865ms | 183m ago |
| 25.117.252.171 | 46970 | SOCKS5 | Anonymous | 🇬🇧 United Kingdom | 50% | 1117ms | 134m ago |
| 36.44.41.221 | 46948 | HTTPS | Elite | 🇩🇪 Germany | 54% | 585ms | 16m ago |
| 166.44.252.160 | 2686 | HTTP | Anonymous | 🇸🇬 Singapore | 71% | 1304ms | 240m ago |
| 93.170.236.13 | 59946 | HTTPS | Elite | 🇸🇬 Singapore | 53% | 651ms | 238m ago |
| 214.115.184.42 | 59348 | HTTP | Transparent | 🇲🇽 Mexico | 73% | 841ms | 4m ago |
| 128.7.127.132 | 21930 | SOCKS4 | Transparent | 🇹🇷 Turkey | 49% | 1082ms | 110m ago |
| 55.209.71.51 | 57162 | SOCKS4 | Anonymous | 🇸🇬 Singapore | 55% | 682ms | 185m ago |
| 77.41.253.53 | 7480 | SOCKS5 | Transparent | 🇬🇧 United Kingdom | 73% | 998ms | 227m ago |
| 36.161.178.94 | 56637 | HTTP | Transparent | 🇦🇺 Australia | 71% | 724ms | 81m ago |
| 76.193.233.254 | 56684 | SOCKS5 | Elite | 🇮🇹 Italy | 63% | 263ms | 132m ago |
| 130.44.31.138 | 36075 | HTTPS | Transparent | 🇧🇷 Brazil | 50% | 1045ms | 150m ago |
| 169.50.128.88 | 5217 | HTTPS | Elite | 🇦🇺 Australia | 77% | 137ms | 182m ago |
| 221.39.33.81 | 19842 | SOCKS4 | Anonymous | 🇸🇬 Singapore | 65% | 854ms | 119m ago |
| 16.172.18.9 | 59724 | SOCKS4 | Elite | 🇮🇹 Italy | 75% | 92ms | 205m ago |
| 114.82.4.189 | 57803 | SOCKS5 | Anonymous | 🇺🇸 United States | 78% | 270ms | 187m ago |
| 47.53.72.82 | 25590 | SOCKS4 | Elite | 🇮🇳 India | 59% | 1303ms | 109m ago |
| 15.3.136.209 | 44835 | HTTP | Elite | 🇵🇱 Poland | 67% | 620ms | 89m ago |
| 21.154.82.193 | 55699 | SOCKS4 | Transparent | 🇯🇵 Japan | 82% | 1141ms | 178m ago |
| 165.69.111.239 | 29497 | HTTP | Anonymous | 🇬🇧 United Kingdom | 48% | 1430ms | 222m ago |
| 158.99.117.134 | 9151 | SOCKS4 | Elite | 🇮🇩 Indonesia | 95% | 1181ms | 215m ago |
| 107.222.68.223 | 64468 | SOCKS4 | Elite | 🇮🇹 Italy | 48% | 916ms | 29m ago |
| 157.61.54.147 | 43295 | HTTP | Transparent | 🇦🇺 Australia | 47% | 203ms | 66m ago |
| 135.232.198.222 | 39512 | HTTP | Elite | 🇯🇵 Japan | 78% | 222ms | 55m ago |
| 139.144.27.177 | 53127 | HTTPS | Transparent | 🇵🇱 Poland | 52% | 559ms | 55m ago |
| 102.26.63.254 | 11727 | SOCKS4 | Elite | 🇵🇱 Poland | 47% | 1500ms | 31m ago |
| 55.208.51.254 | 34958 | SOCKS5 | Elite | 🇦🇺 Australia | 77% | 538ms | 210m ago |
| 57.121.98.61 | 62984 | SOCKS5 | Anonymous | 🇲🇽 Mexico | 95% | 599ms | 234m ago |
Every value in this table, including the IPs, ports, uptime, latency and check times, is an illustrative example, not a live proxy. Real public entries tend to vanish within hours anyway. For client or production work, use our paid proxies (99.9% uptime target; datacenter pools reach most targets in under 50ms).
⚠️ What a free proxy means for a business
- Nobody you can identify runs a public proxy. The operator can record your traffic, alter pages as they load, insert ads or capture logins, and many do.
- Typical uptime is 30-60%. Entries go offline quickly, and the same IPs turn up on list after list.
- Most addresses have already been abused, so large sites recognise and refuse them, usually within seconds on any protected site.
- Response times swing between 80ms and 5,000ms, with no service level of any kind.
- Throughput often tops out around 100KB/s, which rules out large data jobs and anything time-sensitive.
Where they can help: learning how proxies work, disposable tests, and a quick look at how a harmless public page appears from another country.
Where they do not belong: anything involving a login, client or company accounts, payments, customer data, or collection work that your reports depend on.
Where the entries on public lists come from
Most public lists are assembled from three kinds of source:
- Misconfigured servers - an HTTP proxy left open on a port by mistake, which scanners find and publish.
- Honeypots - proxies made public on purpose, by researchers or by attackers, in order to record what passes through them.
- Recycled free trials - addresses from paid services' trial accounts, collected and posted again.
Not one of these sources is stable or safe. Most entries survive for hours or days, and a meaningful share are run with bad intent.
If someone on your team tests a public proxy anyway
The rows on this page are examples, not working proxies. If a colleague wants to try a real public entry found elsewhere, these steps limit the damage:
- Take the entry from the public list being tested and enter it in your tool as
IP:PORT. - Run it through our proxy checker first, because many public entries are already offline.
- For HTTP or HTTPS entries, curl only needs its
--proxyflag. - For SOCKS entries, use a client that supports SOCKS and the
socks5://URL scheme. - Confirm with our My IP tool that the visible IP has really changed.
- Keep away from logins, passwords, client dashboards and company email for the whole test.
Signs the work has outgrown free lists
As soon as any of these is true:
- Someone needs to sign in to a business or client account.
- The data feeds a report, a pricing decision or a client deliverable (and is collected within each site's terms).
- A failed run would cost the business money or a deadline.
- Results have to come from the same, accurate location every time.
- The job goes beyond about 100 requests.
Our paid proxies start at $3.50 per GB, billed as you go, and cut the time staff spend chasing dead or blocked entries. Whatever your team runs, it must respect each target site's terms of service and the law that applies.
What a free proxy list actually is
A free proxy list is a published set of proxy servers that anyone can reach, normally laid out as IP:PORT pairs with columns for protocol, country, anonymity level and when each entry was last checked. Point a browser or tool at one of those entries and your traffic passes through that machine instead of going direct. The table at the top of this page copies that format with example rows we generate each day; none of them is a working proxy.
The attraction is clear: no cost, and a different IP within minutes. The trade-off is that nobody is accountable for uptime, speed, security or how long an entry lasts. For a business, a free list is a way to understand how proxies work, not a supplier. Work that has to run again next week belongs on a managed pool, with someone answerable for it.
Where proxy settings go in common tools
Setup is the same for free and paid proxies: the tool needs an address, a port and, for a paid pool, login details. These are the three places a team usually enters them.
Browsers
Find the network or proxy settings, switch to manual setup and enter the IP and port. Most browsers take an HTTP/HTTPS proxy and a SOCKS host as separate fields. Save, reload a page, then confirm the new IP with the tools further down.
Command-line tools
cURL takes --proxy http://IP:PORT for an HTTP/HTTPS proxy and --proxy socks5://IP:PORT for SOCKS5. Many other command-line tools read the http_proxy / https_proxy environment variables instead.
Scripts and monitoring tools
Python requests, Scrapy, Puppeteer and Playwright all accept a proxy URL written as scheme://IP:PORT. With free entries, build in retries and timeouts, because failures are constant; a paid pool simply adds a username and password to the same URL.
Our guide on how to use a proxy covers each tool step by step. Whatever the setup, check that the IP really changed before relying on the result.
What the protocol and anonymity columns mean
Public lists mix several kinds of proxy, and the example table above uses the same labels. Entries differ in the protocol they use and in how much they reveal about the person behind them, which is what the two groups below explain.
The protocol column
Made for ordinary web traffic and simple API calls. Easy to set up, but the connection to the proxy is unencrypted, so a hostile operator can read all of it.
Carries encrypted connections through a tunnel, so the proxy passes TLS traffic along without seeing its content. Our HTTPS proxies are the managed equivalent.
Work at a lower level and carry any TCP traffic (plus UDP with SOCKS5), not only web pages, which suits tools other than browsers. See SOCKS5 proxies for details.
The anonymity column
Hides your real IP and does not announce that a proxy is in use. On paper it reveals the least, but on a free list nobody can confirm the label, which is the core problem.
Hides your real IP but adds headers showing that a proxy is involved. Acceptable for a casual look at a page, though the destination can see a proxy is in use.
Passes your real IP on in the request headers and offers almost no privacy. Fit only for caching or basic connectivity tests, never for sensitive work.
How each protocol behaves in detail is covered in proxy protocols explained.
What free proxies put at risk
For a business the risk goes beyond a slow connection: client data, account access and the accuracy of your reports are all exposed. This is what is at stake before anything important goes through a free entry.
Data and credentials
Every request passes through a machine you know nothing about. Its operator can record traffic, insert ads or malware into pages and collect whatever staff type, and some lists exist as honeypots for that very purpose.
Reliability
Public entries usually manage 30–60% uptime and disappear within hours, with no service level, replacement or notice. A list that worked at the start of the day may be mostly offline by midday.
Speed
Throughput often stops at around 100 KB/s and latency ranges from 80 ms to several seconds, so large transfers and volume work are impractical.
Blocked, overused IPs
The same addresses are used by very large numbers of people, many of them spammers. Sites have flagged them widely, so requests fail often and staff spend more time on errors than on results.
Nobody to call
When an entry fails there is no dashboard, ticket queue or documentation, only a dead IP and a list that may never be updated.
Unreliable location
Country labels on free entries are often wrong or change without warning, so rank checks, ad reviews and price research that depend on location cannot rely on them.
Ground rules if a free proxy is used at all
If a team member still wants to experiment with a public entry, these rules stop a learning exercise from becoming a security incident:
- ✓No logins, passwords or payment details through a free proxy, at any point.
- ✓Stick to HTTPS sites, so the content stays encrypted end to end even if the proxy is hostile.
- ✓Choose entries labelled elite or anonymous rather than transparent, then check the label with the anonymity tools below.
- ✓Work in a separate browser profile or container, away from the cookies and sessions of real work accounts.
- ✓Treat everything sent as recorded, and send nothing you would not be willing to publish.
- ✓Once a task matters to the business, move it to a managed pool.
Free lists and paid pools side by side
They answer different needs. A free list suits learning and throwaway tests; a paid pool suits work the business depends on.
| Factor | Free public proxies | Our paid proxies |
|---|---|---|
| Uptime | 30–60%, and nobody answers for it | 99.9% uptime target |
| Speed | Often throttled and unpredictable | Managed pools on dedicated bandwidth |
| Security | Unknown operators who may log traffic | No traffic logs; HTTPS and SOCKS5 access |
| IP reputation | Shared by many users, widely blocked | Consent-based, ethically sourced pools |
| Support | Nobody to contact | Staffed support, 24/7 |
| Cost | Nothing to pay, but staff time lost | Per GB from $3.50, pay as you go |
The longer comparison is in our guide to free vs paid proxies.
Checking whether an entry works and what it reveals
A large share of any public list is offline or leaks the user’s IP, so test before use. These free tools show within seconds whether an entry responds and what it exposes.
Proxy checker
Shows whether an IP:PORT responds, which protocol it uses and roughly how quickly it answers.
Anonymity check
Reveals whether a proxy passes on your real IP or announces itself, separating a true elite entry from a transparent one.
My IP
Displays the IP and location websites see, so you can compare before and after switching a proxy on.
More free diagnostics are listed on the proxy tools page.
Where a free proxy is acceptable
There is a narrow place for them, provided the stakes are low and use stays within each site's terms of service and the law:
- ✓Training — showing a new team member how a proxy changes the visible IP.
- ✓Connectivity checks — seeing whether a page loads from another network or region.
- ✓Simple location previews — a quick look at how a public page appears in another country.
- ✓Tool set-up trials — finding where proxy settings go in a tool before buying data.
Market research, ad verification, SEO reporting and price monitoring need a consistency that free entries cannot offer, so that work belongs on a managed pool. In every case, collect only publicly available data and respect the terms of each site you connect to.
Making the case for a paid pool
For most teams the decision comes down to whether the result matters. Move to paid proxies when you:
- →Rely on the output, and a failed run would cost time, money or a client deadline.
- →Need the same accurate location on every check for testing or verification.
- →Work at volume, beyond a handful of requests.
- →Need a provider that keeps no traffic logs, for your own and your clients’ security.
- →Want a person to contact when something needs fixing.
Pay-as-you-go pricing keeps the move low-risk: estimate the spend in the proxy calculator and buy only the data a project needs.
What a paid pool from us includes
Four proxy types, each with one published per-GB rate. Every order supports HTTP, HTTPS and SOCKS5, signs in by username/password or IP whitelist, is delivered as soon as payment clears and stays valid for a fixed 30 days.
Datacenter
from $3.50/GB
Economical IPs for high-volume work on open sites: catalogue and stock checks, uptime monitoring and bulk tasks.
Datacenter proxies →Residential
from $3.99/GB
Home-broadband IPs with country and city targeting, used for ad verification, SEO reporting and market research.
Residential proxies →Mobile (4G/5G)
from $4.50/GB
4G/5G carrier IPs for social media management, mobile ad reviews and app testing, within each platform’s rules.
Mobile proxies →Residential Premium
from $6.50/GB
A selected residential tier for difficult sites, when fewer retries are worth a higher rate.
Premium proxies →Where our IPs come from, and what we do not log
Provenance is a key difference between a paid network and a free list. Our residential and mobile IPs come from real home connections and carrier devices supplied under legitimate, consent-based agreements, not from hidden or unclear sources. For a business that matters: a client or compliance reviewer can be told where the IPs originate, which no anonymous free proxy can offer.
We also keep no traffic logs, so the sites your team visits and the data it moves are not recorded or resold. Add HTTPS and SOCKS5 support and IP-whitelist controls, and that is a level of privacy no stranger’s free proxy provides. As a new service we do not claim certifications we do not hold; what we commit to is ethical, consent-based sourcing and clear terms.
Questions teams ask about free proxy lists
No. Every row in the table is an illustrative example that we generate for this page, and the rows are regenerated each day. They are not live, working proxies, and the uptime, latency and check-time values are examples too. To judge a real public entry found elsewhere, test it with our proxy checker first.
Only for low-stakes, disposable tasks. Each free proxy is run by an unknown operator who can log or alter traffic, so staff should never sign in, enter passwords or send payment or client details through one. Sensitive work needs a managed pool that keeps no traffic logs.
Free IPs are shared heavily, abused often and rarely maintained, so sites flag them and many are offline at any moment. A large share of any public list is dead at a given time, which is why testing comes first.
A transparent proxy passes on your real IP, an anonymous proxy hides it but signals that a proxy is in use, and an elite proxy hides both. Free lists cannot back these labels up, so check an entry with our anonymity tool before believing them.
Using a proxy is legal in most places, but the activity carried out through it must still comply with the law and with each site's terms of service. Collect only publicly available data and stay within the rules that apply to your business.
Once the result matters: dependable uptime, a consistent location, real speed, volume, security or support. Our paid proxies start at $3.50/GB, billed as you go, and access is issued as soon as payment clears.
Billing, setup and support questions are answered in the main FAQ.
Ready to move client work off free lists?
Our managed pools start at $3.50/GB, with a 99.9% uptime target, consent-based sourcing, no traffic logs and staffed support around the clock. Access is issued as soon as payment clears, and you pay only for the gigabytes your team uses.
