Note to self… Finding your IP address when HTTP is proxied

Due to … issues with my home Internet service at the moment, I’m currently tethered to an EE mobile phone for my outbound Internet access. For 99.9% of access, this is fine, however… not when you create dynamic security groups based on your own IP address. For whatever reason (I’m guessing they’re doing HTTP(S) proxying to perform some traffic analysis) when you make HTTP requests, you appear as one IP address, but when you make any other type of request, you get another.

In order to test this, I ran some checks (I’ve changed the first three octets for privacy);

# DNS Check
$ dig +short txt ch whoami.cloudflare @
# HTTP Check
# HTTPS Check
# SSH Check
$ ssh
The authenticity of host ' (64:ff9b::313:6f08)' can't be established.
RSA key fingerprint is SHA256:OhNL391d/beeFnxxg18AwWVYTAHww+D4djEE7Co0Yng.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '' (RSA) to the list of known hosts.

"comment": "##     Your IP Address is (54140)     ##",

"family": "ipv4",
"ip": "",
"port": "54140",
"protocol": "ssh",
"version": "v1.3.0",
"website": "",
"sponsor": "Sponsored by ConvergeOne,"
 Connection to closed by remote host.
Connection to closed.

So, I guess, what this tells us is that I can’t guarantee what IP address I’ll be using, but at least I know it’s one of those two!


He/Him. Husband and father. Linux advocating geek. Co-Host on the AdminAdmin Podcast, occasional conference speaker.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.