Services

Start a project Chat on WhatsApp
News & Insights

Chrome Stops Trusting New eMudhra Certificates on 16 November: What a Small Business Should Do

A designer working on a website design

From 16 November 2026, Google Chrome will stop trusting a new group of website security certificates. If your website still uses one of them, your visitors could soon see a full page security warning instead of your homepage. The fix is usually free and takes minutes, but only if you check before the deadline.

What happened

A security certificate is the file that puts the padlock in your browser address bar and proves your website is who it claims to be. On 17 October 2026, a security researcher reported that the private keys behind eight intermediate certificates from eMudhra, an Indian certificate authority that sells certificates under the emSign brand, had been generated with too little randomness. In plain language, the secret numbers were so small that they could be worked out from the public certificates. Researchers found that one of the private keys was the number 4.

The browsers moved the same day. Chrome blocked the affected keys within hours, and Firefox blocked them within three hours. eMudhra revoked all eight certificates the next day. On 20 October, Google and Mozilla published their responses. Mozilla shipped Firefox 158.0.1 and removed the root certificate that signed the affected ones, emSign ECC Root CA – G3, from its trust store. Google removed the same root from the Chrome Root Store, with the change reaching devices from 27 October.

On 22 October, eMudhra’s board decided to leave the global SSL certificate business altogether. Then, on 4 November, Google added a second deadline. From Chrome 153 onward, Chrome will not trust certificates that chain to eMudhra’s older root, emSign Root CA – G1, if their earliest public log entry is dated after 16 November 2026 at 11:59 PM UTC. That is about 5 AM Pakistan time on 17 November. Certificates logged on or before that moment keep working until they expire. Apple is reported to remove the G1 root on 30 November.

Two honest limits matter here. Google says no fraudulent certificates from the affected intermediates appeared in the public Certificate Transparency logs before its block, and eMudhra says it is not aware of any exploitation before disclosure. This is not a story about your website being hacked. It is a story about a trust decision with a date on it.

What it means for a small business

If your website still serves a certificate that chains to the removed G3 root, visitors on Chrome and Firefox already see a security warning instead of your site. Orders, bookings and enquiries stop until it is fixed, and most visitors will not come back to try again.

If your website uses a G1 certificate, it still works for now, provided it was logged before the cutoff. But do not renew with eMudhra. A replacement certificate logged after 16 November will not be trusted in Chrome, and the company is leaving this business.

Most small business websites are not affected at all. The bulk of the web runs on certificates from Let’s Encrypt, Sectigo, DigiCert or Google Trust Services. Digilistan’s own website, for example, uses Google Trust Services and Let’s Encrypt certificates, so it is not affected. A two minute check settles the question for your site.

What to do

  1. Open your website in Chrome. Click the padlock or tune icon next to the address, then Connection is secure, then Certificate is valid. Look at Issued by. If it says emSign or eMudhra, your site is affected.
  2. Check your subdomains too: shop, bookings, app, staging and any payment page.
  3. If you are affected, ask your hosting provider to reissue the certificate from a different authority. Most hosts do this free with one click, and Let’s Encrypt certificates cost nothing. Ask them to confirm the new issuer in writing.
  4. Do not accept a new eMudhra certificate as the replacement. Any G1 certificate first logged after 16 November will not be trusted in Chrome.
  5. After the new certificate is installed, open the site in a fresh browser window and check the padlock again. Then test the checkout or contact form once.
  6. If your host manages certificates for you, send them this question today: Does any certificate on my hosting account chain to emSign or eMudhra, and if so, when will it be replaced?

If your website was built or is hosted through Digilistan, ask us and we will check the certificate chain for you.

Details are correct as of 10 November 2026.

Sources

Start the conversation

Tell us what you are building

Whether you need a website, a chatbot that never sleeps or a workflow that gives your team its evenings back, start with a short conversation. We reply to every serious enquiry personally.

  • Your message goes to the founder, not a call center.
  • We suggest the smallest service that fixes the problem.
  • The first conversation costs nothing but a few minutes.

Prefer to talk first? Message us on WhatsApp and skip the form.

Chat with us