eMudhra SSL Certificate: Check If You Are Affected

Summarize this article with AI:

Table of Contents

Chrome no longer trusts any eMudhra SSL certificate that chains to emSign ECC Root CA - G3, so you must replace it now. Certificates under the emSign G1 root need a plan too, because browsers are tightening trust on that hierarchy this month.

A root removal means a browser deletes a certificate authority's top-level certificate from its trust list. Every certificate that chains to that root then shows a full-page warning.

What happened to the eMudhra root in Chrome?

Researchers found on October 17 that the private keys behind eight eMudhra intermediate CAs were weak enough to compute. Google then removed emSign ECC Root CA - G3 from the Chrome Root Store.

The removal reached Chrome devices on October 27, and eMudhra announced its TLS exit on October 22. According to Google's Chrome security announcement, some legitimate certificates under this root also stop working.

The timeline below shows why the story did not end on October 27.

Date (2026)Event
17 OctWeak keys found in eight intermediates. Chrome and Firefox block the affected website certificates.
20 OctGoogle announces removal of emSign ECC Root CA - G3 from the Chrome Root Store.
22 OcteMudhra announces its exit from TLS and offers Sectigo-issued alternates.
27 OctThe G3 root removal reaches Chrome devices.
4 NovGoogle adds a G1 rule: Chrome 153 and higher stops trusting new G1-chain certificates by default.
30 NovApple G1 removal date, as listed by eMudhra.

So the G3 problem is already live, while the G1 changes are still rolling out.

Is my SSL certificate affected?

Affected certificates chain to emSign ECC Root CA - G3 or emSign Root CA - G1. Certificates from other authorities are not part of this action.

First, find your chain's top-level name in the table. Then confirm it with the checks below.

Your chain ends atCurrent statusWhat to do
emSign ECC Root CA - G3Removed from the Chrome Root Store; Mozilla removed it tooReplace now
emSign Root CA - G1, first logged after 16 NovNot trusted by default in Chrome 153 and higherReplace now
emSign Root CA - G1, first logged on or before 16 NovWorks in Chrome; Apple lists 30 Nov as its G1 removal dateReplace before 30 Nov
Any other CANot affected by this actionNo action; keep monitoring

The G1 rows depend on the date of the certificate's earliest Signed Certificate Timestamp (SCT), which is the first time it was logged publicly. Google's 4 November update sets the cut-off at 16 November, 11:59:59 PM UTC.

Use these checks to read your chain:

  1. Open your site in Chrome, click the padlock icon, and view the certificate's certification path.
  2. Run openssl s_client -connect yourdomain.com:443 -servername yourdomain.com -showcerts and search the output for "emSign" or "eMudhra".
  3. Run the domain through the SSL checker tool, then compare it with the chain you saw in the browser.
  4. Repeat the check on every system that uses certificates, including APIs, mail servers and load balancers.

Warning Sign
A missing root in the OpenSSL output does not prove you are safe. Servers usually send only the leaf and intermediate certificates, so read the issuer name instead.

How do I replace an affected certificate?

Order a new certificate from a CA in the Chrome Root Store, then install it with its full chain. A new intermediate alone does not help if the chain still depends on a removed root.

Follow these steps in order:

  1. Choose a CA that is currently trusted by Chrome, and order the replacement.
  2. Add the new CA to your DNS CAA record first, if your domain has one. Otherwise the order may fail.
  3. Install the certificate with the full chain your CA provides.
  4. Point ACME clients such as Certbot or acme.sh to the new CA, so renewals do not return to eMudhra. Review your automated certificate management setup for the same reason.
  5. Reload the site in Chrome and confirm the issuer now shows the new CA.

Diagnostic Tip
After installing, run the OpenSSL command once more. Then confirm the server sends the intermediate. Some clients fail without it, even when Chrome loads the page.

What else can break outside the browser?

Browsers are only one part of the problem, because many systems keep their own trust lists. Check every service that presents or validates a certificate.

Prioritize these areas:

  • APIs and partner integrations that pin or validate a specific chain.
  • Load balancers, VPN gateways and security appliances.
  • Mail servers and other non-web services.
  • Java runtimes, containers and base images that ship their own trust stores.

For example, a container image built last year may still trust the old hierarchy. Rebuild it after you update the certificate, and test the connection from a client that does not use Chrome.

Should I take eMudhra's replacement or choose my own CA?

eMudhra says it has offered Sectigo-issued certificates to customers since October 22, so a no-cost path exists. You can also buy from any CA in the Chrome Root Store, which gives you a direct vendor relationship.

OptionWhat you getWhat to check
eMudhra-arranged Sectigo certificateReplacement handled through eMudhra, at no charge according to eMudhraValidity period and who supports renewals after eMudhra exits
Certificate from your own CAYou pick the CA, product and validation levelYou order, validate and install it yourself

If you are unsure which product fits, compare SSL certificate types before you order. Also note that Google is still reviewing whether eMudhra's remaining roots should stay in the Chrome Root Store.

How do I avoid depending on one CA next time?

Keep a second approved CA ready and automate issuance. Then a distrust event is a reissue task, not an outage.

This incident left about ten days between the first block and the root removal. A practical multi-CA strategy starts with three habits:

  • Keep an inventory of which CA issued every certificate you run.
  • Allow at least two CAs in your CAA records.
  • Test an ACME switch to your backup CA before you need it.

FAQ

My eMudhra certificate still works. Do I need to replace it?

Yes, if the chain ends at emSign ECC Root CA - G3, because Chrome removed that root. G1 certificates logged by 16 November still work in Chrome. Apple lists 30 November as its G1 removal date, so plan the replacement now.

Were fraudulent certificates issued with the weak keys?

The sources reviewed show no confirmed report of misuse. The keys were weak enough that anyone could compute them, which is why browsers blocked the affected certificates.

Are my eMudhra code-signing or digital signature certificates affected?

This guide covers TLS website certificates only. Two of the eight intermediates issue code-signing certificates that Microsoft trusts, so ask eMudhra about those directly.

Will I have to pay to replace my certificate?

eMudhra states that it offers alternate certificates to its TLS customers at no charge. If you buy from another CA yourself, you pay that CA's normal price.

Is only Chrome affected?

No. Firefox also removed the G3 root, and Apple and Microsoft blocked the affected certificates in the days after October 17. Apple lists a separate G1 removal date of 30 November.