As of February 1, 2018, DigiCert will submit all newly issued SSL certificates to Certificate Transparency (CT) logs as a default.<\/span><\/p>\n Clint Wilson, DigiCert\u2019s Technical Product Manager, detailed the decision in a blog post<\/a>:<\/p>\n In the interest of improving our customer\u2019s security and encouraging adoption, we are making this change ahead of Google\u2019s industry-wide requirement that goes into effect in\u00a0April 2018. CT logging has only been required for EV certificates since 2015.<\/p>\n This change will happen automatically on February 1st<\/sup>. Your publicly trusted DigiCert SSL Certificates issued on or after that date will include pieces of data called \u201cSCTs\u201d\u2014Signed Certificate Timestamps. These are embedded directly into the certificate and tell client software, like web browsers, that the certificate has been logged. When Google Chrome begins enforcing CT compliance in April, your certificates will already be compatible. You don\u2019t need to do anything unless you don\u2019t want your certificates logged.<\/p><\/blockquote>\n This move will only affect DigiCert certificates. The Symantec brand (Symantec, RapidSSL, GeoTrust & Thawte), which DigiCert acquired last Fall, is already required to log all new certificates as part of an agreement with Google.<\/p>\n If you\u2019re looking for a detailed explanation of Certificate Transparency, Vince (who ironically now works for DigiCert) wrote an excellent article about it last year<\/a>.<\/p>\nWhat is Certificate Transparency?<\/h2>\n