This is the error message I got, along with the URL showing the https crossed out in red:
Your connection is not private
Attackers may be trying to steal your information from time.com (for example, passwords, messages, or credit cards). NET::ERR_CERT_COMMON_NAME_INVALID
I guess I don’t need to be on an https URL to visit Time.com, but still… makes you wonder.
All Things Chronic 
Perhaps I misunderstand you, but are you saying that Time Magazine is willing to potentially damage their reputation just to make it so that users will connect to their website via an insecure connection?
(Fyi, that’s not a criticising question; I mean it genuinely. I want to make sure that I understand you correctly.)
LikeLiked by 1 person
I’ve received this error message on more than one occasion for Time.com. In fact, I just typed Time.com in my browser, and got the same message. I’m not sure what it means, but when it happens, I’ve always clicked on, “go back to safety.”
LikeLike
YIKES!
LikeLiked by 1 person
I too have had multiple instances. It’s very frustrating. A few things I have been able to determine, though, are that
a. If I block all HTTP connections, it will not work at all; I get an error message saying an extension is blocking the site (clearly the one I used to block all HTTP. Lol.).
b. It works perfectly fine on an HTTP connection.
c. Weirdly enough, after switching to HTTP, it started working just fine after I switched back to HTTPS, even if I were to block all HTTP requests.
LikeLiked by 1 person