That's normal and intentional: https://news.ycombinator.com/item?id=20584848

If it does lead to an HTTPS page, I believe that only happens when your browser tries HTTPS before HTTP (if it tries HTTP at all).

The irony has not gone unnoticed: https://twitter.com/NeverSSL/status/1456310362551164928

But that doesn't explain why they do it.

From my HN link:

> 1. Why does neverssl.com use Javascript to redirect to a random subdomain?

> Over the last year users reported that some networks aggressively cache the fake DNS and pages they use for wifi capture. Neverssl.com now works around this generating a request to a random subdomain - this will bust any DNS cache, and any HTTP cache. It also means that if your browser or ISP caches the Neverssl.com page itself, that's fine.

That doesn't explain why networks aggressively caching a fake DNS is a problem for their website without SSL redirects.

It doesn't do that for me.