This request appears NOT to have come via a proxy.
The request appears to have originated from host ec2-50-19-34-255.compute-1.amazonaws.com which has ip address 184.108.40.206
The Lagado Proxy Test shows details of any proxy servers you are using. It is especially useful to expose transparent proxies. These are proxies inserted between your browser and the web, typically by your ISP, and often without you knowing.
Sometimes a proxy will be deliberately hidden so it won't be exposed by this test. In this case you can use the Cache Test to expose stealthed transparent proxy caches.
The Raw Details
Here are the raw details of the request received by this server.
Remote Host ec2-50-19-34-255.compute-1.amazonaws.com IP Address 220.127.116.11
Request Protocol HTTP/1.0 Method GETRequest Headers
|Accept-Encoding||x-gzip, gzip, deflate|
|If-Modified-Since||Sun, 17 Dec 2017 15:52:50 GMT|
Date: Wednesday 21 Feb 2018 0:09:21 GMT+1100
Please Note: The conclusion that the request did not come via a proxy is based on the absense of the Via, Forwarded, X-Forwarded-For and Client-ip headers. It is still possible that a proxy is handling the request without announcing itself in the recommended way. (see rfc2616 & draft-ietf-http-v10-spec-01 & Squid Configuration Guide & Squid Release Notes 1.1)
Update 08 Feb 2002 by Lagado: Added support for Client-ip header used by some transparent proxies. See more background.
Update 30 Apr 2001 by Lagado: Added Cache-Control: no-cache header to proxy-test responses. This discourages HTTP/1.1 compliant proxies from returning cached test results. Also freshened the document references.
Copyright © 2000 Lagado. First release 21 May 2000