-
Notifications
You must be signed in to change notification settings - Fork 184
Let's Encrypt Reference Sheet
Eugene Bekker edited this page Nov 15, 2016
·
10 revisions
This page documents useful reference information regarding the specifics of the Let's Encrypt CA (LE) service.
Full details can be found here.
Metric | PROD | STAGE |
---|---|---|
Certs/Registered Domain/Week | 20 | 30,000 |
Duplicate Certificate/Week | 5 | 30,000 |
Max Registrations/IP Address/Hour | 500 | 500 |
Max Pending Authorizations | 300 | 300 |
- LE uses a sliding window for rate limiting so if you hit a rate during the week, the limit will be relaxed one week after the metric started accumulating -- not from time you hit the limit.
- Registered domains are the part of the domain you pay for to a registrar as calculated by the Public Suffix List.
- Certs are considered Duplicate Certs if they have the exact same names ignoring case and ordering.
Feature | PROD | STAGE |
---|---|---|
SAN Names/Cert | 100 | 100 |
The Boulder CA server that power the LE project diverges from the ACME Spec in a few areas.
The complete list can be found here:
Some notable differences from this list:
- Boulder does not allow
tel
URIs in the registrations contact list. - Boulder does not implement the
status
,applications
orcertificates
fields in the registration object. - Boulder does not implement the
new-application
resource. Instead it implementsnew-cert
. - Boulder does not provide a
Retry-After
header when a user hist a rate-limit. - Boulder uses a modifies style of key roll-over.
- Boulder does not implement the
reason
field for therevoke-cert
endpoint and defaults tounspecified
for all requests. - Boulder implements
tls-sni-01
and nottls-sni-02
validation method. - Boulder does not implement
oob-01
validation method.
Docs
- Overview
- FAQ
- Let's Encrypt Reference Sheet
- Quick Start
- Requirements
- Basic Concepts
- Vaults, Vault Providers and Vault Profiles
- Challenge Types, Challenge Handlers and Providers
- Troubleshooting
- Contributions
Legacy Docs - out of date
Reference
- Good to Know
- Proposed Extension Mechanism
- PowerShell Module Design
- Style Guides and Conventions
- Documentation Resources
A bit dated