I thought there was a different redirect on ipv6 for a moment, maybe there was for a short time.
x.com on ipv4 maps to 104.18.16.213 and ipv6 maps to 2606:4700::6812:10d5 and that right now is a cloudflare server with a 302 redirect to “https://.twitter.com” most importantly is, SSL doesn’t work on it. It fails with an ssl error on curl.
Seems like it goes to .twitter.com now, which my browser refuses to load because of the . in front of it
I thought there was a different redirect on ipv6 for a moment, maybe there was for a short time.
x.com on ipv4 maps to 104.18.16.213 and ipv6 maps to 2606:4700::6812:10d5 and that right now is a cloudflare server with a 302 redirect to “https://.twitter.com” most importantly is, SSL doesn’t work on it. It fails with an ssl error on curl.
So, yeah. Quite a funny mess up.
He literally just fixed it, and he learned nothing from this, Dunning-Kruger as strong as always.