Appearance
What is a proxy server, and how is it different from a VPN?
A proxy forwards one application's traffic so the destination sees the proxy's address instead of yours — and that sentence contains both differences from a VPN: one application's, and no mention of encryption. Proxies are older, lighter, and more surgical than VPNs, genuinely useful for per-app routing — and routinely oversold as privacy tools, a job where their gaps do the talking. Here's the honest shape of the thing.
Maintained by the ipconfig.io team · Reviewed 1 July 2026
What it does, mechanically
You configure an app — usually a browser — to send requests to the proxy, which relays them onward. The destination logs the proxy's IP; check from a proxied browser and ipconfig.io shows the proxy's address, while a terminal curl ipconfig.io on the same machine still shows your real one. That split-screen is the lesson: the proxy covered the browser, and nothing else.
The common types, quickly: HTTP(S) proxies understand web traffic (the HTTPS variant relays encrypted tunnels without reading them); SOCKS5 relays any TCP stream, protocol-blind (ssh -D gives you one for free); transparent proxies intercept without being configured — corporate networks and some ISPs; reverse proxies are the same idea pointed the other way, shielding servers rather than clients (that's Cloudflare in front of a website — including this one).
Proxy vs VPN, honestly
| Proxy | VPN | |
|---|---|---|
| Coverage | The app configured to use it | Every process on the device |
| Encryption added | Generally none | The whole tunnel |
| DNS lookups | Often bypass it (leak) | Inside the tunnel — if configured right |
| WebRTC | Usually bypasses it — your real IP leaks | Covered by full-device tunnels |
| Your ISP sees | Your destinations (plain HTTP: content too) | One encrypted stream |
| Typical use | Scraping, testing, per-app routing, filtering | Whole-device privacy |
The leak rows are the punchline: browser-proxy setups are precisely the configuration where UDP-based side channels (STUN/WebRTC) and system DNS walk around the proxy, exposing the address you were hiding. If the goal is privacy, the tool shaped like the goal is a full-device VPN or Tor — not because proxies are bad, but because coverage-by-default is the property privacy needs.
The free-proxy warning
A proxy occupies a privileged position: it sees every request sent through it, and for unencrypted traffic it can read and rewrite the content. Public lists of free proxies are, structurally, lists of strangers volunteering for that position. Some are honest, some are harvesting, and you can't tell which from the outside — treat "free proxy" the way you'd treat "free USB stick in the parking lot." Accountable operators (paid services, your own ssh -D, your employer's infrastructure) are the credible versions.
Frequently asked questions
What is a proxy? A relay that forwards an app's traffic so destinations see its IP instead of yours — per-app, usually unencrypted.
Proxy vs VPN? Proxy: one app, no added encryption, DNS/WebRTC often leak. VPN: whole device, encrypted, leak-resistant by default.
Are free proxies safe? Generally no — the operator sees (and on HTTP can modify) your traffic, with zero accountability.
What are they good for? Per-app jobs: scraping, geo-testing, filtering, routing one tool without touching the system.
Next steps
- How to hide your IP — all the methods side by side, including where proxies fit.
- What is a WebRTC leak? — the classic proxy-bypass channel.
- Does a VPN hide everything? — the whole-device alternative, honestly bounded.