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 10.1.128.240
The connection IP shows up as 216.73.216.91

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.

HTTP_ACCEPT_ENCODINGgzip, br, zstd, deflate
SCRIPT_URIhttp://www.leaky.org/ip_tester.pl
HTTP_ACCEPT*/*
REQUEST_URI/ip_tester.pl
HTTP_CACHE_CONTROLmax-age=259200
REQUEST_METHODGET
HTTP_USER_AGENTMozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
QUERY_STRING 
HTTP_CONNECTIONkeep-alive
SCRIPT_URL/ip_tester.pl
SERVER_NAMEwww.leaky.org
HTTP_VIA1.1 squid-proxy-5b96dc6d46-5prjn (squid/6.13)
REMOTE_PORT39563
HTTP_HOSTwww.leaky.org
CONTEXT_PREFIX 
GATEWAY_INTERFACECGI/1.1
REQUEST_SCHEMEhttp
REMOTE_ADDR216.73.216.91
SERVER_PORT80
HTTP_X_FORWARDED_FOR10.1.128.240
SCRIPT_NAME/ip_tester.pl
SERVER_PROTOCOLHTTP/1.1
SERVER_ADDR82.145.59.7
SERVER_SIGNATURE 

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.