Privacy & VPN

Free Proxy Servers: What They Can See, the Risks, and How to Test One

How a free proxy server works, what its operator can read or change in your traffic, what two large studies found, and a five-step way to test any free proxy.

In this guide

A free proxy is a server someone else runs that forwards your web requests, so websites see its address instead of yours. The operator can read any unencrypted traffic, change pages, and log every site you visit. Public lists are mostly dead or short-lived servers, and large tests found a measurable share injecting ads or tracking code.

That is the whole risk in three sentences. The rest of this guide explains why it is true, what the published measurements say, which parts of your traffic a proxy can and cannot read, and how to test a specific proxy before you send anything through it. For the basics of what a proxy is and how it differs from a VPN, see what is a proxy server; this post picks up from there.

Test it now

Cloudflare edge
IP websites see216.73.216.115
LocationColumbus, United States
Internet providerAnthropic, PBC

Read at the Cloudflare edge from this request. The homepage adds your provider, network type and the VPN, DNS and WebRTC checks.

Show details

What a free proxy actually is

Public proxy lists collect servers that answer proxy requests from anyone on the internet. Some are deliberately open: a volunteer, a researcher, or a company giving away a limited tier. Many are not. An "open proxy" is often a misconfigured web server, a router with a forgotten management port, or a compromised machine that a criminal uses for a few days and then loses. The list site scans address ranges, records which hosts respond, and publishes the result with a country flag and an uptime percentage.

The consequence is that a free proxy has no accountable operator. You do not know who runs it, where its logs go, or why it exists. In the largest criminal case of this kind, the US Department of Justice said in May 2024 that the 911 S5 service had turned more than 19 million residential computers into proxy exits by bundling malware with VPN programs; the people whose computers relayed the traffic never agreed to it. A public list cannot tell you whether the address you picked is one of those.

What the measurements found

Two studies have tested free proxies at scale rather than arguing about them.

The larger one was presented at the NDSS Symposium in 2018. Researchers from FORTH, the University of Cyprus and Stony Brook collected 65,871 unique proxies from 15 public list sites over about two months and fetched pages they controlled through each one. Of the 19,473 proxies that worked, 7,441 (38.21 percent) modified the content and 1,004 (5.15 percent) were classified as malicious. The malicious behavior included injecting ads (472 proxies), collecting user information (392), tracking mouse and keyboard input (157), tracking with cookies (152) and requesting unsafe sites (118). Some proxies behaved honestly on most pages and injected code only on specific sites or only occasionally, which is why a single test can miss them.

The smaller one is a 2015 test by Christian Haschek, who checked 443 proxies from public lists. Only 199 were online. Of those, 157 (79 percent) refused HTTPS connections, 33 (16.6 percent) rewrote static HTML pages to insert ads, and 17 (8.5 percent) modified JavaScript. His conclusion was that a proxy that blocks HTTPS most likely wants to see the plain-text version of your traffic.

The two studies use different methods and different years, and neither measured today's lists. What they agree on is the shape of the problem: most free proxies are offline, a large minority of the working ones alter what you receive, and a small, persistent share are actively hostile.

What a proxy can see, and what HTTPS hides

Everything you send through a proxy passes through its memory, so the question is what is readable there.

On a plain HTTP page, the proxy sees the full URL, every header, every cookie, the page content, and anything you type into a form. It can also change all of it before it reaches you. This is the case the studies above measured.

On an HTTPS page, the browser sets up an encrypted tunnel through the proxy to the destination. The proxy sees the hostname you connect to (it has to, to forward the connection) and the size and timing of the traffic. It does not see the path, the content or your form fields, unless one of two things happens: the proxy presents its own certificate and your browser accepts it, or the proxy refuses HTTPS and you fall back to HTTP. A certificate warning while using a proxy is the proxy trying to read your traffic. Do not click through it.

Outside the browser, the proxy sees nothing. A browser proxy setting covers browser traffic; other apps and system updates keep using your real connection. That is also why a proxy is not a VPN: there is no system-wide tunnel and no encryption of your traffic between you and the proxy unless the proxy itself is reached over TLS, which most free ones are not.

The headers that give you away

Many proxies announce themselves. A forwarding proxy that follows the standards adds a header to each request. RFC 7239 defines the Forwarded header, whose "for" parameter carries the originating client address; the older X-Forwarded-For header does the same job informally, and the Via header names the proxy software and version. Proxy lists call servers that send these "transparent", servers that send Via but hide your address "anonymous", and servers that send neither "elite". The names are a convention of the lists, not a standard, and the only way to know what a given proxy sends is to look.

The what websites see page prints the request headers your browser delivers after they have passed through whatever is in the path. If a Forwarded, X-Forwarded-For or Via header appears there with your real address in it, the proxy is not hiding you from anyone who reads headers, and that includes most fraud and bot-detection systems.

Even an "elite" proxy is usually known. Detection databases maintain lists of public proxy addresses; MaxMind's Anonymous IP database, for example, has an "is_public_proxy" field that is set for addresses that belong to a public proxy. Any address that has sat on a public list for a week is in feeds like that one, so sites that use them treat you as a proxy user regardless of headers.

How to test a free proxy in five steps

Do this before you send anything through a proxy, and do it from a browser profile with no logged-in accounts. The steps were checked on current desktop versions of Chrome and Firefox; the proxy setting lives under the operating system's network settings in Chrome and under Settings, Network Settings in Firefox.

  1. Confirm the exit address. With the proxy configured, open the IP lookup. The address, ISP and country shown should belong to the proxy. If you still see your own ISP, the proxy is not being used at all, which is common with dead list entries.
  2. Check what the address is known as. Open the proxy check. It reports whether the address appears on published proxy, VPN, Tor or relay lists and whether the network is a hosting provider or a consumer ISP. A free proxy that is already listed will be blocked or challenged by many sites; a residential address on a free list is a warning sign in itself, because it is likely a compromised device.
  3. Look at your headers. Open the what websites see page and read the request headers. Any Forwarded, X-Forwarded-For or Via line means the proxy is disclosing the path.
  4. Test HTTPS. Load an HTTPS site you know well. A certificate warning, a downgrade to HTTP, or a connection error means the proxy either cannot or will not pass encrypted traffic. Stop there.
  5. Check DNS. Run the DNS leak test. Browser proxy settings often forward only the web request while name lookups still go from your machine to your ISP's resolver. If the resolver shown belongs to your ISP, every domain you visit is still visible on your own connection.

If a proxy passes all five, you know it forwards traffic, hides your address from header readers and does not break encryption. You still do not know who runs it or what it logs, and no test can tell you that.

Free proxy vs paid proxy vs VPN: what the money buys

A paid proxy or VPN does not buy you trustworthiness. It buys you an operator you can name, a policy you can read, and addresses that are not shared with everyone who found the same list. Whether that operator deserves trust is a separate question, and the published measurements above are about free lists, not about paid services.

The practical rule is to match the tool to the stakes. For reading a geo-restricted news page, a tested free proxy on an HTTPS site is a tolerable risk. For anything with a login, a payment, or your real identity, it is not, because the proxy can see the hostname of every service you touch and can interfere with any connection it chooses. For hiding your own address from websites in general, a VPN or Tor covers the whole device; the hide your IP address guide compares those options.

Sources

Questions

Are free proxies safe?

Not by default. The operator sits between you and every site you visit, can read unencrypted traffic and can rewrite pages. A 2018 NDSS study of 19,473 working open proxies found 38.21 percent modified content and 5.15 percent were malicious. Use one only for non-sensitive browsing on HTTPS sites, and test it first.

What is the difference between a free proxy and a paid proxy?

A paid proxy comes with an operator you can identify, terms that say what is logged, and addresses that are not shared with thousands of strangers. A free proxy from a public list has none of that, so its address is often already on blocklists and its operator is unknown.

Can a free proxy see my passwords?

Only if the site sends them unencrypted. On an HTTPS page the proxy sees the domain you connected to but not the page content or form fields. If a proxy refuses HTTPS connections, or presents its own certificate, assume it wants to read the traffic.

How do I check whether a proxy is working?

Configure the browser to use it, open a site that reports your address, and confirm the address and location belong to the proxy rather than to your ISP. Then run a DNS leak test; many proxy setups still send DNS queries from your own connection.