Published file metadata, source observations, indicators, and research history in one bounded catalog.
128Reachable catalog records
5 / 6Current catalog page
24Maximum records per page
0Samples downloaded by this page
Feed collection status
Sources represented on this page. Publication and observation dates describe the content; successful batch dates describe local collection. A recent batch does not certify complete coverage or current provider availability.
src_823f7b237762257237Collection status unverifiedLast successful batch: Unverified
Stale means older than twice the recorded collection interval, with a minimum of one hour; without an interval, the threshold is 24 hours. Cached content remains available while a feed is stale, paused, or unverified.
128 MATCHING RECORDSMETADATA ONLY / SOURCE ATTRIBUTION PRESERVED
Update: January 15, 2026 Six-day and IP address certificates are now generally available. See 6-day and IP Address Certificates are Generally Available for details. Since Let’s Encrypt started issuing certificates in 2015, people have repeatedly requested the ability to get certificates for IP addresses, an option that only a few certificate authorities have offered. Until now, they’ve had to look
First reported Jul 01, 2025 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
Seth Schoen was an early contributor to Let's Encrypt through his work at the Electronic Frontier Foundation. He's also one of the longest standing participants in the Let's Encrypt community support forum, so we asked him to offer his thoughts on the role and impact of the forum as a resource for our users. Thank you for your many years of expertise and participation, Seth! — Josh Aas, Head of Le
First reported Oct 07, 2025 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
Update, August 18, 2025 We have updated the read-only and shutdown dates to ensure that our new Static CT API logs are fully trusted by browsers before switching Oak to read-only in order to avoid any disruption. Let’s Encrypt operates two types of Certificate Transparency (“CT”) logs—some implement the original RFC 6962 API, and some that implement the newer Static CT API. Today we are announcing
First reported Aug 14, 2025 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
At Let’s Encrypt we know that building a secure Internet isn’t just a technical challenge—it’s a long-term commitment. Over the past decade we’ve made enormous strides: from issuing billions of TLS certificates to continually innovating to keep the web safer and more accessible. But none of this would be possible without recurring donations from individuals and organizations around the world. Recu
First reported May 21, 2025 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
When the scripts that generate the data for letsencrypt.org/stats broke yet again, we decided to retire them rather than repair them. Let’s Encrypt issues six to ten million certificates each day, producing a large volume of logs that keeps growing. It became increasingly time-consuming and difficult to answer questions about our own issuance like “how many certificates use the ‘shortlived’ profil
First reported Sep 17, 2026 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
Ten years ago, we printed one of the nerdiest t-shirts we’ve ever made. On the front was the entire PEM encoding of ISRG Root X1 in base64. Back then, it represented a future we were working toward. Today, that same design tells the story of just how far Let’s Encrypt has come. Let’s Encrypt was already issuing publicly trusted certificates in 2016, but ISRG Root X1 itself was still slowly and qui
First reported Aug 11, 2026 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
Today we turned off our Online Certificate Status Protocol (OCSP) service, as announced in December of last year. We stopped including OCSP URLs in our certificates more than 90 days ago, so all Let’s Encrypt certificates that contained OCSP URLs have now expired. Going forward, we will publish revocation information exclusively via Certificate Revocation Lists (CRLs). We ended support for OCSP pr
First reported Aug 06, 2025 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
Update: March 11, 2026 If you use Certbot, see Six-Day and IP Address Certificates Available in Certbot for details on requesting these certificates. Short-lived and IP address certificates are now generally available from Let’s Encrypt. These certificates are valid for 160 hours, just over six days. In order to get a short-lived certificate subscribers simply need to select the ‘shortlived’ certi
First reported Jan 15, 2026 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
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
First reported May 14, 2025 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
How Pebble Supports ACME Client Developers Together with the IETF community, we created the ACME standard to support completely automated certificate issuance. This open standard is now supported by dozens of clients. On the server side, did you know that we have not one but two open-source ACME server implementations? The big implementation, which we use ourselves in production, is called Boulder
First reported Apr 30, 2025 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
When you request a certificate from Let’s Encrypt, our servers validate that you control the hostnames in that certificate using ACME challenges. For subscribers who need wildcard certificates or who prefer not to expose infrastructure to the public Internet, the DNS-01 challenge type has long been the only choice. DNS-01 works well. It is widely supported and battle-tested, but it comes with oper
First reported Feb 18, 2026 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
The Certificate Transparency ecosystem has been improving transparency for the web PKI since 2013. It helps make clear exactly what certificates each certificate authority has issued and makes sure errors or compromises of certificate authorities are detectable. Let’s Encrypt participates in CT both as a certificate issuer and as a log operator. For the past year, we’ve also been running an experi
First reported Jun 11, 2025 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
On September 14, 2015, our first publicly-trusted certificate went live. We were proud that we had issued a certificate that a significant majority of clients could accept, and had done it using automated software. Of course, in retrospect this was just the first of billions of certificates. Today, Let’s Encrypt is the largest certificate authority in the world in terms of certificates issued, the
First reported Dec 09, 2025 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
Have you ever needed to make sure your website has a broken certificate? While many tools exist to help run an HTTPS server with valid certificates, there aren’t tools to make sure your certificate is revoked or expired. This is not a problem most people have. Tools to help manage certificates are always focused on avoiding those problems, not creating them. Let’s Encrypt is a Certificate Authorit
First reported Apr 10, 2026 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
Let’s Encrypt has been proud to work with the IETF to maintain ACME as an open standard since we first developed the technology a decade ago. We’re happy to announce that IETF has published our latest addition to the ACME protocol, ACME Renewal Information (ARI), as RFC 9773. ARI helps keep the renewal process reliable during unexpected events affecting certificate validity. Since the ACME protoco
First reported Sep 16, 2025 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
This was also posted on EFF’s blog. As we announced earlier this year, Let’s Encrypt now issues IP address and six-day certificates to the general public. The Certbot team at the Electronic Frontier Foundation has been working on two improvements to support these features: the --preferred-profile flag released last year in Certbot 4.0, and the --ip-address flag, new in Certbot 5.3. With these impr
First reported Mar 11, 2026 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
Since its inception, Let’s Encrypt has been sending expiration notification emails to subscribers that have provided an email address to us via the ACME API. This service ended on June 4, 2025. The decision to end the service is the result of the following factors: Over the past 10 years more and more of our subscribers have been able to put reliable automation into place for certificate renewal.
First reported Jun 26, 2025 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
This letter was originally published in our 2025 Annual Report. This year was the 10th anniversary of Let’s Encrypt. We’ve come a long way! Today we’re serving more than 700 million websites, issuing ten million certificates on some days. Most importantly, when we started 39% of page loads on the Internet were encrypted. Today, in many parts of the world, over 95% of all page loads are encrypted.
First reported Dec 29, 2025 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
A filename, label, or report mention alone does not establish maliciousness. Observation dates describe cited sources; collection dates describe this local metadata catalog. No malware samples are stored, fetched, or executed by these pages.