
A customer sends you a screenshot: a red warning page saying “Your connection is not private” with the code NET::ERR_CERT_DATE_INVALID. Your website, the one your ads and name cards point to, now looks unsafe.
This guide is for Malaysian business owners and marketers facing an “SSL certificate expired” warning right now. It shows how to confirm the problem, why automatic renewal failed, the fix with realistic timelines, and how to stop a repeat.
One scope note: if your site loads normally but the padlock shows a warning because some images or scripts still load over HTTP, that is a different problem. See our guide to fixing a mixed content warning after SSL instead.
The short video below covers the visitor-side checks, such as the device clock and browser cache. Use it to rule out one device before you change anything on your website.
Source video: Watch on YouTube (QuickHelper)
Quick Answer: An expired SSL certificate means the digital ID that proves your website is genuine has passed its end date. Browsers no longer trust it, so they show a full-page “not private” warning before your site loads. The encryption itself still exists, but visitors are told the connection may be unsafe.
Every certificate has a start date and an end date. When the end date passes, browsers treat the certificate like an expired passport: real, but no longer valid. Our plain-English explainer on SSL and HTTPS covers how certificates work. Customers may describe the warning in different words depending on their browser:
| Browser | Warning headline | Typical error code |
|---|---|---|
| Chrome / Edge | Your connection is not private | NET::ERR_CERT_DATE_INVALID |
| Firefox | Warning: Potential Security Risk Ahead | SEC_ERROR_EXPIRED_CERTIFICATE |
| Safari (iPhone / Mac) | This Connection Is Not Private | No code shown; certificate details say “expired” |
| Outlook / mail apps | The security certificate has expired or is not yet valid | Pop-up when sending or receiving mail |
Source: browser and mail-app warning pages observed by ZenWeb on Malaysian client sites, checked October 2026. Wording can change between versions.
If the page does not load at all and the browser says it “can’t provide a secure connection”, that is a handshake failure instead. Our guide to the SSL protocol error on your website covers that case.
Want a website where renewals are handled for you?
Our web team sets up hosting, certificates and renewal checks as part of every build. See what our web design service includes →
Quick Answer: Browsers judge expiry using the device’s own clock, so a laptop set to the wrong date shows the same warning. If the warning appears on every phone and computer, your SSL certificate has expired. If only one device complains, fix that device’s date, time zone and browser first.
Spend five minutes confirming before you call anyone:
Also test both yourdomain.com.my and www.yourdomain.com.my. Sometimes only one version has lapsed, for example when the www address points somewhere else after a DNS change. If you recently moved your domain, read why DNS may not be propagating after a domain change.
Quick Answer: Most certificates renew automatically, so an expiry usually means renewal failed quietly. The top cause is a domain validation check that failed after a DNS or CDN change. Next come unpaid or suspended hosting, a paid certificate renewed but never installed, and a domain that now points somewhere else.
When Malaysian SMEs bring us an expired certificate, the real question is “why did renewal stop working?” The chart shows what we usually find.
| Root cause | Share of cases |
|---|---|
| Domain check failed after a DNS or CDN change | 34% |
| Hosting unpaid or suspended (expired card, missed invoice) | 22% |
| Paid certificate renewed but never installed | 18% |
| Auto-renew never set up (manual certificate) | 14% |
| Domain itself lapsed or pointed to a parked page | 12% |
Source: From ZenWeb client tracking across Malaysian SME websites, 2024–2026. Illustrative of typical patterns.
What each cause looks like in practice:
Quick Answer: Settle any unpaid hosting first, then open your hosting panel’s SSL section and reissue the free certificate for your domain and www. If you use a paid certificate, renew it and install the new file. Check the CDN certificate too, clear every cache and retest from outside your network.
Work through these steps in order. Each one removes a cause from the chart above:
Once the certificate is valid, open Search Console and check the Pages report for crawl errors. Look at enhancements as well, because a broken HTTPS period often surfaces alongside structured data errors and rich result warnings.
Quick Answer: A free certificate reissue usually clears the warning within minutes to a few hours. A suspended hosting account adds the time your host takes to reactivate it. Paid business-validated certificates need a few working days for document checks, so a free certificate is the fastest way back online.
Use this table to set expectations with your team and your boss:
| Fix applied | Typical time to clear | What slows it down |
|---|---|---|
| Free certificate reissue (AutoSSL / Let’s Encrypt) | Minutes to a few hours | Failed domain check, CDN cache |
| Hosting reactivation after payment | A few hours to 1 working day | Weekend billing teams, bank transfer clearing |
| Paid domain-validated certificate | Under 1 hour to 1 day | Validation email going to an old inbox |
| Paid organisation-validated certificate | About 1–5 working days | SSM documents, company phone verification |
| Domain renewal or DNS fix | Up to 72 hours | DNS caches around the world |
Source: ZenWeb operational observations, Malaysian SME websites, 2024–2026. Times vary by host and certificate issuer.
For an organisation-validated certificate, the issuer checks that your company is real, so keep your SSM documents ready and answer the publicly listed company phone. Stuck waiting? Install a free certificate first, then swap in the paid one later.
Quick Answer: More than the home page. Ad platforms may reject or stop ads with an unsafe landing page, product feeds can stall, analytics loses visits that never load, and mail apps throw certificate pop-ups. Check each channel once the certificate is fixed, because some will not recover by themselves.
Use this checklist after the fix to catch the knock-on effects:
| Channel | Typical symptom | Recovers by itself? |
|---|---|---|
| Google Shopping | Products disapproved for an unavailable landing page | Often needs a re-crawl or feed refresh |
| Meta catalogue ads | Product links flagged, delivery drops | Usually after the next feed update |
| GA4 analytics | Traffic and conversion dip for the outage days | Yes, but the gap stays in reports |
| Business email | Outlook certificate pop-ups, failed sending | Only once the mail server certificate is renewed |
| Google organic search | Lower clicks while visitors bounce off the warning | Usually, if fixed within days |
Source: From ZenWeb client tracking across Malaysian SME accounts, 2024–2026. Illustrative of typical patterns.
For paid channels, check why Google Shopping ads stop showing and why Meta catalogue products get no impressions. In analytics, outage days can leave odd rows; see what (not set) in GA4 reports means and why GA4 custom events stop showing. For mail, learn why a business email is not receiving messages.
Tired of chasing renewals, feeds and broken pages?
We build and look after business websites with HTTPS, monitoring and clean tracking set up properly. Get a secure, well-maintained website →
Quick Answer: Rely on automatic renewal, but watch it. Certificate lifetimes are shrinking every year, and some issuers no longer email expiry reminders, so add an outside monitor that alerts you weeks before expiry. Keep hosting billing current and recheck renewal after every DNS, CDN or hosting change.
Renewals now happen far more often than they used to. Let’s Encrypt’s FAQ says its standard certificates last 90 days. Let’s Encrypt also stopped sending expiration notification emails on 4 June 2025, so many owners no longer get a warning. Paid certificates are getting shorter too, under CA/Browser Forum Ballot SC081v3:
| Certificates issued | Maximum lifetime | Renewals per year (minimum) |
|---|---|---|
| Before 15 March 2026 | 398 days | 1 |
| From 15 March 2026 | 200 days | 2 |
| From 15 March 2027 | 100 days | 4 |
| From 15 March 2029 | 47 days | 8 |
Source: CA/Browser Forum Ballot SC081v3 (2025). Renewals per year calculated by ZenWeb from the maximum lifetime.
With renewals this frequent, build a routine that does not depend on memory:
A dependable host makes all of this easier; compare options in our guide to web hosting in Malaysia.
Quick Answer: Escalate if renewal keeps failing after you reissue, if nobody has the hosting or DNS login, if the certificate is valid but the warning stays, or if this is the second expiry in a year. Each of these points to a setup problem rather than a one-off lapse.
Get help early in these situations:
A secure, always-on site is one of the clearest website trust signals for new visitors. ZenWeb is a Google Partner agency that has worked with 500+ Malaysian businesses. Our web design services team sets up hosting, certificates and renewal monitoring so a lapse never reaches your customers.
When your SSL certificate has expired, the warning looks alarming, but the fix is usually quick. Confirm the expiry date, settle any hosting bill, reissue or install the certificate, then clear caches and retest. The bigger job is finding out why renewal failed and adding monitoring, because certificates now renew several times a year. For more help keeping your website working for your business, start at the ZenWeb home page.
Do not ask them to. The warning means the browser cannot confirm the site is genuine, and many visitors will rightly refuse. Telling customers to bypass security warnings also trains them into unsafe habits. Fix the certificate instead; a free reissue often takes minutes.
Automatic renewal only works if the issuer can still confirm you control the domain and the hosting account is active. A DNS or CDN change, an unpaid invoice or a suspended account will stop renewal quietly. Check those first.
A short lapse fixed within a day or two rarely causes lasting harm. A long one can, because visitors bounce off the warning and Google may crawl the site less. Fix it quickly, then check Search Console for crawl errors.
No. A free certificate from your host or Let’s Encrypt removes the warning and encrypts traffic just as well. Paid organisation-validated certificates add a company identity check using your SSM documents, which some businesses prefer, but they are not required.
Website still showing “Your connection is not private”?
Talk to our web team. We’ll check your certificate, hosting and renewal set-up, and give you a clear plan to get the warning off your site.
Get A Free Proposal
Complete the form and our team will contact you to discuss your goals. Let’s grow your business.
Chat with us on WhatsApp
Tell us a little about what you need. We'll open WhatsApp with your message ready to send.