# Reverse proxy

A reverse proxy is a server that sits in front of one or more origin servers and accepts requests from the public on their behalf, then forwards them internally. Load balancers, CDNs and API gateways are reverse proxies. It is the opposite of the forward proxies that proxy providers sell, and it is also the layer that scores incoming visitors on protected websites.


## Why it matters to proxy users

The bot-management layer of a large website usually runs at its reverse proxy or CDN edge. That layer inspects the visitor's IP address, its reputation, its autonomous system, the TLS handshake and the request rate, and decides whether to serve the page, a challenge or a block. Understanding that the decision is made there explains why the *kind* of exit address changes outcomes: a [residential](https://proxshift.com/glossary/residential-proxy) exit is scored like a home visitor, a [datacenter](https://proxshift.com/glossary/datacenter-proxy) range like hosting.


## Common reverse-proxy signals

- IP reputation and blocklists, refreshed continuously.
- ASN class: consumer ISP, mobile carrier, hosting provider.
- Request rate per IP and per session, with a low ceiling for hosting ranges.
- Consistency between IP geolocation, language headers and account country.


## How it works at ProxShift

ProxShift's own website sits behind a reverse proxy too, as most sites do. On the proxy side, the residential and mobile gateways are forward proxies; nothing ProxShift sells is a reverse proxy.

Source: https://proxshift.com/glossary/reverse-proxy