I tend to agree.  There is so much that SSL&#x2F;TLS doesn&#x27;t validate that I don&#x27;t have a strong security expectation.  The web server could be some pre-release accidentally pushed to production.  The software I&#x27;m talking to on the other end could be bug central.  The employees at the company could be untrustworthy.  The site could be compromised.  Someone could be sniffing traffic between frontends and backends (&quot;SSL added and removed here! :-)&quot;)<p>All the lock icon says is &quot;someone who made a request to the CA controls the other end of the connection&quot;.  Usually this means you aren&#x27;t being MITM&#x27;d by one of your ISP&#x27;s or WiFi hotspot&#x27;s ad insertion proxies.  That&#x27;s about it.<p>If the CAs start wanting to verify organization software engineering practices and issue different certificates based on the outcome of the audit, that&#x27;s fine.  But that&#x27;s not my current expectation.