Attributed metadata history
Up to 100 retained publisher events per page for 8269478a9e65bb94d276145a60ae058b64b8b1c5ce97007b5289d6f618e8534c. Withdrawals and unavailable references remain attributed to their publishers.
intelligence_src_823f7b237762257237
observed · 2026-10-12 12:09:04 UTC
Since March 2023, Let’s Encrypt has been improving our resiliency and reliability via ACME Renewal Information (ARI). ARI makes it possible for our Subscribers to handle certificate revocation and renewal easily and automatically. A primary benefit of ARI is that it sets Subscribers up for success in terms of ideal renewal times in the event that Let’s Encrypt offers certificates with even shorter lifetimes than 90 days. We recently published a guide for engineers on how to integrate ARI into existing ACME Clients. In this blog post, we’ll explore Let’s Encrypt Subscriber Tailscale’s experience adopting ARI. In total, it took just two Tailscale engineers less than two days to implement ARI. Prior to ARI, the Tailscale team had made other iterations of cert renewal logic, including hardcoding renewal 14 days before expiry and hardcoding 1/3rd of remaining time until expiry. An issue with these approaches was that assumptions were made about the validity period of certificates issued by Let’s Encrypt, which will change in the future. In contrast, ARI allows Tailscale to offload the renewal decision to Let’s Encrypt without making any assumpti
Fingerprint: 8a773f7a84c78dff2df963e74ce7f0d5fb12abfc3310ae45cbeb69f83404ed0b
intelligence_src_823f7b237762257237
observed · 2026-10-12 12:09:04 UTC
available
Fingerprint: 3ee9ede72037d42a31a54231e2db3aca2f948cab8548bb5974fefbf1d8cf8232