the issue is that these return a bunch of html so using them from the command line is not ideal.

I made wgetip.com back in 2008 to solve this. icanhaz must've been pretty suboptimal back then to have issues with traffic. wgetip still gets about 3M requests per hour. All from a single $5 droplet.

ip4.me and ip6.me have /api endpoint for programmatic access

The /api endpoint seems to return me a 301 error from the command line.

That’s a redirect, not an error. Probably to /api/ with a trailing slash. Or use the -l flag to curl to have it auto redirect.

  curl https://ip4.me/api/

works for me

There, /ip is better.

Best thing to try first is to append /ip I've found.

For wgetip.com that is not needed of course. But I haven't found a way to get the IPv4 address there...

https://www.ipify.org/ is my go to, mostly because it has a really simple JSON version. Funny how many ways there are to do this simple thing.

https://api.ipify.org/ works to just get text IP.

Does Chrome not recognize the .me TLD? I just tried to type that ip4.me domain twice and it just sent me to search results.

Edge works just fine which is interesting.

I think that would be very surprising to the fine people of Montenegro.

Check your local DNS configuration, something is likely hijacking NXDOMAINs.

Works for me (heh).

I like ifconfig.me because it returns the IP along with some other little bits of useful information, and works great with curl

Icanhazip.com will do the same.

They have ipv4.icannazip.com and ipv6.icannazip.com where they will return that.

so 3, 2 less memorable sites, ok got it

I’d say that is up you. I can never remember what tld those other sites used. I’ve been using icanhazip since many years. I seem to remember it fine.

Replace the double nn in your post by nh and it will work better ;-)

Thanks. Phone keyboards are hard sometimes.

ipinfo.io's API and site is dualstack. But for IPv6 connection, you need to use v6.ipinfo.io for the API service.

Even though nobody asked, I have to mention this every time there is a discussion about IPv6 and IP address data. According to domain name records, even if a site supports both IPv4 and IPv6 it defaults to IPv6. I would love to know why.

I have come across a lot of people saying IPinfo doesn't support IPv6. The internet as an ecosystem doesn't completely support IPv6, but we do. So, mentioning it constantly in every discussion is my current approach.

> According to domain name records, even if a site supports both IPv4 and IPv6 it defaults to IPv6. I would love to know why.

Newer is better? Good clients use the 'happy eyeballs' (rfc 8305) mechanism, which is roughly, open v6, wait a bit, open v4, use whichever connection comes back first. There's a bias towards v6 because often it's a more direct connection, and may work better, but it was also common to have non working AAAA records, so a delayed fallback is preferable to no fallback as used to be common.

Don't forget about the new still-draft-but-already-used HTTPS DNS record type (no, that's not a typo)! I'm still fuzzy on its IP hint value(s) but it can potentially bypass A and AAAA records completely.

When helping someone over the phone, I get them to go to http://ipchicken.com

Very easy URL to relay, "do you see the chicken? let me know what the blue numbers are below it" - and most people seem to get a kick out of it!

A long time ago I spent a bit too long debugging something to later find out the "source port" that displays isn't right! It's still not right! I obviously fixed this by making my own site (https://ip.wtf).

Great service! Very informative. If you could also implement ip.wtf/ip or some such, it might decrease your bandwidth..!

Thanks!

No need for a /ip, just doing:

$ curl ip.wtf

... will do the right thing, or if your user-agent isn't curl send a header of "Accept: text/plain" and you'll get the plain text version (see https://ip.wtf/about for more).

And no need for an IPv4 or IPv6 mode url/param since curl -4 or curl -6 will do the trick!

Gives a CloudFlare 520 error for me...

And if you attach /ip you get only the IP address (as /api also includes the URL of the documentation).