Security 11 min read ·
emSign SSL Certificate Not Trusted? What eMudhra Users Must Do
emSign SSL certificate not trusted? Check if your site chains to an eMudhra root, see the browser cut-off dates, replace it free and fix your CAA record.
If your website uses an SSL certificate from eMudhra's emSign certificate authority, browsers are withdrawing trust in it. In October 2026 a researcher showed that the private keys of eight eMudhra intermediate CAs could be calculated, so Chrome, Firefox, Edge and Safari have already removed the emSign ECC Root CA – G3 root, and from 16 November 2026 Windows starts removing every remaining eMudhra root, while Edge drops emSign Root CA – G1. The fix is to install a certificate from a different authority, such as a free Let's Encrypt certificate, and to update any CAA record that allows only emsign.com. Digital signature certificates (DSC) and eSign are not affected.
The short version, as of 15 November 2026:
- Check who issued your certificate. If the issuer or the chain mentions emSign or eMudhra, replace it now rather than at expiry.
- Certificates that chain to the G3 root already fail in Chrome, Firefox, Edge and Safari.
- Certificates that chain to the G1 root still work in Chrome and Firefox if they were issued by 16 November, but Edge and Windows begin rejecting them from 16 November, and eMudhra says Apple devices will reject all of them from 30 November.
- eMudhra is leaving the website certificate business and says it is moving customers to other providers at no charge.
- The DSC you use for GST, MCA or income tax filings, and eSign, are not part of this.
What happened to eMudhra's emSign SSL certificates?
eMudhra is an Indian certificate authority best known for digital signature certificates. Under the emSign name it also sold website (SSL/TLS) certificates that browsers around the world trusted.
On 17 October 2026 an independent researcher reported that eight eMudhra intermediate CA keys were weak. CERT-In's advisory CIAD-2026-0050 says the keys were generated with insufficient randomness, so they could be recovered from the public certificates. Six of the eight issued website certificates and two issued code-signing certificates. Anyone holding those keys could have created a certificate for any website that browsers would accept.
Google's Chrome team blocked the affected intermediates less than two hours after the report, and Mozilla did the same for Firefox in under three hours. eMudhra revoked all eight on 18 October. Google says no website certificate from those intermediates had been logged publicly before the block, and CERT-In said no malicious use had been confirmed as of 21 October. eMudhra's incident page traces the fault to its key ceremony of 30 April 2025, which produced a second, weak set of keys, and those weak keys were the ones published.
Browsers then removed the root that signed those intermediates, emSign ECC Root CA – G3. That root also carried genuine certificates: eMudhra says about 30,800 of them belonged to one US customer group, and The Hacker News reported that 99.9% came through InCommon, a US certificate service. On 22 October eMudhra said it would leave the global SSL/TLS business, and its 5 November update says it will stop issuing emSign website certificates. That is why its other main root, emSign Root CA – G1, is now being phased out as well.
In India, MeitY set up a special team to investigate and said the impact on Indian websites and applications "has been very limited" (AIR News, 22 October).
eMudhra distrust timeline: what breaks and when
Dates below are from Google, Mozilla, Microsoft, Apple, CERT-In and eMudhra, checked on 15 November 2026. Two of them, Firefox's G1 cut-off and Apple's 30 November date, come from eMudhra's own updates, because we could not find them on Mozilla's or Apple's pages.
| Date (2026) | What happened | What it means for websites |
|---|---|---|
| 17 October | Weak keys reported. Chrome and Firefox block the affected intermediates. | No effect on genuine sites: eMudhra says none of these intermediates had issued website certificates. |
| 18 October | eMudhra revokes all eight intermediates. | None for visitors. |
| 20 October | Firefox 158.0.1 and NSS 3.131.1 remove the G3 root. Windows blocks the affected CAs. | G3 certificates fail in Firefox. |
| 21–22 October | CERT-In advisory. MeitY sets up a special team. eMudhra announces its exit from SSL/TLS and starts moving customers to other certificate providers. | Time to plan a replacement. |
| 26–27 October | Windows (26th) and Edge (27th) remove six eMudhra G3 roots. Chrome removes emSign ECC Root CA – G3 (27th). | G3 certificates fail in Chrome and Edge. |
| 28 October | WordPress 7.1.4 updates its bundled root certificates because of the revocation. | Update WordPress. |
| By 9 November | Apple blocks the G3 root in Safari, Mail and apps. macOS 27.2.1 also removes five roots, including G1, for command-line tools. | G3 certificates fail on iPhone, iPad and Mac. |
| 16 November | Chrome 153 and later stops trusting G1 certificates first logged after 16 November, 23:59:59 UTC; eMudhra says Firefox applies the same cut-off. Windows begins removing the 10 remaining eMudhra roots, and Edge and WebView2 drop G1 and three other emSign roots. | No newly issued G1 certificate works in Chrome. Existing G1 certificates start failing in Edge and Windows apps. |
| 30 November | Apple removes emSign Root CA – G1, according to eMudhra. | Every G1 certificate fails on Apple devices, whatever its issue date. |
Microsoft's dates are from its security response post, updated on 12 November, and the full list of removed roots is in its Trusted Root Program announcements. Apple's are from its support note on the eMudhra CAs.
How to check if your SSL certificate is from emSign
Check every hostname you use (the bare domain, www, shop, mail, api), because each one can have its own certificate.
In your browser
Open your site, click the icon to the left of the address, and open the connection and certificate details. Look at "Issued by" and at the certificate hierarchy, which lists every certificate in the chain up to the root. If any line names emSign or eMudhra, that hostname is affected.
With OpenSSL
On Linux, a Mac or a VPS, or in Git Bash on Windows, run:
openssl s_client -connect example.com:443 -servername example.com -showcerts </dev/null
Each certificate in the chain shows a subject line (s:) and an issuer line (i:). A healthy Let's Encrypt chain looks like this:
0 s:CN=example.com
i:C=US, O=Let's Encrypt, CN=YE1
1 s:C=US, O=Let's Encrypt, CN=YE1
i:C=US, O=ISRG, CN=Root YE
To check quickly, filter for eMudhra's names, or print just the issuer and expiry date:
openssl s_client -connect example.com:443 -servername example.com -showcerts </dev/null 2>/dev/null | grep -iE "emsign|emudhra"
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -issuer -enddate
No output from the first command means none of the certificates your server sends mention emSign. Mail servers have certificates too: swap :443 for :993 (IMAP) or :465 (SMTP) and use your mail hostname.
With an online checker
- SSL Labs SSL Server Test is free and shows the certificate and its chain for any public site.
- crt.sh lists every certificate recorded in public Certificate Transparency logs for your domain, with an Issuer Name column. It is a good way to find a forgotten subdomain that still uses an emSign certificate.
Why does an emSign site show NET::ERR_CERT_AUTHORITY_INVALID?
Chrome shows NET::ERR_CERT_AUTHORITY_INVALID when a site's certificate is, in the words of Chromium's source code, "signed by an authority we don't trust". Once a browser drops an emSign root, every certificate under it lands in this group, even if it hasn't expired. A certificate that has itself been revoked shows NET::ERR_CERT_REVOKED instead. Firefox, Edge and Safari show their own "connection is not private" warnings.
Nothing a visitor does fixes this. If it's your site, replace the certificate. If you are visiting someone else's site, update your browser and operating system, and don't click past the warning: CERT-In's advisory says plainly, "Do not bypass certificate-validation warnings or disable certificate verification."
How to replace an emSign SSL certificate
- Check your CAA record first (next section). If it allows only emsign.com, every other authority will refuse to issue for your domain.
- Get a certificate from another authority. For most sites a free, domain-validated Let's Encrypt certificate is enough, and most hosts issue one automatically. If a client or tender needs an OV or EV certificate with your company name, buy one from another commercial CA. eMudhra says it is moving its website certificate customers to other providers at no charge, and names Sectigo as one alternative: existing CertiNext users request them in their account, and other customers write to support@emudhra.com.
- On your own VPS, Certbot gets and renews Let's Encrypt certificates. With Nginx:
Usesudo certbot --nginx -d example.com -d www.example.com sudo certbot renew --dry-run--apachefor Apache. Our guide to SSL certificates covers the basics. - Install the full chain, meaning your certificate plus the intermediate, then reload the web server. Certbot's Nginx and Apache plugins do this for you; if you install a certificate by hand, use the full-chain file your CA provides.
- Test on several devices, including an iPhone and Edge on Windows, because those are where G1 certificates fail first. Run SSL Labs again.
- Replace it everywhere it was installed: mail server, API endpoints, load balancers, CDN origins, and any mobile app that pins your certificate.
Servers and apps that keep their own list of trusted roots need updates too. CERT-In asks organisations to check language runtimes, container images, network appliances and similar. WordPress 7.1.4 updated the root certificates it bundles because of the eMudhra revocation (release notes), and the same release fixed 22 security issues; see our WordPress 7.1.4 update guide. A public tracker at emudhra.we-have-a-problem.com lists patched versions of operating systems, runtimes and tools, with test sites.
How to fix a CAA record that only allows emsign.com
A CAA record is a DNS record that names the certificate authorities allowed to issue certificates for your domain (see DNS records explained). emSign's own certification practice statement asked customers who use CAA to add emsign.com. If that is the only authority listed, Let's Encrypt, Sectigo and every other CA must refuse to issue, so your new certificate, or your host's automatic one, fails.
Check your record from a terminal, or on Google's dns.google page with the type set to CAA:
dig CAA example.com +short
If you see only emsign.com, change it at your DNS provider (wherever your nameservers point):
# Before: only eMudhra may issue
example.com. CAA 0 issue "emsign.com"
# After: Let's Encrypt may issue
example.com. CAA 0 issue "letsencrypt.org"
# Or, if you are moving to Sectigo
example.com. CAA 0 issue "sectigo.com"
example.com. CAA 0 issuewild "sectigo.com"
- Subdomains inherit the parent's record. Under RFC 8659, a CA checking www.example.com climbs to example.com if www has no CAA record of its own. Check any subdomain that has its own record too.
- Wildcard certificates follow
issuewildif it is present, so update both tags. - Deleting all CAA records also works: with none, any authority may issue.
- Remove emsign.com once the new certificate is in place, since eMudhra is stopping issuance anyway.
Is my DSC or eSign affected by the eMudhra incident?
No. eMudhra's update of 28 October says: "None of eMudhra's Global Digital Signature Certificate (DSC) or eSign business is affected by this incident." CERT-In's advisory says the issuance of digital signature certificates and eSign services is "not impacted", and MeitY said DSC and eSign services regulated by the Controller of Certifying Authorities (CCA) "remain completely unaffected". The incident concerns eMudhra's global website certificate business, not the DSCs issued under India's CCA framework.
So the USB token you use to sign GST returns, MCA forms or income tax filings doesn't need replacing because of this. Two code-signing intermediates were among the eight compromised keys, which matters to software publishers who sign apps, not to DSC holders.
What to do if your site is on HostEthical hosting
Every site on our web hosting gets a free Let's Encrypt certificate. It is requested automatically once your domain points to us and renewed automatically before it expires, so there is no emSign certificate to replace and nothing to buy. Two things can still block it: a CAA record that allows only emsign.com, or a domain that doesn't yet point to our servers. Our guide to connecting a domain to hosting covers the second.
On a Cloud VPS, which is unmanaged, the certificate is yours to manage: use Certbot as shown above and check that its renewal timer runs. Certificate lifetimes are also shrinking for every authority, to 100 days from March 2027, which our post on SSL certificate validity in 2026 explains.
Frequently asked questions
Why is my emSign SSL certificate not trusted?
In October 2026 the private keys of eight eMudhra intermediate CAs were found to be weak, so browsers removed eMudhra's emSign ECC Root CA G3 root. eMudhra then decided to leave the website certificate business, and its G1 root is being phased out too: Windows and Edge start dropping it from 16 November 2026, and eMudhra says Apple removes it on 30 November. Replace the certificate with one from another authority.
Is my DSC affected by the eMudhra incident?
No. eMudhra says none of its digital signature certificate or eSign business is affected, CERT-In's advisory says DSC and eSign issuance is not impacted, and MeitY says DSC and eSign services regulated by the Controller of Certifying Authorities remain completely unaffected. The problem was limited to eMudhra's global website certificate business, so the DSC token you use for GST, MCA or income tax filings does not need replacing because of it.
How do I check who issued my SSL certificate?
Click the icon to the left of the address bar, open the connection and certificate details, and read the Issued by field and the certificate hierarchy. From a terminal, run openssl s_client with -connect and -servername for your domain and read the issuer lines. Free online tools such as SSL Labs show the full chain. If any certificate in the chain mentions emSign or eMudhra, replace it.
What does NET::ERR_CERT_AUTHORITY_INVALID mean on an emSign website?
It is Chrome's error for a certificate signed by an authority the browser does not trust. After Chrome removed the emSign ECC Root CA G3 root on 27 October 2026, sites with certificates under that root started showing it, even if the certificate had not expired. Visitors cannot fix it and should not click past the warning; the site owner has to install a certificate from another authority.
Will eMudhra replace my SSL certificate for free?
eMudhra says it is moving its website certificate customers to other providers at no charge, and names Sectigo as one alternative. Existing CertiNext users can request one in their account, and other customers can write to eMudhra support. For most websites a free Let's Encrypt certificate is also enough. Before you request any new certificate, check that your CAA record does not allow only emsign.com.