7. Oktober 2026 – IACBOX

Update on TLS Certificates

To increase the security of TLS certificates, the CA/Browser Forum decided in 2025 to shorten the maximum validity of certificates in several steps from the previous 398 days to 47 days. We already presented the schedule at that time in our blog article (https://www.iacbox.com/blog/gueltigkeit-von-tls-zertifikaten-wird-verkuerzt/).

Since March 15, 2026, certificates may be valid for a maximum of 200 days, from March 2027 only 100 days, and from March 2029 only 47 days.

We will therefore switch to Let’s Encrypt certificates in the first quarter of 2027. Since the certificate for our default domain hotspot.internet-for-guests.com expires in November 2026, we are delivering one last certificate with a 200-day term (valid until April 2027) with IACBOX update 24.3.6. This allows sufficient time for a relaxed transition. As an IACBOX operator, however, you will not notice any of this.

Certificates Independent of Software Updates

Previously, TLS certificates were delivered with software updates—the certificate in version 24.3.6 is the last of its kind. In contrast, short-lived Let’s Encrypt certificates are distributed independently of software updates, similar to DNS filter lists. The infrastructure for this has already been included in the IACBOX for several months. IACBOXes with valid Software Maintenance will therefore always receive an up-to-date TLS certificate in the future, regardless of the installed software version. To ensure that things do not get tight in the event of a late Software Maintenance renewal, there is a grace period of several weeks.

Technical Impact

As a captive portal, we must take a conservative approach when choosing the Root CA (Certificate Authority), as even the oldest possible devices should trust the certificate issuer. The Let’s Encrypt Root CA (ISRG Root X1) was created in 2015, has been included in all common operating systems and browsers since 2016-2018, and is now correspondingly widespread. Older devices were previously covered via a cross-signature from an older CA. When this expired in 2021, problems occurred with some old devices.

Furthermore, we are switching from RSA to EC (Elliptic Curve) certificates. These have been widely supported for many years, are significantly smaller, and thus accelerate connection establishment.

White Label Partners

In the future, we will handle the issuance and distribution of partner certificates for our white label partners. For this, we only require an additional DNS entry with which the domain validation towards Let’s Encrypt is delegated to us. We will contact our white label partners regarding this in the coming months.

Own Domains

Those using their own domain can also upload TLS certificates via the Admin API (formerly Batch API) since version 24.3.0. In this way, the IACBOX also integrates seamlessly into your automated environment here. Click here for the API documentation (https://manual.iacbox.com/admin-api/24/). Additionally, a ready-to-use upload shell script is available (https://manual.iacbox.com/iacbox/24.0/docs/interfacing/admin-api/#api-helper-scripts), which can be used as a deploy hook for certbot and practically any other ACME client.

Outlook: Post-Quantum Cryptography

However, 47 days is not the end. Merkle Tree Certificates (MTC) are already appearing on the horizon. They are intended to make signature methods that can withstand quantum computers practical on the web—because their signatures are significantly larger than today’s. MTCs are expected to be valid for only a few days and will be supported by Google starting at the end of 2027.

Automated certificate management will thus become the norm by 2027 at the latest. Stay secure and up to date—with IACBOX Software Maintenance.