>Only(in general) thing that it provides is content encryption which is going through internet. If you hosting public website, this content is already publicly

>Only(in general) thing that it provides is content encryption which is going through internet. If you hosting public website, this content is already publicly available. Why are you confusing https encryption with private vs publicly available information? Let's unpack your concepts a bit using COVID-19 as an example[0]. The information that Wikipedia displays about COVID-19 is public information instead of top-secret classified files. But you'll notice that wikipedia serves its pages as "https". Think about why they do that. Even if you manually type "http" without the "s" in your web browser url bar[1], Wikipedia will still redirect you to "https". Why do they do that if COVID is public information? As a web surfer, I also want wikipedia to serve its pages with "https". Think about why I would want that. [0] https://en.wikipedia.org/wiki/COVID-19_pandemic https://en.wikipedia.org/wiki/COVID-19_pandemic [1] this will still redirect to https: http://en.wikipedia.org/wiki/COVID-19_pandemic http://en.wikipedia.org/wiki/COVID-19_pandemic