What records might a reverse-proxy provider hold?¶

A reverse proxy receives public requests and passes them to a service behind it. Its records can therefore help identify both the customer-facing endpoint and the hidden origin.

Configuration, access and traffic¶

Account and billing records may identify the customer. Configuration may show domains, certificates, routing rules and origin addresses. Administrative logs can record who changed those settings and when.

Request logs may show the hostname, path, source address, timestamp, response and destination used. Security systems may record blocked requests, attacks or abuse reports. Availability varies because logging may be optional, sampled or retained briefly.

The proxy is like reception in a secure building: it may record visitors and the internal room contacted, while the work and documents remain inside that room.

Historic configuration can be more important than the current setup. Origins change, routes are updated and accounts transfer. Provide exact hostnames and times when seeking a period-specific answer.

The origin value identifies the next technical destination, not automatically the operator. It may lead to another proxy, cloud service or reseller.