Skip to content
AdminKit

Reverse proxy

What is Reverse proxy?

A reverse proxy is a server that sits in front of one or more backend servers and forwards client requests to them, so clients only ever see the proxy's own address. AdminKit's HTTP Headers tool inspects response headers like X-Forwarded-For and Via that often reveal a reverse proxy in the path.

By AdminKit team, Netbase JSC · Updated

A reverse proxy is a server that sits in front of one or more backend servers and forwards incoming client requests to them, returning the response as if it came from the proxy itself. Clients only ever see the reverse proxy’s address, never the backend servers directly, which lets an operator load-balance traffic across multiple servers, terminate TLS in one place, cache responses, and hide internal network layout. This is the opposite of a forward proxy, which sits in front of clients and forwards their requests outward on their behalf. It operates at the application layer rather than translating addresses the way NAT or manual port forwarding do at the network layer, though all three can end up hiding what’s really behind a single public-facing address. Reverse proxies commonly add or rewrite headers such as X-Forwarded-For and Via as a request passes through, which is why checking response headers with AdminKit’s HTTP Headers tool often reveals that a reverse proxy, CDN, or load balancer is in the path even when the real backend stays hidden. nginx’s proxy module documentation shows the mechanism: its $proxy_add_x_forwarded_for variable is the client’s X-Forwarded-For header with the connecting address ($remote_addr) appended, separated by a comma, or just that address when the header is absent. The Apache HTTP Server reverse proxy guide describes the same role, where the server acts as a gateway in front of backend servers so that, to the client, the proxy looks like the origin, and the standardized successor to the ad hoc X-Forwarded-For header is defined in RFC 7239 (current document status at its IETF Datatracker entry).

Frequently asked questions

Is a reverse proxy the same as a CDN?

Not exactly -- a CDN typically uses reverse proxy servers distributed across many locations to cache and serve content closer to users, but a reverse proxy by itself is just the general role of standing in front of backend servers; not every reverse proxy is part of a CDN.

What's the difference between a reverse proxy and a forward proxy?

A reverse proxy sits in front of servers and forwards requests to them on the servers' behalf, hiding the backend from clients; a forward proxy sits in front of clients and forwards their requests outward, hiding the clients from the destination instead.

How can I tell if a site is using a reverse proxy?

Response headers often give it away -- a reverse proxy, CDN, or load balancer commonly adds or rewrites headers like X-Forwarded-For and Via as a request passes through, which AdminKit's HTTP Headers tool can show directly.

Does a reverse proxy see unencrypted traffic even over HTTPS?

Often yes -- a common reverse proxy setup terminates TLS at the proxy itself, meaning the connection from client to proxy is encrypted but the proxy can see the decrypted request before forwarding it on, possibly over a separate connection to the backend.