What Is a Proxy Server? A Plain-Language Guide

A proxy is an intermediary between you and a website. Here is how it works, the main types, and what a proxy can and cannot do for you.

12 min read

A proxy server is a computer that sits between your device and the internet. Instead of connecting to a website directly, you send your request to the proxy, which makes the request on your behalf and passes the answer back. The website sees the proxy’s IP address, not yours.

How a proxy request works

  1. Your application is configured with the proxy’s address, port and, usually, a username and password.
  2. It connects to the proxy and asks it to reach a destination, either with an HTTP request or a CONNECT/SOCKS command.
  3. The proxy opens its own connection to the destination from its own IP address.
  4. Data flows back through the proxy to you.

The main kinds of proxy

  • HTTP/HTTPS proxies understand web requests and tunnel HTTPS using the CONNECT method.
  • SOCKS5 proxies relay raw TCP (and optionally UDP) traffic for any application.
  • Datacenter, ISP, residential and mobile proxies differ in where the exit IP comes from, which affects speed, cost and how websites treat it.
  • Static proxies keep one IP; rotating proxies change it for you.

What proxies are good for

Common uses are viewing a site as a visitor from another country, spreading automated requests over many addresses, keeping separate network identities for separate accounts, testing geo-targeted content and running tools that must appear to come from a specific location.

What a proxy does not do

Unlike a VPN, which usually tunnels all traffic from a device, a proxy works per application or per request. That is a strength when you need different identities side by side and a weakness if you expect device-wide protection.

Choosing one

Start from the job: which sites, which countries, how many requests, and whether you need a stable or changing address. Then pick the IP type and protocol that match. Our guide on choosing a proxy provider covers what to verify before paying.

Proxy toolsProxy CheckerPaste your proxies and find out which ones really work: the checker opens a tunnel through each one and reports the exit IP, protocol and response time.Explore

Forward, reverse and transparent proxies

The word “proxy” covers three different deployments, and mixing them up causes much of the confusion around the topic. A forward proxy is the kind you buy: your client is configured to send its requests to it, and it acts for you toward the open internet. A reverse proxy faces the other way. It sits in front of a website’s servers, accepts connections from visitors and passes them to one or more back-end machines, which is how load balancers, CDNs and web application firewalls work. A transparent (or intercepting) proxy is installed in the network path and catches traffic without any client configuration, a setup common on corporate and school networks.

Everything sold on BuyProxy is a forward proxy that you configure yourself. This matters when you read error messages. A 407 status always comes from your forward proxy, while a 502 or 504 can come from either side: the proxy you configured, or the reverse proxy in front of the website you are trying to reach. Work out which hop produced the error before you change anything.

Anonymity levels describe headers, not invisibility

Older proxy lists label proxies as transparent, anonymous or elite. These labels describe only which HTTP headers the proxy adds. A transparent proxy passes your original address along in headers such as X-Forwarded-For or Forwarded and announces itself with a Via header. An anonymous proxy withholds your address but still reveals that a proxy is in use. An elite, or high-anonymity, proxy sends neither. Headers are only one signal. A site can also match the connecting IP against commercial IP databases, inspect the TLS handshake of your client, and compare cookies and browser fingerprints with what it saw before. So an “elite” label says nothing about whether a site will treat you as an ordinary visitor. To confirm your own setup, load the IP address checker through the proxy and verify that the address it reports is the proxy’s and that your real address appears nowhere.

What each party on the path can see

It helps to list the observers and what each one can learn, because this is where beginners most often overestimate what a proxy protects.

  • The destination website sees the proxy’s IP address plus everything your client sends: headers, cookies, user agent, language and the timing of your requests. It does not see your real address unless a header or a leak exposes it.
  • The proxy operator sees, for HTTPS destinations, the hostname and port named in the CONNECT request, when the connection happened and how many bytes moved, but not the page content, because TLS is negotiated end to end with the site. For plain http:// URLs the operator can read the full request and response.
  • Your local network, such as Wi-Fi, an employer or your ISP, sees that you connect to the proxy’s address and port. Unless the proxy itself is reached over TLS, that first hop is not encrypted, so an on-path observer can read the destination hostname and the proxy credentials.

Two rules follow. Never install a root certificate that a proxy provider asks you to trust, because a proxy holding one can decrypt HTTPS, and ordinary proxy use does not need it. And treat proxy credentials as secrets that can leak on untrusted networks, since HTTP Basic authentication is only Base64-encoded and SOCKS5 username/password is sent as plain text on the hop to the proxy.

One request on the wire

Seeing the real messages makes the abstract steps concrete. For an HTTPS site, an HTTP proxy receives a CONNECT request naming the destination, checks the Proxy-Authorization header and answers 200 once it has connected. From then on the connection is a raw byte tunnel, and the TLS handshake with the destination happens inside it.

HTTP
CONNECT example.com:443 HTTP/1.1
Host: example.com:443
Proxy-Authorization: Basic dXNlcjpwYXNz

HTTP/1.1 200 Connection established

The value after “Basic” is just the Base64 form of user:pass, which is why it provides no secrecy. For a plain http:// destination there is no tunnel: the client puts the full URL in the request line and the proxy forwards the request, so it can read, cache or alter it. When credentials are wrong the proxy answers 407 Proxy Authentication Required with a Proxy-Authenticate header. That status exists only for proxies, which lets you tell bad proxy credentials from a 401, which comes from the destination site.

Authentication: credentials or an allow-list

A proxy needs a way to know you are a customer. Username and password is the common method and works from any network, but every tool you use must be able to send the credentials. An IP allow-list (whitelist) instead trusts connections that arrive from registered source addresses. Nothing is sent, so tools without authentication support work, but it breaks when your own address changes, and it grants access to everyone who shares your NAT address. Which methods exist depends on the plan: datacenter plans list username and password, and static mobile plans list whitelisting in the customer panel. Check the order page of your plan for the exact options.

A three-minute smoke test

Before building anything, confirm the proxy works with a tool that has no moving parts. curl is available on Windows, macOS and Linux. The first command below uses an HTTP proxy and the second a SOCKS5 proxy with remote DNS; both print the address the target saw.

Bash
curl -x http://user:pass@proxy.example.com:8080 https://api.ipify.org
curl -x socks5h://user:pass@proxy.example.com:1080 https://api.ipify.org

Add -v to see the CONNECT exchange or the SOCKS5 negotiation. If the printed address is the proxy’s, the tunnel works. Next, run the proxy checker for latency and the IP information tool to see which network the address belongs to.

Reading the first error

  • 407 Proxy Authentication Required: wrong credentials, or your source IP is not on the allow-list.
  • Connection refused: nothing listens on that host and port. Check the port and the protocol, because an HTTP client pointed at a SOCKS5 port fails in the same way.
  • Timeout: a firewall drops your packets, the proxy is overloaded, or the port is wrong in a way that gets no reply. The port checker shows whether the TCP port answers at all.
  • 403 on CONNECT: some proxies allow tunnels only to selected ports such as 443, so a destination on an unusual port can be refused.
  • The proxy works but the target blocks you: the proxy did its job and the site dislikes the IP, the rate or the client. Debug the target side, not the proxy.

Frequently asked questions

Is a proxy the same as a VPN?

No. A VPN typically tunnels all device traffic through an encrypted link; a proxy forwards the traffic of a configured application or request and may not encrypt it.

Are proxies legal?

Using a proxy is legal in most places, but what you do with it must be lawful and comply with the terms of the sites you visit.

Can a proxy owner read my passwords on HTTPS sites?

Not the page content. HTTPS is encrypted between your client and the destination, so the operator sees only the hostname, port and volume of traffic. Plain http:// sites are different, because the operator can read form data in clear text. Never install a root certificate from a proxy provider, since that is what would allow decryption.

Will a proxy make my connection faster?

Usually not. Your traffic takes an extra leg, from you to the proxy and from the proxy to the site, so latency is roughly the sum of both legs. Caching proxies inside corporate networks can speed up repeated downloads, but proxies sold for IP location do not work that way. Throughput depends on the network behind the proxy and on distance, so measure with your own targets.

Why does a website still seem to know I am using a proxy?

A proxy changes your IP address and little else. The address may be registered to a hosting company, appear in an IP-intelligence database, or clash with your browser’s time zone, language and fingerprint. Browser features such as WebRTC can also expose a different address. The IP information tool shows who owns an address, which is a useful first check.

Not sure which plan fits?

Describe your use case and target countries and we will recommend a product — or tell you honestly when another type suits you better.