Https from Symantec? Tens of thousands of websites will be identified as unsafe if they do not interrupt the HTTPS certificate they use in the next two months.
Thanks to a decision made in September, Google will no longer consider SSL / TLS issued by Symantec safe. 
The decision will apply from mid-April, and the users of the program tourChrome users who visit such pages using security certificates issued before June 1, 2016 or after December 1, 2017, by Symantec, will be warned by the browser that their connection is not private and that their information can to be intercepted.
Change will come with her version 66 of Chrome, which will be released on April 17. But the problem will become even bigger on October 23 when build 70 is released which will recognize all Symantec certificates as untrusted.
Of course, not everyone is using Chrome and they are not all upgraded directly to the latest version. But as we do, websites using HTTPS from Symantec will have problems.
So if you are a company, or an organization that uses Symantec security protocols, you will soon have to do something, so you do not get exposed.
Symantec, meanwhile, claims that only 127 certificates were issued incorrectly, not the 30.000 originally announced. But a few months after the revelation of the "wrong" certificates and after the insistence of Google, Symantec sold the certificate department to DigiCert.
