- March 15th 2018: Chrome 66 is released as beta and it will stop trusting Symantec-issued certificates issued prior to June 1, 2016.
- April 17th 2018: Chrome 66 will change status from beta to stable release.
- September 13th 2018: Chrome 70 is released as beta, which will remove trust in ALL old Symantec-rooted Infrastructure.
- Chrome 70 will change status from beta to stable release.
The Google Chrome team advise site operators to reissue their CERTS as from now 1st December but it also states that you may need to do it again when version 70 is released.
Google is also limiting the CA root from Symantec to 13 months limit, so I would recommend that you choose a new vendor.
I recommend that you read through the page linked below, its long but hopefully will inform you in more ways than I have done so.
Chrome 66 released to beta, which will remove trust in Symantec-issued
certificates with a not-before date prior to June 1, 2016. As of this
date Site Operators must be using either a Symantec-issued TLS server
certificate issued on or after June 1, 2016 or a currently valid
certificate issued from any other trusted CA as of Chrome 66.
Site Operators that obtained a certificate from Symantec’s old
infrastructure after June 1, 2016 are unaffected by Chrome 66 but will
need to obtain a new certificate by the Chrome 70 dates described
Chrome 70 released to Beta, which will remove trust in the old
Symantec-rooted Infrastructure. This will not affect any certificate
chaining to the new Managed Partner Infrastructure, which Symantec has
said will be operational by December 1, 2017.
Only TLS server certificates issued by Symantec’s old infrastructure
will be affected by this distrust regardless of issuance date.
~October 23, 2018 Chrome 70 released to Stable.