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 wide variety of trusted digital certificates, PKI services, and certificate lifecycle management.
Google Chrome, Apple, and Mozilla have distrusted new issuance of Entrust certificates.
Public TLS/SSL certificates issued from Entrust roots will not be trusted by Google Chrome if the Signed Certificate Timestamp (SCT) is dated after November 11, 2024, by Apple if the SCT is dated after November 15, 2024, and by Mozilla if the SCT is dated after November 30, 2024.
We understand this incident is a business disruption for affected organizations.
As a global leader in globally trusted public and private trust solutions, we are committed to helping you maintain critical operations and ensure business continuity during the transition from Entrust—and beyond.
Our experts can help ensure you make the transition without disruption or costly outages. Reach out today.
We helped thousands navigate the Symantec distrust in 2018. Join us for an experience-backed roadmap to avoiding disruption from the Entrust distrust.
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
Why did Google decide to distrust Entrust roots?Ìý
In , Google said:
Over the past several years, highlighted a pattern of concerning behaviors by Entrust that fall short of the above expectations, and has eroded confidence in their competence, reliability, and integrity as a publicly-trusted CA Owner.
And...
Certification Authorities (CAs) serve a privileged and trusted role on the Internet that underpin encrypted connections between browsers and websites. With this tremendous responsibility comes an expectation of adhering to reasonable and consensus-driven security and compliance expectations, including those defined by the CA/Browser TLS Baseline Requirements.
Over the past six years, we have observed a pattern of compliance failures, unmet improvement commitments, and the absence of tangible, measurable progress in response to publicly disclosed incident reports. When these factors are considered in aggregate and considered against the inherent risk each publicly-trusted CA poses to the Internet ecosystem, it is our opinion that Chrome’s continued trust in Entrust is no longer justified.