ipify-api
ipify-api copied to clipboard
ipv6 doesn't seem to be working
Ipify.org also doesn't have an aaaa record
Ipv6 examples are just empty with a ?
Working on fixing this.
Any update on ipv6 fix?
This is in the works now =) Will update here when I have more news.
Hi,
Since May, no evolution for IPv6 support ?
I'm assuming they do not have an IPv6 Address yet which is weird as even my server has one.
When IPv6 is available, can you do the following with it: Have 3 domains for the API. api.ipify.org Both A and AAAA records. api6.ipify.org Only AAAA records. api4.ipify.org Only A records.
This allows people to test if IPv6 is preferred, if IPv6 works, and find out what IPv4 or IPv6 addresses are individually.
The issue I'm having is:
- This is hosted on Heroku, which provides no IPv6 support.
- I've tried moving it to AWS / Elastic Beanstalk, but beanstalk doesn't support IPv6 yet either.
- I was considering moving it to digitial ocean direct, but the work required is too much for a service whose stability needs to be automatically managed.
As a result, I'm currently sorta just waiting for AWS to support IPv6 on Elastic Beanstalk so I can move it over without issue =/
Am open to other suggestions.
Could always use an he ipv6 tunnel.
http://ipv6-test.com/api/
More specifically: http://v6.ipv6-test.com/api/myip.php
Unfortunately it doesn't support https...
Ah, here we go:
https://myexternalip.com/raw
curl -6 https://myexternalip.com/raw
Beware: there's a sneaky nasty little newline at the end.
The web site mentions "It works flawlessly with both IPv4 and IPv6 addresses". Is that inaccurate at the moment?
I saw an interesting comment on an issue on another project pointing out that for IPv6 a service for finding your public address shouldn't really be necessary, since there's no real reason for using NAT with IPv6 addresses and you can just find your global address by inspecting your network interface configuration. Is that correct, or are there some circumstances where people are using NAT with IPv6 (other than NAT64, which is a whole other thing for providing IPv4 access to IPv6-only networks but not relevant to this issue)?
ipify.org is compromised? https://www.virustotal.com/en/domain/api.ipify.org/information/
Latest detected files that communicate with this domain Latest files submitted to VirusTotal that are detected by one or more antivirus solutions and communicate with the domain provided when executed in a sandboxed environment. 22/55 2016-06-22 18:06:07 dfd5d7645d4e91fd65f8d139f4b3ee102027aad6f121608eb58135ed1d53355f 2/56 2016-06-22 17:59:48 2b4ae8cb8d735448f666b9d683c3ad305bd2db6ebad68ccb398eebe5a5020e53 15/56 2016-06-19 23:45:58 2dcde260ace074a6af8ce4a52813539e56fa2d1eca09134e10f35a14369b5e12 27/54 2016-06-13 22:16:49 3aa5f8a594537302aae94964b8939eea5f6465b799bc6a3c9a1145423d07e75b 7/56 2016-06-12 16:25:40 89d1ab1f3e6b999f0955a2195585b78da43038aaf68f165e9ea6d720150f05ac 2/57 2016-06-06 19:18:30 180eee35d6471b03270bebc33df767796dba840d7f6276e383caa02851f2d583 2/57 2016-06-01 11:24:37 7d70823b6037794dd69ea7107666e1d467bad29a2de50e0ff8f4e731d50129d0 21/57 2016-05-31 12:45:53 9c79f5e61c218453e1c440458e8fe2681c80ab3b6f2dab4bcdcacc032cb8d1d9 25/57 2016-05-28 15:08:40 1ba2068957ef4ddf5bb108485ca6d80b55b67fb3b699670fcb3117ae95dbe818 29/57 2016-05-25 21:48:21 41f8897678e352350e904f8d48924b2d5092363224550bbd8d464a0552ab7d1f
@HarriL I do not see how ipify can be compromised if it is just a proxy to golang...
@JJC1138 My reason for having IPv6 support in ipify is so that I can verify that my IPv6 is working properly. Sometimes you see network issues and it is actually related to IPv6 vs IPv4.
@HarriL ipify is not compromised. A lot of these antivirus companies are completely insane, and think that because some random programmer wrote a virus that uses ipify to get the victim's IP address, that ipify is a bad domain (it is not). If people misused ipify, that's not my problem.
As a result, I'm currently sorta just waiting for AWS to support IPv6 on Elastic Beanstalk so I can move it over without issue =/
Am open to other suggestions.
You could use Cloudflare, the IPv6 address should then be in the X-Forwarded-For header.
Contact Digital Ocean. They host a number of open source projects. I bet this would be worthy of them.
https://twitter.com/coolaj86/status/829726921239908353
Ask, and it shall be given you; seek, and ye shall find; knock, and it shall be opened unto you:

Woa! That's amazing. I'll hit them up! Thanks everyone =D
Amazon is enabled IPv6 now, and main site seems running just fine, any plans to add AAAA record for api subdomain?
Any news on this?
Fixing this should be as easy as selecting "dualstack" as the address type for the load balancer.
It would be nice to at least mention on the front page that api.ipify.org doesn't support IPv6 as of now.
Otherwise, it says that
It works flawlessly with both IPv4 and IPv6 addresses, so no matter what sort of technology you're using, there won't be issues.
(it's technically correct that ipify itself supports IPv6, yet it's confusing since api.ipify.org doesn't)
I just spent an hour trying to figure out why ipify doesn't return my IPv6 address (and curl -6 even refuses to connect to it) while google.com does.
(I'm surely a newbie with IPv6 and my setup is somewhat complicated, but ipify added some more confusion to it)
Just in case somebody else stumbles upon this issue, have a look at https://github.com/mpolden/echoip Running at https://ifconfig.co/
I believe this just bit me and prevented ePAyco from working. On the other hand https://github.com/mpolden/echoip works fine. And indeed forcibly making my network IPv4 only makes api.ipify.org work.