Odd. I get a full fledged HTML 404 page.
Comment on Twitter API has a list of users who are allowed to use racial slurs
ryannathans@aussie.zone 4 months ago
Url does not resolve to an IP address
AVincentInSpace@pawb.social 4 months ago
ryannathans@aussie.zone 4 months ago
What dns server resolves the site?
AVincentInSpace@pawb.social 4 months ago
I tried to visit the site again when I saw your comment and the site had disappeared by then. Fascinating. It must have been taken down and the change took a while to propagate.
Nasan@sopuli.xyz 4 months ago
I’m currently overseas in SE Asia, it resolves to a local address (10.3.1.1) with a cname record pointing to an AWS load balancer with 3 separate IPs through my ISP’s DNS server. protected-users.twitter.okta.com still appears across a few different DNS records according to dnschecker.org at the time of my post.
biscuitswalrus@aussie.zone 4 months ago
I checked too, it’s not a valid public DNS record, so then the question is, does Oktas DNS resolve this. Even if it does, how does okta even sit in this? Are they the identity provider for Twitter? Surely even if it’s identity, it’s got nothing to do with content moderation? So many questions.