The yearly SSL renewal is over: certificates are capped at 200 days today, 100 days from 15 March 2027 and 47 days from 2029. Who has to act, who does not, and what to ask your agency or IT provider this month.
On this page
Most business owners we meet in Dubai know their website "has an SSL" because once a year somebody renews it: the agency, the host or an IT contractor. That yearly rhythm is over. Since 15 March 2026 no public website can be issued a one-year certificate, and from 15 March 2027 the maximum is 100 days.
If your certificate renews automatically, you should not notice. If a person installs it by hand, the job is about to come round four times a year, and one missed renewal puts a browser warning in front of every visitor.
What changed, and when
An SSL certificate is the file on a server that lets a browser confirm it has reached the real site and encrypt the connection: the "s" in https. Its proper name is a TLS certificate; "SSL" is the older name that stuck (Let's Encrypt glossary).
Certificate authorities, the organisations that issue them, follow rules set with the browser makers in the CA/Browser Forum. In April 2025 the Forum adopted ballot SC-081v3, proposed by Apple, with Google, Microsoft and Mozilla in favour and no votes against (CA/Browser Forum ballot record). It cuts the longest life a public certificate may have, in steps (TLS Baseline Requirements, section 6.3.2):
- Before 15 March 2026: 398 days, hence the yearly habit.
- From 15 March 2026: 200 days, the rule as of November 2026.
- From 15 March 2027: 100 days.
- From 15 March 2029: 47 days.
Each limit applies to certificates issued on or after its date, so one you already hold runs to its expiry date. The last one-year certificates will be gone by mid-April 2027.
How long an authority may reuse its check that you control the domain shrinks on the same dates: 200 days now, 100 from March 2027, 10 from March 2029.
If renewal is automatic, little changes
Short certificates only hurt when a person installs them. Three common set-ups already renew certificates of 90 days or less by software:
- Cloudflare. It issues and renews free certificates for the domains on its network; they last 90 days and renewal starts 30 days before expiry (Universal SSL; validity periods).
- Let's Encrypt. The free, non-profit authority has issued 90-day certificates since 2015 and is going shorter than the rule demands: 64 days by default from 10 February 2027, 45 days from 16 February 2028 (Let's Encrypt).
- A host that manages it. Many hosts obtain and manage Let's Encrypt certificates for their customers (Getting started).
Two cautions. Let's Encrypt asks automated users to check that their set-up copes with shorter lives; a fixed 60-day timer will no longer be enough. And Cloudflare covers the visitor's side only: if the server behind it has its own certificate and that expires, its strict setting shows an error page (Error 526).
Who has work to do
Anyone whose certificate is bought, downloaded and installed by a person:
- A certificate bought "for a year" from a reseller or host and installed by hand on a web server.
- A firewall, a VPN gateway, a mail server or an old appliance with its own login page.
- Subdomains nobody remembers: a client portal, a booking system, last year's campaign site.
- A multi-year "subscription". You pay once, but the certificates inside it are short: DigiCert says the first lasts at most 199 days and that reissuing "does not update the expiring certificate on your website automatically" (DigiCert, Multi-year Plans).
For these, once a year has become twice. From March 2027 it is about four times and from 2029 about eight.

What happens when one lapses
Nothing fails gently:
- Browsers block the page. Chrome's certificate error reads "Your connection is not private" (Chrome Help), and Apple tells Safari users never to enter a password or card number on a site whose certificate has expired (Apple Support). Where a site sends the HSTS security header, as the sites we host do, returning visitors cannot click through (MDN).
- Enquiries and orders stop. Every form, checkout and paid click ends at that warning until someone notices.
- Software is stricter than people. Stripe checks for "a valid server certificate" before it sends a payment event to your server (Stripe); Meta requires one on any server that receives notifications from its platforms (Meta for Developers), and by default an iPhone app refuses a server whose certificate has expired (Apple Developer).
- Search notices. Google may stop preferring a page's HTTPS version when its certificate is invalid (Google Search Central); see technical SEO before a site launches.
Check your own certificate in two minutes
- In Chrome on a computer, click the icon at the left of the address bar, then "Connection is secure", then "Certificate is valid". The window shows who issued the certificate and when it expires.
- Our rule of thumb until March 2027: a life of 90 days or less points to automatic renewal; around 200 days suggests a purchased certificate, so ask who installs it.
- Repeat for every address the business uses: the shop, the client portal, webmail, the VPN login.
Questions to ask this month
Send these to whoever looks after the website, the server and the office network:
- Which certificates do we have, on which addresses and devices, and when does each expire?
- Who issued each one, through whose account, and which mailbox gets the notices?
- Is each renewal automatic, and how would we find out that one had failed?
- If it is manual, who does it, who covers for them, and what is the plan for four renewals a year?
- Which devices cannot renew automatically, and what happens to them?
A supplier who replies "it renews every year" has not read the rule.
Watch the expiry date yourself
Do not count on a reminder email. Let's Encrypt stopped sending expiry notices on 4 June 2025 (Let's Encrypt), and in our experience a reseller's reminders go to whoever placed the order, often a former employee or a previous agency. Two cheap safeguards, worth having even with automatic renewal:
- A monitoring service that emails more than one person as expiry approaches. Let's Encrypt lists several and recommends Red Sift Certificates Lite, free for up to 250 certificates (monitoring options).
- A shared calendar entry three weeks before each expiry, with a named owner and a deputy.
What automation means, and what it costs
Automation means a small program on the server, or a service in front of it, requests a new certificate before the old one expires, proves control of the domain and installs the result with nobody logging in. The standard protocol is ACME (RFC 8555); Let's Encrypt recommends the Certbot program and lists others, including several for Windows (ACME clients).
The certificate is the small part of the cost:
- It can be free. Let's Encrypt charges nothing (FAQ) and Cloudflare's Universal certificates are free. As we wrote in how much a website costs in Dubai, a quote that charges separately for "SSL" deserves a question.
- A paid one need not cost more for being replaced often. DigiCert, for one, says its price is an annual subscription (DigiCert).
- The real cost is set-up work, which varies too much for us to put a figure on. A web server is a one-off job; a firewall or appliance that cannot run such a program may need a firmware update, another server in front of it, or replacing. Ask for that estimate now.
Do you still need an OV or EV certificate?
Organisation-validated (OV) and extended-validation (EV) certificates add a check of the company to the check of the domain; EV exists to identify "the legal entity that controls a Web site" (EV Guidelines). What EV has lost is its place in the address bar. Chrome moved the company name out in version 77, after finding that the badge "does not protect users as intended" (Chromium); Apple had removed it from Safari in 2018 (CA/Browser Forum), and Firefox followed in version 70 (Mozilla). The verified name is still inside the certificate. Buy one if a bank, a tender or a contract asks for it. Let's Encrypt does not issue them, the company check must be repeated at least every 398 days, and DigiCert says its ACME service can automate them.
Most sites need no new budget, only a list: every certificate, where it lives, who renews it and how. Automate what you can and monitor the rest before March. We host the sites we build behind Cloudflare, which terminates TLS at the edge; the reasoning is in how we host the sites we build.
Sources
- CA/Browser Forum, Ballot SC-081v3: the vote and the proposer.
- CA/Browser Forum, TLS Baseline Requirements: the schedule (6.3.2) and validation reuse (4.2.1).
- DigiCert, TLS certificate lifetimes will officially reduce to 47 days and Understand Multi-year Plans: an authority's account of the dates, pricing and ACME.
- Let's Encrypt, Decreasing certificate lifetimes to 45 days, glossary, Getting started, FAQ, ACME clients, expiry emails and monitoring options.
- Cloudflare, Universal SSL, Validity periods and renewal and Error 526.
- Google Chrome Help, Apple Support and MDN, Strict-Transport-Security: browser warnings.
- Stripe, Webhooks, Meta for Developers, Webhooks, Apple Developer, Preventing insecure network connections and Google Search Central, canonical URLs: integrations, apps and search.
- IETF, RFC 8555: the ACME protocol.
- CA/Browser Forum, EV Guidelines and 2018 minutes, Chromium, EV UI moving to Page Info and Mozilla Security Blog: EV in browsers.
- The questions and the rule of thumb are our own practice.
- SSL certificates
- TLS
- HTTPS
- website security
- hosting



