Published file metadata, source observations, indicators, and research history in one bounded catalog.
128Reachable catalog records
4 / 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
If you work at a hosting provider or CDN, ACME’s DNS-01 validation method can make it a lot easier to onboard new customers who have an existing HTTPS website at another provider. Before your new customer points their domain name at your servers, you need to have a certificate already installed for them. Otherwise visitors to the customer’s site will see an outage for a few minutes while you issue
First reported Oct 09, 2019 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
Let’s Encrypt protects a vast portion of the Web by providing TLS certificates to over 550 million websites—a figure that has grown by 42% in the last year alone. We currently issue over 340,000 certificates per hour. To manage this immense traffic and maintain responsiveness under high demand, our infrastructure relies on rate limiting. In 2015, we introduced our first rate limiting system, built
First reported Jan 30, 2025 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
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. This year we will continue to pursue our commitment to improving the security of the Web PKI by introducing the option to get certificates with six-day lifetimes (“short-lived certificates”). We will also add support for IP addresses i
First reported Jan 16, 2025 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
We issued our billionth certificate on February 27, 2020. We’re going to use this big round number as an opportunity to reflect on what has changed for us, and for the Internet, leading up to this event. In particular, we want to talk about what has happened since the last time we talked about a big round number of certificates - one hundred million. One thing that’s different now is that the Web
First reported Feb 27, 2020 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
It’s hard to believe 10 years have passed since Eric Rescorla, Alex Halderman, Peter Eckersley and I founded ISRG as a nonprofit home for public benefit digital infrastructure. We had an ambitious vision, but we couldn’t have known then the extent to which that vision would become shared and leveraged by so much of the Internet. Since its founding in 2013, ISRG’s Let’s Encrypt certificate authorit
First reported May 24, 2023 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
Earlier this year we announced our intent to provide certificate revocation information exclusively via Certificate Revocation Lists (CRLs), ending support for providing certificate revocation information via the Online Certificate Status Protocol (OCSP). Today we are providing a timeline for ending OCSP services: January 30, 2025 OCSP Must-Staple requests will fail, unless the requesting account
First reported Dec 05, 2024 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
Engineers design systems and processes to ensure high quality outcomes and solutions - what if the same lens could be used to build a workplace where these very same engineers can thrive? Many organizations toil on how to build an environment where employees are engaged, challenged, and happy with their workplace, and while ISRG is not immune to those challenges, we do implement a few distinctive
First reported Jan 12, 2023 12:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
When Let’s Encrypt first launched, we needed to ensure that our certificates were widely trusted. To that end, we arranged to have our intermediate certificates cross-signed by IdenTrust’s DST Root CA X3. This meant that all certificates issued by those intermediates would be trusted, even while our own ISRG Root X1 wasn’t yet. During subsequent years, our Root X1 became widely trusted on its own.
First reported Jul 10, 2023 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
Update, July 10, 2023 See our new blog post for details on the September 2024 expiration of the newer ISRG Root X1 cross-sign from IdenTrust. Update, December 21, 2020 Thanks to community feedback and our wonderful partners at IdenTrust, we will be able to continue to offer service without interruption to people using older Android devices. We flagged the content of this blog post that is no longe
First reported Nov 06, 2020 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
Update: Feb. 5 2020 The Let’s Encrypt CT logs are now included in approved log lists and are usable by all publicly-trusted certificate authorities. Today we are announcing a new Certificate Transparency log called Oak. The Oak log will be operated by Let’s Encrypt and all publicly trusted certificate authorities will be welcome to submit certificates. Sectigo generously provided funding to cover
First reported May 15, 2019 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
The Internet Society has supported our work toward a 100% encrypted Web since before we’d even issued our first certificate. Their commitment to helping us execute our vision has been a substantial help over the years. Today, I’m excited to invite Christine Runnegar, Senior Director at The Internet Society and member of ISRG’s Board of Directors, to share her thoughts. -Josh Aas, Executive Directo
First reported Oct 21, 2021 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
Today we are announcing our intent to end Online Certificate Status Protocol (OCSP) support in favor of Certificate Revocation Lists (CRLs) as soon as possible. OCSP and CRLs are both mechanisms by which CAs can communicate certificate revocation information, but CRLs have significant advantages over OCSP. Let’s Encrypt has been providing an OCSP responder since our launch nearly ten years ago. We
First reported Jul 23, 2024 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
Let’s Encrypt is proud to introduce Sunlight, a new implementation of a Certificate Transparency log that we built from the ground up with modern Web PKI opportunities and constraints in mind. In partnership with Filippo Valsorda, who led the design and implementation, we incorporated feedback from the broader transparency logging community, including the Chrome and TrustFabric teams at Google, th
First reported Mar 14, 2024 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
On a normal day Let’s Encrypt issues nearly two million certificates. When we think about what essential infrastructure for the Internet needs to be prepared for though, we’re not thinking about normal days. We want to be prepared to respond as best we can to the most difficult situations that might arise. In some of the worst scenarios, we might want to re-issue all of our certificates in a 24 ho
First reported Feb 10, 2021 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
Let’s Encrypt helps to protect a huge portion of the Web by providing TLS certificates to more than 235 million websites. A database is at the heart of how Let’s Encrypt manages certificate issuance. If this database isn’t performing well enough, it can cause API errors and timeouts for our subscribers. Database performance is the single most critical factor in our ability to scale while meeting s
First reported Jan 21, 2021 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
What does it take to manage TLS certificates at a leading e-commerce company? Before Let’s Encrypt, it took the security team at Shopify weeks to manually obtain certificates for their websites. Doing this once is unpleasant enough, but if an incident were to happen that necessitated renewing all of their certificates, Shopify estimated it would take them 100+ days without automated issuance and m
First reported Sep 14, 2021 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
As previously announced, over the next two years we will be switching the default certificate lifetime from 90 days to 64 days, and then 45 days. This will ultimately double the number of certificate renewal requests each day: today we expect renewal around day 60 (of a 90-day certificate), while in the future we expect renewal around day 30 (of a 45-day certificate). If you use an ACME client tha
First reported Feb 24, 2026 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
NGINX and Let's Encrypt share a common vision of an open and secure web. Now, with built-in support for ACME, the world's most popular web server, reverse proxy and ingress controller for Kubernetes can simplify certificate management for everyone. From the home lab to scaled-out, mission-critical enterprise deployments. — Liam Crilly, Sr Dir, Product Management, F5 NGINX Our ideal has always been
First reported Sep 11, 2025 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
Let’s Encrypt is committed to a post-quantum-safe Web PKI. The path we’re planning to take is Merkle Tree Certificates (“MTCs”), a new approach that adds post-quantum authentication to the web without sacrificing the speed and reliability that have made TLS universal. This post is about these plans and why we believe MTCs are worth pursuing as a key to a post-quantum future. An increasingly urgent
First reported Jun 03, 2026 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
On February 10, 2027, all Let’s Encrypt subscribers will move to certificates with 64 day lifetimes by default unless they select an even shorter lifetime (45 or 6 days, as previously announced). This means that any certificate we issue or renew on and after that date will have a 64 day validity period, and we expect the last 90-day certificate to expire on May 11, 2027. We will not revoke valid c
First reported Oct 07, 2026 00:00 UTCCatalog metadata updated Oct 08, 2026 03:47 UTCOpen evidence record
Earlier this year we announced our intention to introduce short-lived certificates with lifetimes of six days as an option for our subscribers. Yesterday we issued our first short-lived certificate. You can see the certificate at the bottom of our post, or here thanks to Certificate Transparency logs. We issued it to ourselves and then immediately revoked it so we can observe the certificate’s who
First reported Feb 20, 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.