Chrome now marks HTTP pages as “Not secure” if they have password or credit card fields. When Google releases its next Chrome 62 in October 2017, all HTTP sites with forms will be marked “Not secure.” E.g., blogs with comments and search boxes. Also all HTTP pages visited in Incognito mode. This is an example of what it’s going to look like:
The “Not secure” message will appear after user starts typing into the text field. Eventually, Google will mark all HTTP sites as “Not secure.” Example:
To prevent that from happening to your website, you’d have to get a security certificate and migrate to HTTPS (the “S” at the end of that abbreviation stands for “Secure”).