"Your connection is not private" is the warning a browser shows when it cannot confirm a website's security certificate. If customers see it on your website, many of them will leave before the page loads. The fix is usually quick once you know which of five causes you have, and this month one of them is in the news: Microsoft and Google have acted against parts of the eMudhra certificate hierarchy.
Our view as web developers: a certificate warning is not a cosmetic issue. With Black Friday on 27 November, it is an outage that happens to have a polite message on it.
What does "Your connection is not private" mean?
Every secure website has a certificate. It proves the site is the one in the address bar and lets the browser encrypt what visitors type, from passwords to card details. Before a page loads, the browser checks three things: the certificate is in date, it covers this exact address, and it was issued by an authority the browser trusts.
If any check fails, Chrome shows "Your connection is not private" with an error code underneath. Other browsers show similar warnings in their own words. Google's Chrome help page on connection errors lists the common codes, including errors about the certificate's date, its name (ERR_CERT_COMMON_NAME_INVALID) and its issuer (NET::ERR_CERT_AUTHORITY_INVALID), and notes that a wrong date and time on the visitor's device can cause one of them. The code tells you where to look.
Why is my website showing "Your connection is not private"?
When the warning appears on your own site, it is almost always one of these five causes.
1. Has the certificate expired?
Certificates last months, not years, so they have to renew. Renewal often fails quietly: a card on file expires, a DNS change breaks the automatic check, or a host moves your site and the renewal job stays behind. The code is usually NET::ERR_CERT_DATE_INVALID.
- Click the icon left of your address bar, open the certificate details and check the expiry date.
- Find out who renews it: your host, your CDN, your developer or you.
- Set a calendar reminder 30 days before expiry, even if renewal is automatic.
2. Does the certificate cover this exact address?
A certificate for `example.com.au` does not cover `www.example.com.au` unless both are listed. New subdomains, a shop on a separate address, or a recent domain change all cause this. The code is usually ERR_CERT_COMMON_NAME_INVALID.
- List every address customers use: with and without www, your shop, booking and landing page subdomains.
- Check each one is named on the certificate, or that the extras redirect cleanly to one that is.
3. Has your certificate issuer lost browser trust?
This is the cause in the news. Browsers keep a list of certificate authorities they trust. When an authority has a serious failure, browsers remove it, and every certificate it issued starts failing. The code is usually NET::ERR_CERT_AUTHORITY_INVALID.
- Check who issued your certificate in its details.
- If the issuer is eMudhra or emSign, read the next section and plan a replacement now.
4. Is part of the certificate chain missing?
Your certificate links back to a trusted root through one or more intermediate certificates. If the server does not send the full chain, some browsers and phones fail while others work, because some fill the gap and some do not. This one confuses people because the site loads fine on the developer's laptop.
- Test on a phone on mobile data and in a private window, not just your usual browser.
- Ask whoever installed the certificate to install the full chain from the issuer.
5. Is the problem on the visitor's device?
Sometimes your site is fine. A wrong date on the visitor's device, public Wi-Fi that intercepts traffic, or security software that inspects connections can all trigger the warning for one person only.
- If one customer reports it and nobody else can reproduce it, ask them to check their device's date and try another network.
- If several customers report it on different networks, assume it is your site and check causes 1 to 4.
What changed with eMudhra certificates in November 2026?
eMudhra is a certificate authority whose roots were trusted by the major browsers. In October 2026, private keys for eight of its intermediate certificate authorities were reported as compromised. Microsoft's security team set out its response and said it would remove the remaining 10 eMudhra roots from its Trusted Root Program from 16 November 2026, with Windows, Edge and WebView2 all dropping trust in the remaining roots (Microsoft). Its advice to customers is to replace dependent certificates.
On 13 November, iTnews reported that eMudhra had revoked another eight intermediate certificate authorities and would stop issuing from its G1 hierarchy on 17 November. iTnews also reported that eMudhra said Apple would end trust in its certificates on 30 November. We have not seen a statement from Apple.
Google blocked the compromised intermediates in Chrome and removed one emSign root. It also said certificates from the emSign Root CA G1 first logged in public certificate records after 16 November 2026 will not be trusted by default in Chrome 153 and higher. For the removed emSign root, it told affected site owners to get a new certificate from another hierarchy (Google).
What this means in practice: a site on an eMudhra certificate may already fail for Windows and Edge users, eMudhra has said Apple devices will follow on 30 November, and a renewal from the same hierarchy may not be trusted in newer Chrome versions. If your site uses one, the timing lands in a busy trading fortnight, with Black Friday on 27 November.
What this means for your website
For most business owners, the lesson is bigger than one certificate authority. Your certificate is a supplier, and you probably do not know who it is. That is fine until it fails.
- Know who issued your certificate and who renews it. Write both down.
- Get an alert when a certificate is close to expiry or changes unexpectedly.
- After any hosting, DNS or domain change, check every address on the site loads without a warning.
- Check your checkout, forms and login pages specifically. They are where a warning costs the most.
Certificates are one of several quiet dependencies on a business site. Plugins are another, which is why the WordPress vulnerability fixed in 7.1.4 needed fast updates too.
What this means for web development in Australia
For our industry, the eMudhra case is a reminder that a launch checklist ends too early if it stops at "SSL installed". Developers should hand over who issued the certificate, how it renews, which addresses it covers and who gets the expiry alert. Hosting moves and DNS changes should include a certificate check on every address, not just the home page. Small habits like these turn a lost sales weekend into a five-minute fix.
How Web Mage can help
If your site is showing the warning right now, treat it as urgent and contact us. We will check which cause you have and tell you what needs to change, and who needs to change it.
- Our website maintenance plans include uptime and security monitoring, so a problem is caught early, plus developer hours to fix it.
- Running an online store before Black Friday? Our ecommerce team can check that your checkout and payment pages work, and help you review every address customers use.



![6 Best Web Design Agencies in Brisbane [2026]: featured image](/wp-content/uploads/2026/11/brisbane-web-design-agencies-featured-webmage.webp)