Six-day and IP certificates: what they are for
While everyone watches the 47-day deadline, the largest authority already issues certificates that expire in under a week and certificates with no domain name at all. They are generally available, they are free, and they answer two questions the 47-day debate skips.
The menu
Let's Encrypt now offers certificate profiles, chosen by the client when it places an order.1 The classic profile is the 90-day certificate everyone knows. A server profile lives 45 days, almost exactly the 2029 maximum, available today. And a short-lived profile lives 160 hours, a little under seven days, and is the only one that accepts an IP address as an identifier.1 The six-day and IP options became generally available in January 2026.2
What a six-day certificate is for
The reason is the one behind the whole schedule: revocation does not work well, and a short lifetime shrinks the window in which a stolen key is useful.2 Six days is for the endpoints where that window matters most: the login page, the API gateway, anything an attacker would want to impersonate for as long as possible. It is also the class of certificate the rules allow to omit revocation pointers entirely, because expiry does the job.3
What an IP certificate is for
Services reached by address rather than name: a DNS resolver, a management interface, an appliance, a bootstrap endpoint that has to work before DNS does. Until this year those mostly used a private certificate, a commercial public one, or nothing. Validation for an address works like validation for a name, restricted to the HTTP and TLS-ALPN challenges, because there is no DNS zone to prove control of.2
What it costs to run
- Renewals in the hundreds. Let's Encrypt asks that certificates shorter than ten days be renewed halfway through their lifetime, which for 160 hours is every three and a third days: over a hundred renewals a year per certificate.4
- Tolerance measured in days. An authority outage, a DNS misconfiguration or a broken client that a 90-day certificate would ride out becomes an incident within the week.
- Clocks that agree. A certificate valid for hours makes clock skew between issuer, server and client a real failure mode.
- Rate limits that do not bite. Renewals driven by the authority's renewal information are exempt from rate limits, so the volume is allowed; the point is that your client must use it.5
The same idea inside the walls
Week-long public certificates are the public web catching up with what private infrastructure has done for a while: workload and SSH credentials that live minutes, issued on proof of identity, renewed by machines. trstctl issues those internally with default lifetimes of ten minutes for attested workload certificates and fifteen minutes for attested SSH user certificates.6 On the public side, its Let's Encrypt driver requests the profile you configure, so the six-day and 45-day profiles are a setting, not a code change; without one it gets the default 90-day classic certificate. It orders DNS names only, not IP addresses, and its profile requests are tested against a local ACME server, not yet against Let's Encrypt itself.7
The workload identity page covers short-lived internal credentials, and the limitations page explains profile selection and its limits.
Sources
- Let's Encrypt, Profiles: classic (90 days), tlsserver (45 days), shortlived (160 hours, DNS and IP identifiers), selected through the ACME profile field.
- Let's Encrypt, Announcing Six Day and IP Address Certificate Options in 2025, with the January 2026 general-availability update.
- CA/Browser Forum, Ballot SC-063v4: the short-lived certificate class.
- Let's Encrypt, Integration Guide, "When to renew".
- Let's Encrypt, Rate Limits.
- trstctl documentation, Workload identity and SSH: ten- and fifteen-minute default lifetimes for attested credentials.
- trstctl documentation, Limitations, "ACME certificate profiles".