# Any fixes for Chrome's new security check? **URL:** \ **Category:** Miscellaneous and Personal Stuff I Must Share\ **Created:** [May 2, 2017, 12:45pm UTC](https://boards.straightdope.com/t/any-fixes-for-chromes-new-security-check/785713 "2017-05-02T12:45:50Z")\ **Posts on this page:** 5\ **Page:** 2
**Author:** ![Musicat](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/musicat/32/20189_2.png) [@Musicat](https://boards.straightdope.com/u/Musicat)\ **Post date:** [May 5, 2017, 4:56pm UTC](https://boards.straightdope.com/t/any-fixes-for-chromes-new-security-check/785713/21 "2017-05-05T16:56:16Z")
> [@arseNal](#): > > But you ought to investigate why YOUR chrome is having an issue with the certs on common sites where no one else is having problems. You’re treating the symptom, not the root cause. If you don’t feel it’s worth your time then that’s of course entirely up to you. It’s not worth a LOT of my time, especially since I have a sneaking suspicion that it’s a Chrome bug, and will eventually be fixed by them. And I just noticed that the prominent “not secure” notice next to the URL is not appearing anymore. I think I’ll try invoking Chrome without the no-cert option and see what happens. ---
**Author:** ![Musicat](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/musicat/32/20189_2.png) [@Musicat](https://boards.straightdope.com/u/Musicat)\ **Post date:** [May 5, 2017, 5:07pm UTC](https://boards.straightdope.com/t/any-fixes-for-chromes-new-security-check/785713/22 "2017-05-05T17:07:23Z")
Rebooting Chrome without the no-cert option…any site that uses https shows “secure” to the left of the URL. Http shows nothing. Godaddy’s sites replace the secure with GoDaddy INC. [US] and the https: is shown in color whenever it appears. I did nothing that I can think of to my computer that might have affected this. ---
**Author:** ![arseNal](https://avatars.discourse-cdn.com/v4/letter/a/ecae2f/32.png) [@arseNal](https://boards.straightdope.com/u/arseNal)\ **Post date:** [May 5, 2017, 5:08pm UTC](https://boards.straightdope.com/t/any-fixes-for-chromes-new-security-check/785713/23 "2017-05-05T17:08:53Z")
> [@Musicat](#): > > It’s not worth a LOT of my time, especially since I have a sneaking suspicion that it’s a Chrome bug, and will eventually be fixed by them. > > And I just noticed that the prominent “not secure” notice next to the URL is not appearing anymore. I think I’ll try invoking Chrome without the no-cert option and see what happens. Well, I take back part of what I said. I just tried that --ignore-certificate-errors flag myself and went to a server that I know has a problematic cert, and chrome still warned me about it. So it seems I was wrong about that part. ---
**Author:** ![Musicat](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/musicat/32/20189_2.png) [@Musicat](https://boards.straightdope.com/u/Musicat)\ **Post date:** [May 5, 2017, 5:20pm UTC](https://boards.straightdope.com/t/any-fixes-for-chromes-new-security-check/785713/24 "2017-05-05T17:20:56Z")
> [@arseNal](#): > > Well, I take back part of what I said. I just tried that --ignore-certificate-errors flag myself and went to a server that I know has a problematic cert, and chrome still warned me about it. So it seems I was wrong about that part. I think Chrome uses a different and possibly hybrid detection method for malware, not relying entirely on the certificate status. Those Chrome dudes may not be perfect, but they’re pretty hip. ---
**Author:** ![BigT](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bigt/32/12044_2.png) [@BigT](https://boards.straightdope.com/u/BigT)\ **Post date:** [May 6, 2017, 10:17pm UTC](https://boards.straightdope.com/t/any-fixes-for-chromes-new-security-check/785713/25 "2017-05-06T22:17:21Z")
> [@Musicat](#): > > Rebooting Chrome without the no-cert option…any site that uses https shows “secure” to the left of the URL. Http shows nothing. Godaddy’s sites replace the secure with GoDaddy INC. [US] and the https: is shown in color whenever it appears. > > I did nothing that I can think of to my computer that might have affected this. That’s the way it’s supposed to be, AFAIK. Showing the name is supposed to be a way to let you know you are definitely on the real GoDaddy site, and not some similar URL. I believe it requires some other additional authentication. I would guess that it was a bug, and that Chrome silently patched it, as it often does. Or there was a problem with these site’s certificates that they’ve since fixed. Still would be nice to know why you ran into this problem, though. [Previous page](https://boards.straightdope.com/t/any-fixes-for-chromes-new-security-check/785713.md?page=1)