In fairness, DNS entries do get cached for a while (usually 24 hours), so you might have gotten a stale version of the resource record. It’s even entirely possible that whatever DNS resolver Musk uses did have the up to date version already while yours did not.
Still, Twitter should double and triple checked that this works even from other resolvers before announcing it like this.
Right, the head twit, the one who “doesn’t need” to ever consult with domain experts from his own companies, because he “knows” he’s right about everything anyway…
Replacing a notable, at this point ingrained part of modern internet culture, to the letter “X” LMAO. Elon just doing whatever to stay in the headlines.
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.
Not necessarily, more like GoDaddy was the domain swatter that was holding on to that domain until Musk decided to pay the ransom. We cannot tell from the screenshot what registrar he uses for that domain now.
We can, however, tell from whois, and what do you know, it’s godaddy…
Godaddy AND cloudflare. twitter.com doesn't use either, which coupled with the typo on the redirect makes this really feel like a very Musk initiated thing going on here.
Add comment