Attributed metadata history
Up to 100 retained publisher events per page for 7f93c5a6fbb194f66ef4c2f873b19b69db655a936308ef0815d3ae55d12214ca. 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
Let’s Encrypt will be reducing the validity period of the certificates we issue. We currently issue certificates valid for 90 days, which will be cut in half to 45 days by 2028. This change is being made along with the rest of the industry, as required by the CA/Browser Forum Baseline Requirements, which set the technical requirements that we must follow. All publicly-trusted Certificate Authorities like Let’s Encrypt will be making similar changes. Reducing how long certificates are valid for helps improve the security of the internet, by limiting the scope of compromise, and making certificate revocation technologies more efficient. We are also reducing the authorization reuse period, which is the length of time after validating domain control that we allow certificates to be issued for that domain. It is currently 30 days, which will be reduced to 7 hours by 2028. Timeline of Changes To minimize disruption, Let’s Encrypt will roll this change out in multiple stages. We will use ACME Profiles to allow you control over when these changes take effect. They are configured in your ACME client. For more information, see our blog post announcing them. Changes will be deployed to
Fingerprint: 67d52d90c705af5667cca2cf0dd355501be8fa1b32598790b8e89ba9b7894bb3