I&#x27;ve been wondering about the value of these warnings to the 99% of end users who have no idea what HTTPS is, and who have even less understanding of why a site whose URL begins &quot;<a href="https:&#x2F;&#x2F;&quot;" rel="nofollow">https:&#x2F;&#x2F;&quot;</a> would be insecure. Firefox uses icons to indicate different situations but even I don&#x27;t know what they mean.<p>I think the browsers need to indicate simply that the website is &quot;secure&quot; or &quot;not secure&quot;, with some transparency for advanced users to obtain more details. Don&#x27;t give end users information they don&#x27;t understand about a topic they also don&#x27;t know about and expect them to draw the right conclusion (in the miliseconds they spend thinking about each website); it will fail in its goal almost every time. (In a way, it&#x27;s the same approach as click-wrap legaleze.)<p>That doesn&#x27;t solve another problem: Properly implemented HTTPS doesn&#x27;t really mean &quot;secure&quot;; it just means one component likely is secure. The site could be scam, user data could be exposed many other ways, HTTPS has vulnerabilities, etc. I don&#x27;t know how to effectively inform end-users about those complexities.