Oh nevermind, "ip" works. It used to be "ip address" I think, and that doesn't work anymore. Still gotta be on google.com, the .nl version doesn't do it. And of course, google.com redirects to .nl without /ncr...
I wish a service would provide me with both my IPv4 and IPv6 address...
Google hands me back my IPv6/IPv4, internatddress.me hands me back my IPv4, ipchicken IPv4, jsonip IPv4, ip.webscript.io IPv4, ifconfig.me IPv4, wtfismyip IPv4/IPv6, DDG IPv4.
And some of them bounce between the two ... I know, I know, happy eyeballs and all that, but it would be handy sometimes to know both my IPv6 address and my IPv4 address.
jsonip.com will have this relatively soon. Its been a pain in the ass to setup, much less test. I've tried going through the tunnelbroker tutorials a few times but keep hitting a mental brick wall. I, and perhaps others, need a simple 1-2-3 tutorial.
It's not possible to determine both your IPv4 and IPv6 address in a way that's compatible with curl or links, however. You need something like JavaScript to issue the second request.
A while back, we were using zoneedit.com to keep track of changing DSL addresses at some of our offices. We had a little daemon running that checked the external IP every 15 minutes and shoulder-tapped zoneedit if there was a change. It started failing after a while, and we discovered the external server we were using to query our IP was wigging out.
So we googled for some alternatives. None were much good. So we wrote two of our own, one hosted at the company's main site and one at a free Google App Engine site. That was a good move, as both mostly outperform the various freebies out there.
Along the way, I wrote a little script to test a bunch of alternative IP sources. Just for fun, I added a version of your Google query to the mix, along with the OP's site, and just reran it, with the following results:
The Google hack got the wrong IP. I assume the reason is that script is downloading the page and parsing out the first thing that looks like an IP address it comes across, but the part of the Google response that shows your IP bold and clear occurs further down in the result. So, it could be made to work, but would require a less trivial parse.
BTW, FWIW, www.[cynwoody's company].com is hosted at FutureQuest. Attaboy FutureQuest!
And internetaddress.me did best of all, responding in only 74 ms (I'm located in the Boston area), but one has to wonder what popularity will do.
There's a CSS issue that made me a bit irritated. The <body> element has a margin of 8px, change that to auto so you won't get an annoying horizontal scroll on webkit browsers.
Because the IP address assigned to the box may not be the IP address it is visible to the outside world on?
The output of ifconfig on my mac is dramatically different from what http://jsonip.com/ is showing me, and for good reason.
In addition to standard NATing, if he were on an EC2 instance, the IP addresses are routed to by Elastic IPs, and aren't necessarily visible from the box itself either.
Simply put, there are a variety of reasons you wouldn't necessarily want to rely upon the system's local IP address as canon for what others might see it as.