Attributed metadata history
Up to 100 retained publisher events per page for 07e86621418bf583c131193d12f75c3fc2b525a1ca3ac9e810cd1973eec4592b. 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: Added clarification that only the Let’s Encrypt client software is changing its name and host. The Let’s Encrypt certificate authority and associated services are not changing names or relocating. Over the next few months the Let’s Encrypt client software will transition to a new name, soon to be announced, and a new home at the Electronic Frontier Foundation (EFF). This change does not affect the Let’s Encrypt certificate authority (CA) or associated services, which will retain the Let’s Encrypt name and continue to be hosted by the Internet Security Research Group. The goal of Let’s Encrypt is to make turning on HTTPS as easy as possible. To accomplish that, it’s not enough to fully automate certificate issuance on the certificate authority (CA) side - we have to fully automate on the client side as well. The Let’s Encrypt client is now being used by hundreds of thousands of websites and we expect it to continue to be a popular choice for sites that are run from a single server or VPS. That said, the web server ecosystem is complex, and it would be impossible for any particular client to serve everyone well. As a result, the Let’s Encrypt
Fingerprint: b859e028eadb298d701335c703dca9377f143a9a02a627863952cba010bf721c