Https from Symantec? Tens of thousands of websites will find themselves marked as insecure if they don't discontinue the HTTPS certificate they use in the next two months.
Thanks to a decision made in September, Google will stop considering SSL/TLS issued by Symantec as secure. 
The decision will take effect from mid-April, and Chrome browser users who visit such pages that use 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 be intercepted.
The change will come with Chrome version 66, 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 uses Chrome, and not everyone immediately upgrades to the latest version. But no matter what we do, websites using HTTPS from Symantec will face problems.
So if you are a company or an organization that uses Symantec security protocols, you should do something soon to avoid being exposed.
Symantec, meanwhile, claims that only 127 certificates were issued incorrectly, not the 30,000 initially announced. However, a few months after the “incorrect” certificates were revealed and after Google’s insistence, Symantec sold its certificate division to DigiCert.
