­

HTTPS is "SAFE", right?

Well - the simple answer is "maybe"...
For some time now we have been led to believe that websites using HTTPS (with the green lock) are "SAFE" but that is really a bit of a misnomer. They ARE (normally) safe as far as data flow between you and them goes since it ensures the data is encrypted. You should never enter personal information or especially highly sensitive information on a website that still uses HTTP (absence of the "S") as it is indeed not secure. In that case, any information that passes between you and them is "readable" in plain text for anyone that has access to that data connection. Before you are are too quick to dismiss that, remember that your connection to any website is not just direct between you and them but usually goes though many "hops" before it gets there.

is HTTPS good then?
Absolutely! It is best and that's why browsers are pushing it. Chrome will soon auto direct there for all sites and that - in of itself - is a good thing. But just remember - an HTTPS site is encrypted and is safe in that sense alone. It does not make any claim to the trustworthyness or validity of the site beyond the HTTPS connection when it is verified legitimately (lock symbol).

Certainly, the article below prompted this...
It is about the "new" Chrome 90.

Have a look.
But just don't be fooled by a false sense of security!

 

Chrome 90 to Force HTTPS - but not all sites are created equal

Comments and articles posted or linked here are for your interest only. We do not make any claims as to their absolute accuracy or their source.
Please check with the respective poster should you have questions of that nature.
­