Relevant Items
Refine Search expand_more
Blog add
5 Results for 'certificate transparency'

Certificate Transparency Deadline Moved to April 2018

Google just announced they will not be enforcing certificate transparency (CT) logging for all new TLS certificates until April 2018. 

Certificate Transparency Deployment in 2017

Google announced the requirement for Certificate Transparency for all new SSL/TLS certificates in October 2017. This requirement means that Chrome will no longer trust new SSL/TLS certificates that are not qualified for Certificate Transparency (CT). 

Microsoft Deploys Certificate Reputation

As we have stated previously, website owners have a concern that an attacker can have a certificate issued for their domain name. We now have two systems which will help monitor certificates for domains: Certificate Transparency (CT) and Certificate Reputation. 

Moving Forward with Certificate Transparency

As of January 2015, all EV SSL certificates be publicly logged to retain their EV status. All current EV SSL certificates will be white listed for the Chrome browser. Google Chrome will be the only browser supporting Certificate Transparency. With the release of Chrome 44, if the certificate is not logged, then Chrome states "No Certificate Transparency information was supplied by the server."

Monitor Your Domains with Certificate Transparency

Learn how to gain better Certificate transparency over your domains. Effective December 2014, Entrust will be deploying Certificate Transparency which means that all EV SSL certificates will include the signed certificate timestamp (SCT) and will be logged in a public and all existing non-expired EV SSL certificates will be submitted to Google to be included in a public log. Google has determined there will be no privacy for EV SSL certificates using internal domain names. All certificates will be logged with complete contents.
Page 1 of 1