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.8.255.167
The connection IP shows up as 216.73.216.188

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.

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

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.