I thought it looked like some configuration error. It reminded me of a similar situation...
We were working with an ISP where the shared web server configuration would occasionally get confused. We'd add a new domain or sub-domain and it would take a bit for the system to synch up and show the new site 100% of the time. Meanwhile, instead of the soon-to-be-available-site, the server would show the "first" site in the configuration file. That site was...odd. Not so much
NSFW, but just ... weird.
We convinced them to set up a "The site you were tryng to visit will be available shortly" page and make
that the first-in-config site. It's been much better...