はてなブックマーク

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.

Last updated: Feb 5, 2024 | See all Documentation Update Feb 05, 2024 It’s been two years, and the Android compatibility cross-sign mentioned below is close to expiring. See our recent blog post for a detailed explanation of the changes coming over the course of 2024. Update September 30, 2021 As planned, the DST Root CA X3 cross-sign has expired, and we’re now using our own ISRG Root X1 for trust

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

Update, May 13, 2021 Please visit [this post] (https://community.letsencrypt.org/t/production-chain-changes/150739) on our community forum for the latest information about chain changes as some information about the changes and dates in this blog post are outdated. We’re happy to announce that we have developed a way for older Android devices to retain their ability to visit sites that use Let’s E

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

On Thursday, September 3rd, 2020, Let’s Encrypt issued six new certificates: one root, four intermediates, and one cross-sign. These new certificates are part of our larger plan to improve privacy on the web, by making ECDSA end-entity certificates widely available, and by making certificates smaller. Given that we issue 1.5 million certificates every day, what makes these ones special? Why did we

This document provides a gentle introduction to the data structures and formats that define the certificates used in HTTPS. It should be accessible to anyone with a little bit of computer science experience and a bit of familiarity with certificates. An HTTPS certificate is a type of file, like any other file. Its contents follow a format defined by RFC 5280. The definitions are expressed in ASN.1

Download affected certificate serials for 2020.02.29 CAA Rechecking Incident Last updated: Mar 3, 2020 This page hosts the list of affected serial numbers and a hostname checking utility for the incident reported at https://community.letsencrypt.org/t/2020-02-29-caa-rechecking-bug/114591. We have sent notification emails to affected subscribers who have registered an email address. If you need to

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

At Let’s Encrypt we’re always looking for ways to improve the security and integrity of the Web PKI. We’re proud to launch multi-perspective domain validation today because we believe it’s an important step forward for the domain validation process. To our knowledge we are the first CA to deploy multi-perspective validation at scale. Domain validation is a process that all CAs use to ensure that a

最終更新日:2021/10/02 注意: このページが翻訳された後、英語バージョンのページがアップデートされています。 (2024/06/11) 英語で表示する ルート証明書 私たちのルートは安全にオフラインで保管されています。 私たちは次のセクションにある中間CAからサブスクライバに対してエンドエンティティ証明書を発行します。 新しいルートX2を様々なルートプログラムに送信する際に互換性を得るため、私たちはルートX1からクロス署名しました。 有効 ISRG Root X1 (RSA 4096, O = Internet Security Research Group, CN = ISRG Root X1) 自己署名: der, pem, txt DST Root CA X3のクロス署名: der, pem, txt 有効、利用制限あり ISRG Root X2 (ECDSA P-384,

最終更新日:2020/12/08 | すべてのドキュメントを読む 注意: このページが翻訳された後、英語バージョンのページがアップデートされています。 (2023/02/13) 英語で表示する Let’s Encrypt から証明書を取得するときには、ACME 標準で定義されている「チャレンジ」を使用して、証明書が証明しようとしているドメイン名があなたの制御下にあることを検証します。 ほとんどの場合、この検証は ACME クライアントにより自動的に処理されますが、より複雑な設定を行った場合、詳細な仕組みについて知っておくと役に立つはずです。 よく分からない場合には、クライアントのデフォルトの設定か、HTTP-01 を使用してください。 HTTP-01 チャレンジ 現在、最も多く使われているチャレンジです。 Let’s Encrypt は ACME クライアントにトークンを発行し、ACME

Let’s Encrypt はフリーで自動化されたオープンな認証局です。 2021 年の年次レポートを読む ブログ記事より 2024/07/23 Intent to End OCSP Service Moving to a more privacy-respecting and efficient method of checking certificate revocation. もっと読む 2024/06/24 More Memory Safety for Let’s Encrypt: Deploying ntpd-rs NTP is critical to how TLS works, and now it’s memory safe at Let’s Encrypt. もっと読む 2024/05/30 Let’s Encrypt Continues Partnership with

Let's Encryptは、非営利団体の Internet Security Research Group (ISRG) が提供する自動化されたフリーでオープンな認証局です。 548 Market St, PMB 77519, San Francisco, CA 94104-5401, USA すべての手紙またはお問い合わせを以下に送ってください： PO Box 18666, Minneapolis, MN 55418-0666, USA

注意: このページが翻訳された後、英語バージョンのページがアップデートされています。 (2022/09/07) 英語で表示する 最終更新日:2024/07/02 | すべてのドキュメントを読む Let’s Encrypt は、与えられたドメインを制御する権限があなたにあることを検証し、証明書を発行するために、ACME プロトコルを使用しています。 Let’s Encrypt の証明書を取得するためには、使用する ACME クライアントを1つ選ぶ必要があります。 以下に示す ACME クライアントはサードパーティにより提供されているものです。 サードパーティ製クライアントは Let’s Encrypt の制御下にはなく、レビューを行っているわけではないので、安全性や信頼性に対する保証をすることはできません。 ブラウザ内で動作する ACME クライアントがいくつか存在しますが、以下のリストには

Update, September 17, 2020 Due to concerns about insufficient ISRG root propagation on Android devices we have decided to move the date on which we will start serving a chain to our own root to January 11, 2021. We had originally delayed this change until September 29, 2020. Update, June 11, 2020 In an effort to provide more time for our community to prepare for this transition, we have moved back

It has long been a dream of ours for there to be a standardized protocol for certificate issuance and management. That dream has become a reality now that the IETF has standardized the ACME protocol as RFC 8555. I’d like to thank everyone involved in that effort, including Let’s Encrypt staff and other IETF contributors. Having a standardized protocol for certificate issuance and management is imp

Let’s Encrypt had a great year in 2018. We’re now serving more than 150 million websites while maintaining a stellar security and compliance track record. Most importantly though, the Web went from 67% encrypted page loads to 77% in 2018, according to statistics from Mozilla. This is an incredible rate of change! We’d like to thank all of the people and organizations who worked hard to create a mo

As of the end of July 2018, the Let’s Encrypt root, ISRG Root X1, is directly trusted by Microsoft products. Our root is now trusted by all major root programs, including Microsoft, Google, Apple, Mozilla, Oracle, and Blackberry. Today’s announcement that we’re trusted by all major root programs represents a major milestone for us, but it’s not the conclusion of our journey towards being directly

Last updated: Dec 21, 2017 | See all Documentation Sometimes people want to get a certificate for the hostname “localhost”, either for use in local development, or for distribution with a native application that needs to communicate with a web application. Let’s Encrypt can’t provide certificates for “localhost” because nobody uniquely owns it, and it’s not rooted in a top level domain like “.com”

Let’s Encrypt had a great year in 2017. We more than doubled the number of active (unexpired) certificates we service to 46 million, we just about tripled the number of unique domains we service to 61 million, and we did it all while maintaining a stellar security and compliance track record. Most importantly though, the Web went from 46% encrypted page loads to 67% according to statistics from Mo

We’re excited that support for getting and managing TLS certificates via the ACME protocol is coming to the Apache HTTP Server Project (httpd). ACME is the protocol used by Let’s Encrypt, and hopefully other Certificate Authorities in the future. We anticipate this feature will significantly aid the adoption of HTTPS for new and existing websites. We created Let’s Encrypt in order to make getting

Update, March 13, 2018 Wildcard certificate support is live. Let’s Encrypt will begin issuing wildcard certificates in January of 2018. Wildcard certificates are a commonly requested feature and we understand that there are some use cases where they make HTTPS deployment easier. Our hope is that offering wildcards will help to accelerate the Web’s progress towards 100% HTTPS. Let’s Encrypt is curr

Update, April 27, 2018 ACME v2 and wildcard support are fully available since March 13, 2018. Update, January 4, 2018 We introduced a public test API endpoint for the ACME v2 protocol and wildcard support on January 4, 2018. ACME v2 and wildcard support will be fully available on February 27, 2018. Let’s Encrypt will add support for the IETF-standardized ACME v2 protocol in January of 2018. We wil