If you have many certificates to replace or other complex technical or business requirements, please contact our team to discuss the best migration path for your organization. ¶ºÒõ¹Ý offers a broad variety of trusted digital certificates, PKI services and our modern certificate lifecycle management solution, ¶ºÒõ¹Ý® Trust Lifecycle Manager.
Public TLS certificates issued from Entrust roots with a Signed Certificate Timestamp (SCT) dated after October 31, 2024 will not be trusted by Google Chrome.
We understand this incident poses significant risk of business disruption to a large number of organizations.
As the world leader in globally trusted PKI and TLS/SSL solutions, we are committed to making our services and solutions available to help you maintain critical operations and ensure uninterrupted business continuity during the transition from Entrust—and beyond.
We take our responsibility as aÌýCertificate Authority (CA)Ìýin the root store of all major browsers very seriously. Our entire company’s sole focus is—and has been for more than two decades—to do everything in our power to deliver digital trust to our customers that enables them to safely communicate, engage, and transact across the breadth of the connected world. 
Our experts can help ensure you make the transition without disruption or costly outages. Reach out today.
The Entrust distrust: Key takeaways for CAs and organizations
Why Compliance is the Foundation of Digital Trust
¶ºÒõ¹Ý Releases Innovative Automated Testing Tool for Digital Certificates
What is a CA's role in delivering digital trust?
What is digital trust?
Certificate management for TLS best practices
We helped thousands navigate the Symantec distrust in 2018. Join us for an experience-backed roadmap to avoiding disruption from the Entrust distrust.
When will my Entrust certificates be distrusted by Google Chrome?
When should I start replacing my current Entrust certificates?
How can I determine if we are using Entrust certificates in our environment?
How long will it take to get new certificates?
How can we trust that ¶ºÒõ¹Ý will not have a similar distrust problem?
When will my Entrust certificates be distrusted by Google Chrome?
Public TLS certificates issued from Entrust roots with a Signed Certificate Timestamp (SCT) dated after October 31, 2024, will not be trusted by Google Chrome after October 31, 2024.
Any TLS certificate with an SCT dated before October 31, 2024, will be valid for its term.
When should I start replacing my current Entrust certificates?
We recommend customers start planning their replacement strategy as soon as possible to get an accurate inventory of their certificates with their corresponding expiry date, assess the risk profile of the associated service, and plan the replacement process. Here are the top 4 things you should do today. (link to section on the site that says this)
How can I determine if we are using Entrust certificates in our environment?
A variety of tools can connect to your infrastructure to scan and discover certificates in your environment. ¶ºÒõ¹Ý Trust Lifecycle Manager (TLM) and ¶ºÒõ¹Ý CertCentral can evaluate your environment to identify any Entrust certificates in need of replacement. Contact us if you need help with this.
How long will it take to get new certificates?
Getting new certificates can be done very quickly; however, you will need to be responsive and quick to work with us. We will need to validate your domain, which takes seconds, and then validate your organization, which can be done in minutes. The entire process of getting your new certificates can be completed very quickly.
After this initial organization validation is done, future certificates will not need to go through this process until their validation expires—according to industry guidelines—which means subsequent certificate requests will be even quicker.
How can we trust that ¶ºÒõ¹Ý will not have a similar distrust problem?
There are three things that distinguish ¶ºÒõ¹Ý and its certificate authority business. First, we have well defined processes that we follow diligently and use tools like PKILint that we’ve developed to help mitigate issues. Second, we work closely with the CA/Browser Forum to respond to issues quickly and transparently; when issues arise, we work quickly to solve them. Finally, we are an active participant with the standards bodies, ensuring that we not only comply with standards but help evolve them for the benefit of industry.