I checked too, it’s not a valid public DNS record, so then the question is, does Oktas internal 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.
I tried to visit the site again when I saw your comment and discovered the DNS record had disappeared between when I wrote that comment and now. Fascinating. It must have been taken down and the change took a while to propagate. Judging by the fact that I could see anything at all before my ISP’s nameserver got the memo, the 404 page that was there seems to still be up even though the DNS record that got you to it is gone – wish I had thought to nslookup it when I still could. If I had to take a guess, though, it probably resolved to the same IP address as the twitter.okta.com domain.
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.
Url does not resolve to an IP address
I checked too, it’s not a valid public DNS record, so then the question is, does Oktas internal 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.
Odd. I get a full fledged HTML 404 page.
EDIT: https://archive.ph/c49ul
What dns server resolves the site?
I tried to visit the site again when I saw your comment and discovered the DNS record had disappeared between when I wrote that comment and now. Fascinating. It must have been taken down and the change took a while to propagate. Judging by the fact that I could see anything at all before my ISP’s nameserver got the memo, the 404 page that was there seems to still be up even though the DNS record that got you to it is gone – wish I had thought to nslookup it when I still could. If I had to take a guess, though, it probably resolved to the same IP address as the twitter.okta.com domain.
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.