Attributed metadata history
Up to 100 retained publisher events per page for 87341ddff7578f490b639ea64d067d7504e4bc3179cf1b9524902ff0fb1e3171. Withdrawals and unavailable references remain attributed to their publishers.
intelligence_src_823f7b237762257237
observed · 2026-10-12 12:09:04 UTC
available
Fingerprint: 3ee9ede72037d42a31a54231e2db3aca2f948cab8548bb5974fefbf1d8cf8232
intelligence_src_823f7b237762257237
observed · 2026-10-12 12:09:04 UTC
Update March 16, 2026: Thanks to some timeline changes in the root program requirements, we have been able to push back the removal of the tlsclient profile slightly. If you are already using the tlsclient profile before May 13, 2026, now you will be able to continue to do so through July 8, 2026. Let’s Encrypt will no longer include the “TLS Client Authentication” Extended Key Usage (EKU) in our certificates beginning in 2026. Most users who use Let’s Encrypt to secure websites won’t be affected and won’t need to take any action. However, if you use Let’s Encrypt certificates as client certificates to authenticate to a server, this change may impact you. To minimize disruption, Let’s Encrypt will roll this change out in multiple stages, using ACME Profiles: Today: Let’s Encrypt already excludes the Client Authentication EKU on our tlsserver ACME profile. You can verify compatibility by issuing certificates with this profile now. October 1, 2025: Let’s Encrypt will launch a new tlsclient ACME profile which will retain the TLS Client Authentication EKU. Users who need additional time to migrate can opt-in to this profile.
Fingerprint: c65cc8e68615c1fe5f5b6ba47789dca357569e2dc61f9b39aea7310d8c94fa88