API Announcements

March 13, 2019: End-of-Life for All TLS-SNI-01 Validation Support (8)

Let’s Encrypt allows subscribers to validate domain control using any one of a few different validation methods. For much of the time Let’s Encrypt has been operating, the options were “DNS-01”, “HTTP-01”, and “TLS-SNI-0…

About the API Announcements category (1)
End of Life Plan for ACMEv1 (1)
Rate limits: fixing certs per name rate limit order of operations gotcha (1)
Rate limit update: removal of renewal and new-issuance ordering constraints (5)
ACME v2 - Change to HTTP Status Code for HEAD new-nonce (3)
EDNS Buffer Size Changing to 512 Bytes (1)
ACME v2 - Scheduled deprecation of unauthenticated resource GETs (2)
ACME breaking change: Most GETs become POSTs (1)
ACME-CAA "validationmethods" support (6)
ACME v2 - Draft 13 compliant key rollover (3)
Certificates per registered domain per week limit raised (1)
TLS-ALPN validation method (3)
ACMEv2 Order "ready" Status (4)
ACME v2 strict JWS "kid" header processing (2)
Signed Certificate Timestamps embedded in certificates (3)
Overlapping Wildcard Order Identifiers (2)
ACME v2 Production Environment & Wildcards (2)
Staging endpoint for ACME v2 (2)
JWS POST Content-Type Header Enforcement (1)
IMPORTANT: What you need to know about TLS-SNI validation issues (2)
TLS-SNI challenges disabled for most new issuance (5)
Subscriber agreement update November 15, 2017 (1)
Update Registration/Key Rollover Temporarily Unavailable (2)
Legacy CAA Implementation (3)
CAA SERVFAIL changes (4)
Automatic recycling of pending authorizations (1)
Rechecking CAA at issuance time for some authorizations (2)
Validating challenges from multiple network vantage points (1)
API "/directory" endpoint "meta" field addition (4)