Proxy Detection
Each request is checked with a fixed set of signals (rDNS, reputation, Tor, location, and HTTP headers) to decide whether it is routed through a proxy, VPN, or datacenter.
No proxy detected
Confidence: high
No proxy detected (reverse-proxy traffic is expected infrastructure)
Proxy check
| Test | Result | Detail |
|---|---|---|
| rDNS Test | FALSE | No reverse DNS (PTR) record was found for this address. |
| WIMIA Test | FALSE | No proxy/VPN reputation list is configured; ASN heuristic only. |
| Tor Test | FALSE | The client address is not present in the Tor exit-node list. |
| Loc Test | FALSE | Geolocated to Columbus, US. |
| Header Test | FALSE | Only standard reverse-proxy headers were seen (expected behind nginx/CDN), so this is treated as infrastructure. |
Detected proxy headers
Reverse-proxy infrastructure headers (expected behind nginx/CDN):
x-forwarded-for216.73.216.114x-forwarded-protohttpsx-real-ip216.73.216.114
Connection details
- Trust proxy
- Enabled
- Socket peer
172.20.0.18- Trusted address
216.73.216.114- Forwarded chain
-
216.73.216.114 - Geo
- Columbus, US