Chrome's long-term plan is to show no visual indicator for (valid) HTTPS, and a non-secure indicator for HTTP[1], so that's essentially what you're describing.

Chrome's long-term plan is to show no visual indicator for (valid) HTTPS, and a non-secure indicator for HTTP[1], so that's essentially what you're describing. IIRC Firefox has similar plans. HTTPS deployment numbers don't quite allow for that yet. [1]: https://www.chromium.org/Home/chromium-security/marking-http-as-non-secure https://www.chromium.org/Home/chromium-security/marking-http...