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.
Your X-Forwarded-For header is
The connection IP shows up as 34.231.180.210
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
SCRIPT_NAME | /ip_tester.pl |
REQUEST_METHOD | GET |
HTTP_ACCEPT | text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 |
REQUEST_SCHEME | https |
QUERY_STRING | |
REMOTE_PORT | 34950 |
HTTP_USER_AGENT | CCBot/2.0 (https://commoncrawl.org/faq/) |
SERVER_SIGNATURE | |
HTTP_ACCEPT_LANGUAGE | en-US,en;q=0.5 |
GATEWAY_INTERFACE | CGI/1.1 |
HTTPS | on |
SCRIPT_URL | /ip_tester.pl |
SSL_TLS_SNI | www.leaky.org |
UNIQUE_ID | ZuJbw2i9uXwm76nEvrQaGAAAAAk |
SERVER_NAME | www.leaky.org |
HTTP_ACCEPT_ENCODING | br,gzip |
HTTP_CONNECTION | Keep-Alive |
SCRIPT_URI | https://www.leaky.org/ip_tester.pl |
CONTEXT_PREFIX | |
SERVER_PORT | 443 |
REMOTE_ADDR | 34.231.180.210 |
SERVER_PROTOCOL | HTTP/1.1 |
HTTP_IF_MODIFIED_SINCE | Sat, 22 Jun 2024 13:30:16 GMT |
REQUEST_URI | /ip_tester.pl |
SERVER_ADDR | 78.129.196.11 |
HTTP_HOST | www.leaky.org |