IP ADDRESS TESTER

If you suspect your ISP is doing something strange to your HTTP access like pushing it through a transparent proxy, you can check what should be direct access at https://www.leaky.org/ip_tester.pl instead.

Checking

Your X-Forwarded-For header is
The connection IP shows up as 54.80.185.137

That IP isn't a known web-proxy so we'll just assume this is your actual IP address.
If it is in fact the IP of a web-proxy (run by your ISP), let me know.

Status from checking is one of Unknown, FOUND, NONE or FAILED. Yours is NONE

Browser Headers

For your information, here are some other values relating to your web access.

SCRIPT_NAME/ip_tester.pl
SERVER_NAMEwww.leaky.org
HTTP_ACCEPT_ENCODINGx-gzip, gzip, deflate
REQUEST_METHODGET
HTTP_ACCEPTtext/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
SCRIPT_URIhttp://www.leaky.org/ip_tester.pl
QUERY_STRING 
REMOTE_PORT55332
HTTP_USER_AGENTCCBot/2.0 (http://commoncrawl.org/faq/)
SERVER_PORT80
SERVER_SIGNATURE 
REMOTE_ADDR54.80.185.137
SERVER_PROTOCOLHTTP/1.0
REQUEST_URI/ip_tester.pl
GATEWAY_INTERFACECGI/1.1
HTTP_IF_MODIFIED_SINCEThu, 22 Feb 2018 02:27:59 GMT
SCRIPT_URL/ip_tester.pl
SERVER_ADDR213.229.84.132
REMOTE_HOSTec2-54-80-185-137.compute-1.amazonaws.com
HTTP_HOSTwww.leaky.org

Status Meanings:

Unknown
You should never get this status!
FOUND
The connection IP is a known webproxy. Processing of X-Forwarded-For header succeeded in getting what is probably your real IP
NONE
Connection IP is not a known webproxy. Assuming that to be your actual IP.
FAILED
Connection IP is a known webproxy but either there was no X-Forwarded-For header or processing it failed in some way.

Contact

Tester written by Simon - email website (at) leaky.org
Please feel free to check out my site at leaky.org which has links to my other sites.