I tried to visit the site again when I saw your comment and 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. The 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.
What dns server resolves the site?
I tried to visit the site again when I saw your comment and 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. The 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.