What is a reverse proxy?¶

A reverse proxy is a public-facing service that receives requests for a website and forwards them to another server behind it.

Why place a service in front?¶

The proxy can encrypt connections, filter malicious traffic, balance demand across servers, cache responses and keep the origin server from being directly exposed. Content-delivery networks often perform reverse-proxy functions, although a reverse proxy does not have to be a distributed CDN.

Think of it as a staffed reception desk. Visitors deal with reception; reception decides which internal office should receive each request. The public sees the reception address, not necessarily the room where the work happens.

DNS and connection records may therefore identify the proxy provider. That address may serve many unrelated customers. The proxy can still be an evidence holder: possible records include the customer account, configuration, security events, requests and the destination to which traffic was forwarded.

The origin host may hold different evidence, including content, server access and administrator activity. Historic DNS, configuration and provider records may be needed because both layers can change.

Do not attempt to bypass a protective service merely to discover the origin. That may interfere with systems, alert an operator or produce unreliable results. Use appropriate records and specialist support.