Attributed metadata history
Up to 100 retained publisher events per page for 824f2b55bb545a2d5da213a8dd6e6cf056190320ba7a01526ba8f45a9b05cb21. Withdrawals and unavailable references remain attributed to their publishers.
intelligence_src_823f7b237762257237
observed · 2026-10-12 12:09:04 UTC
It has long been a dream of ours for there to be a standardized protocol for certificate issuance and management. That dream has become a reality now that the IETF has standardized the ACME protocol as RFC 8555. I’d like to thank everyone involved in that effort, including Let’s Encrypt staff and other IETF contributors. Having a standardized protocol for certificate issuance and management is important for two reasons. First, it improves the quality of the software ecosystem because developers can focus on developing great software for a single protocol, instead of having many pieces of less well maintained software for bespoke APIs. Second, a standardized protocol makes switching from one CA to another easier by minimizing technical dependency lock-in. We consider the standardized version of the ACME protocol to be the second major version of ACME, so we refer to it as ACMEv2. The first version, which we call ACMEv1, is the version of ACME that Let’s Encrypt has used since our launch in 2015. Now that ACMEv2 is standardized, we are announcing an end-of-life plan for our ACMEv1 support. Let’s Encrypt is currently providing certificates for more than 150 million websites. W
Fingerprint: e00b29b7ab03f0cfbe26e24b432eed1611e2dc73892756faaa4da0a24d3edcfb
intelligence_src_823f7b237762257237
observed · 2026-10-12 12:09:04 UTC
available
Fingerprint: 3ee9ede72037d42a31a54231e2db3aca2f948cab8548bb5974fefbf1d8cf8232