Integration and Cloud

Your SSL certificate no longer lasts a year

In this article

Nori.mx7 min read

Maximum lifetimeper yearBefore398 days1Mar 15, 2026200 days2Mar 15, 2027100 days4Mar 15, 202947 days8+Let's Encrypt: 64 days from Feb 10, 2027Where they liveSite and portalCustomer APIVPN and webmailProxyOne, in many places*.yourcompany.com

For years, the certificate on the supplier portal was renewed the same way: an email arrived a month ahead, somebody bought it for a year, installed it and set a reminder for the next one. That habit no longer works. Since March 15, 2026, no public certificate can last more than 200 days. On March 15, 2027 the maximum drops to 100, and in 2029 it reaches 47.

The dangerous part is that it barely shows yet. Certificates bought before March 2026 could last up to 398 days, so many are still valid and will expire between now and mid-April 2027. Whoever renews them will do what they always did, and the new certificate will last half, or a quarter, of what their reminder says.

What changed and who decided it

Certificate rules are set by the CA/Browser Forum, where the authorities that issue certificates sit with the companies that build browsers. In April 2025 they approved this schedule without a single vote against; Apple, Google, Microsoft and Mozilla voted in favor.

If issued Lasts up to
Before March 15, 2026 398 days
March 15, 2026 to March 14, 2027 200 days
March 15, 2027 to March 14, 2029 100 days
From March 15, 2029 47 days

A 200-day certificate gets renewed twice a year. A 100-day one, four times. A 47-day one, eight times or more, because nobody waits for the last day. Doing it by hand twice a year is a nuisance; eight times a year, on five different devices, is a mistake that will happen sooner or later.

If you use Let’s Encrypt, its certificates already lasted 90 days, and they are getting shorter too: from February 10, 2027 it issues them for 64 days, and from February 2028 for 45. A scheduled task that renews every 60 days will be late.

There is a second change that shows less. Before issuing a certificate, the authority checks that the domain is yours, usually with a DNS record or an email to the administrator. That check could be reused for over a year. Today it is good for 200 days, in March 2027 it drops to 100, and in 2029 to ten. If your domain’s DNS is run by the agency that built your website years ago, every renewal depends on them answering in time.

The rule applies to the certificates a browser trusts without installing anything: the ones bought from a certificate authority or obtained from Let’s Encrypt. Those issued by your own internal authority, such as the one in Active Directory, last as long as you decide and do not change.

Where a plant’s certificates live

Almost nobody has just one. The usual ones:

  • The company website and the supplier or customer portal.
  • The API your customer, your carrier or your customs broker calls to send you data or ask for it.
  • Remote access: the firewall VPN, the remote desktop gateway and webmail, if email still runs on your own server.
  • The proxy or load balancer in front of internal applications that were published to the outside.

It is also common for a single certificate covering the whole domain (*.yourcompany.com) to be installed in several of those places at once. Renewing it means installing it in all of them, and the one that gets forgotten is the one nobody checks until it fails.

What breaks when it expires

On a website, expiry is visible: the browser shows a red screen and somebody calls. The trouble is in everything without a screen.

Integrations stop going through. When your API’s certificate expires, your customer’s system refuses the connection and does not tell a person: it retries, fails, and at some point stops trying. Orders, ship notices or confirmations stop arriving, and the first sign is usually someone asking about a shipment that does not show up. If you connect with your customer over EDI across the internet, the same thing happens.

Shop floor terminals stop syncing. A scan gun or a tablet that talks to the server over HTTPS keeps storing reads it cannot upload, if it stores them at all.

Some customers pin your certificate. Some trading partners register your certificate in their system and ask you to send the new one before you switch. With one-year certificates that was a yearly chore. With 100-day certificates it is four coordinated swaps a year, and it is worth agreeing with them to trust the issuing authority rather than each certificate.

People get used to clicking “continue.” If the red screen shows up on an internal application and somebody teaches everyone to click “continue anyway,” that habit stays around for the day the warning actually matters.

And do not expect anyone to warn you. Let’s Encrypt stopped sending expiry emails on June 4, 2025. Commercial authorities do send them, but to the email of whoever bought the certificate, who sometimes no longer works at the company. It is the same story as software nobody documented: one person held the key.

What to do before March

  1. Make the full list. Look up your domain in a certificate transparency log, such as crt.sh. Browsers require every public certificate to be recorded there, with its expiry date, so you will also see the ones nobody remembers asking for.
  2. Write down where each one is installed. The log tells you which certificates exist; it does not tell you which devices they are on. That part comes from going through the firewall, the servers and the website provider, and it is what takes the longest.
  3. Automate renewal wherever you can. The protocol is called ACME: the server requests the certificate, proves the domain and installs it on its own. Let’s Encrypt has used it from the start, and many commercial authorities now offer it. On Linux it is handled with certbot, and on a Windows server with IIS, with win-acme. Several recent firewalls and load balancers ship with their own ACME client; the ones that do not can sit behind a proxy that has one, or be renewed with a script through their API.
  4. Set up an alert that does not depend on one person. A monitor that checks every certificate on the list daily and warns when one has less than two weeks left, which is when automatic renewal should already have run. The alert goes to a shared mailbox, not to the inbox of whoever installed it.
  5. Find out who controls your DNS. If it is not someone at your company, get access or move the domain to an account you own. With domain checks coming around more and more often, it cannot depend on a third party who answers when they can.

The real fix

What changed is not the certificate: it is that renewal can no longer live on one person’s calendar. At 47 days, the only setup that holds is one that renews on its own, installs everywhere the certificate lives, and raises an alert when any of that fails.

Requesting the certificate is the easy part. The hard part is everything around it: the old device that only takes a new certificate if somebody uploads it by hand, the integration that has it copied inside its configuration, the server nobody is quite sure who runs. That is what needs finding before March, while certificates still last 200 days and there is time to test.

Where we come in

This is part of our integration and cloud work: listing where every certificate lives, setting up automatic renewal on the servers and devices that allow it, solving the ones that do not, and putting in the monitoring that warns you before an integration goes down. If you want to start with the list, send us your domain and we will tell you which public certificates it has and when each one expires. And if you want to know what else is worth reviewing in your systems, Chira asks you the questions in five minutes and leaves you a document with what to fix first.

References

Related service

Integration and Cloud

Make your ERP, your warehouse and your store speak the same language.

See the service

Articles on this service

IRS calendarNov 1Last testsNov 9TCC changesNov 19, 3 p.m.FIRE shuts downJan 1IRIS onlyYour FIRE file1099 · 2026from your accounting systemIRIS won't take itIRIS has two doorsPortalCSV, up to 100A2AAPI, up to 100 MB

Integration and Cloud

Your January 1099s won't go through FIRE

The IRS shuts down FIRE on November 19 and from January 1099s can only be e-filed through IRIS. Who needs a new code, what changed and which data to check.

6 min read

ANSI X12830Forecast862Firm schedule850/860PO and change856Ship notice810Invoice997Acknowledgment824Error notice856 · ASNPallet › box › pieceSent when the truck leavesBox labelSame ID

Integration and Cloud

When your customer demands an EDI connection

The email with the deadline just arrived. What they are actually asking for, which path fits your volume, and the chargeback nobody mentions up front.

7 min read