Welcome to WebmasterWorld Guest from 18.104.22.168
Forum Moderators: open
Studies show that users do not perceive the lack of a “secure” icon as a warning, but also that users become blind to warnings that occur too frequently. Our plan to label HTTP sites more clearly and accurately as non-secure will take place in gradual steps, based on increasingly stringent criteria. Starting January 2017, Chrome 56 will label HTTP pages with password or credit card form fields as "not secure," given their particularly sensitive nature.Google Chrome Will Mark HTTP Sites Transmitting Passwords or Credit Cards as Non Secure [security.googleblog.com]
Your connection is not secure
The owner of [ target.com | macys.com ] has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website.
[ target.com | macys.com ] uses an invalid security certificate. The certificate is only valid for the following names: a248.e.akamai.net, *.akamaized.net, *.akamaihd-staging.net, *.akamaihd.net, *.akamaized-staging.net
eventually all sites not HTTPS will get a not-secure warning... the red triangle.Is that really the case for all HTTP sites or the ones with password fields? I don't really see a reason for Chrome to display the red triangle on HTTP sites that doesn't have any input fields?!
Long term - Use HTTPS everywhere
Eventually, Chrome will show a Not Secure warning for all pages served over HTTP, regardless of whether or not the page contains sensitive input fields. Even if you adopt one of the more targeted resolutions above, you should plan to migrate your site to use HTTPS for all pages.