Our accuracy rate is currently around 99.6% so we're doing pretty well but of course I don't think it can ever be 100% either.

The biggest thing we've come across so far is geo-sensitive handling of requests. Some sites will redirect you to HTTPS or not based on where you are making the request from! This of course means you might see HTTPS and we see HTTP.

I think it's still fair to include those sites in this case because they aren't serving all traffic securely.

Hey, thanks for the extra insight, I do appreciate. Interesting to know that those sites show these behaviours too. Why could geo-location based redirect be interesting?

My guess would be that maybe sites have different infrastructure in different regions and maybe they aren't completely aligned on their progress. I really don't know why you'd intentionally have it like that.

I thought about country restrictions as well. I noticed most of the offending websites were in China. Wondering is having SSL there is not allowed or something.

The real title should be "Why no HTTPS redirect", but it would be longer. Everything is explained clearly on the website.

It doesn't work every time for me. If i open it in a new private session (chrome or firefox) there is no redirection... Probably a faulty configuration on their side.

So do I, I guess an automatic redirection to https from http is expected.

I noticed in Canada several banks were listed. But they go to SSL.