Root certificate · eMudhra
emSign ECC Root CA - G3
emSign ECC Root CA - G3 is a root CA certificate operated by eMudhra (ECDSA P-384, valid until 2043-02-18, SHA-256 86A1ECBA). As of the latest CCADB data it is trusted for TLS server authentication by 2 of 4 major root stores: Apple, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Blocked Blocked | No | — | No |
| Mozilla | Removed Removed | No | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | No |
The CCADB lists EV policy OID 2.23.140.1.1, 2.23.140.1.3 for this root, but Mozilla does not mark it as EV-enabled.
Blocked Chrome
- Status
- Blocked
Removed Mozilla
- Status
- Removed
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth, emailProtection
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client Authentication, Code Signing, Document Signing, Secure Email, Time Stamping
"Trusted for TLS" means the store includes the root with the server-authentication trust bit (Mozilla "Websites", Apple serverAuth, Microsoft Server Authentication EKU). Microsoft "NotBefore" means only certificates issued before a cutoff date are still trusted. "Constrained" means the store applies extra restrictions.
Details
- CA owner
- eMudhra Technologies Limited
- Subject
- CN=emSign ECC Root CA - G3,O=eMudhra Technologies Limited,OU=emSign PKI,C=IN
- SHA-256
86A1ECBA089C4A8D3BBE2734C612BA341D813E043CF9E8A862CD5C57A36BBE6B- SHA-1 (Windows thumbprint)
3043FA4FF257DCA0C380EE2E58EA78B23FE6BBC1- SPKI SHA-256
8D417DB2DD8BF5E3084D1E3F196D583849D81BDD4C00C70B9D39369E96B8C782- Valid from
- 2018-02-18
- Expires
- 2043-02-18
- Key
- ECDSA P-384
- Signature algorithm
- ecdsa-with-SHA384
- Serial number
3CF607A968700EDA8B84- Country
- IN
- Trust bits (CCADB)
- Server Authentication, Client Authentication, Code Signing, Document Signing, Secure Email, Time Stamping
- EV policy OIDs (CCADB)
- 2.23.140.1.1, 2.23.140.1.3 · TLS EV capable: Yes
- Test websites
- valid:
https://testevg3.emsign.com· expired:https://testevg3e.emsign.com· revoked:https://testevg3r.emsign.com - CCADB record
- A005756
- PEM
- emudhra-emsign-ecc-root-ca-g3.pem
Intermediate CAs issued by this root
The CCADB lists 15 intermediate CA certificates signed directly by emSign ECC Root CA - G3: 3 currently valid, 0 expired and 12 revoked (revoked includes those whose parent was revoked).
Showing 15 of 15: valid certificates first, newest first. Each name links to its crt.sh entry by SHA-256; an arrow marks a cross-certificate for another root on this site.
| Intermediate | Operated by | Expires | Status |
|---|---|---|---|
| emSign Root TLS CA - G3 → emSign Root TLS CA - G3 | eMudhra Technologies Limited | 2039-07-09 | Valid |
| emSign ECC SSL CA - G3 | eMudhra Technologies Limited | 2033-02-18 | Valid |
| emSign ECC EV SSL CA - G3 | eMudhra Technologies Limited | 2033-02-18 | Valid |
| emSign Root SMIME CA - G3 | eMudhra Technologies Limited | 2039-07-09 | Revoked |
| emSign Root TSA CA - G3 | eMudhra Technologies Limited | 2039-07-09 | Revoked |
| emSign Root CS CA - G3 | eMudhra Technologies Limited | 2039-07-09 | Revoked |
| emSign Root Client Auth CA - G3 | eMudhra Technologies Limited | 2039-07-09 | Revoked |
| emSign ECC SMIME CA - G3 | eMudhra Technologies Limited | 2038-08-22 | Revoked |
| emSign ECC Time stamping CA - G3 | eMudhra Technologies Limited | 2033-02-18 | Revoked |
| emSign ECC Class 1 CA - G3 | eMudhra Technologies Limited | 2033-02-18 | Revoked |
| emSign ECC Device CA - G3 | eMudhra Technologies Limited | 2033-02-18 | Revoked |
| emSign ECC Class 3 CA - G3 | eMudhra Technologies Limited | 2033-02-18 | Revoked |
| emSign ECC Class 2 CA - G3 | eMudhra Technologies Limited | 2033-02-18 | Revoked |
| emSign ECC CS CA - G3 | eMudhra Technologies Limited | 2033-02-18 | Revoked |
| emSign ECC EV CS CA - G3 | eMudhra Technologies Limited | 2033-02-18 | Revoked |
Cross-signed versions
No certificate in the CCADB has the same subject and public key as emSign ECC Root CA - G3 with a different issuer, so a client has to carry emSign ECC Root CA - G3 itself in its root store to trust it.
CRL and OCSP addresses
In the root certificate
emSign ECC Root CA - G3 itself contains no CRL Distribution Points and no OCSP (Authority Information Access) extension. That is normal for a root: clients trust it directly and do not check its own revocation status.
Full CRL this CA publishes (CCADB)
http://crl.emsign.com?RootCAG3.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 3 valid intermediates signed by emSign ECC Root CA - G3; the number in brackets is how many of them use each address.
- CRL:
http://crl.emsign.com?RootCAG3.crl(3) - OCSP:
http://ocsp.emsign.com(3)
What happens when it expires
emSign ECC Root CA - G3 is valid until 2043-02-18, about 16.3 years after this data snapshot (2026-11-10). From that day, browsers and operating systems that check trust-anchor expiry stop accepting chains that end at this root, so any certificate that can only chain to it fails validation. Android is a known exception: it does not enforce the expiry date of trust anchors.
Check whether your device trusts it
Each platform keeps its own root store. The commands below look up emSign ECC Root CA - G3 by common name (emSign ECC Root CA - G3) or fingerprint. The store status in each heading comes from the CCADB snapshot; your device can differ if it is out of date or managed by an administrator.
macOS (Apple store: Included · Trusted for TLS)
Search the system roots keychain by common name. -Z prints the SHA-256 hash, which must match the fingerprint on the last line.
security find-certificate -a -c "emSign ECC Root CA - G3" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 86A1ECBA089C4A8D3BBE2734C612BA341D813E043CF9E8A862CD5C57A36BBE6B
Windows (Microsoft store: Included · Trusted for TLS)
Windows identifies roots by SHA-1 thumbprint. It installs third-party roots on demand through Automatic Root Certificates Update, so "not found" can also mean the root has not been needed yet; certutil -generateSSTFromWU roots.sst downloads Microsoft's full list.
certutil -verifystore Root 3043FA4FF257DCA0C380EE2E58EA78B23FE6BBC1
Linux (ca-certificates follows Mozilla: Removed)
Debian, Ubuntu, Fedora and RHEL build their ca-certificates package from Mozilla's root store. Use trust list on p11-kit systems, or search the PEM bundle on Debian and Ubuntu.
# Fedora / RHEL / Arch (p11-kit)
trust list --filter=ca-anchors | grep -iF -A2 "emSign ECC Root CA - G3"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "emSign ECC Root CA - G3"
Java
Java ships its own cacerts keystore; JDK 9 and later accept -cacerts and the default store password is changeit. Search for the SHA-256 fingerprint in colon form.
keytool -list -cacerts -storepass changeit | grep -i "86:A1:EC:BA:08:9C:4A:8D:3B:BE:27:34:C6:12:BA:34:1D:81:3E:04:3C:F9:E8:A8:62:CD:5C:57:A3:6B:BE:6B"
Android
Android's system store is maintained by Google separately from the four CCADB stores above. Open Settings → Security & privacy → More security settings → Encryption & credentials → Trusted credentials → System (menu names vary by vendor and version) and look for eMudhra Technologies Limited → emSign ECC Root CA - G3.
Which root does my site chain to?
List the chain your server sends and compare the last issuer with this root; the fingerprint check confirms a local copy.
# show subject (s:) and issuer (i:) of every certificate the server sends
openssl s_client -connect example.com:443 -servername example.com -showcerts </dev/null 2>/dev/null \
| grep -E '^ *[0-9]+ s:|^ *i:'
# subject and SHA-256 fingerprint of the downloaded PEM file
openssl x509 -in emudhra-emsign-ecc-root-ca-g3.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=86:A1:EC:BA:08:9C:4A:8D:3B:BE:27:34:C6:12:BA:34:1D:81:3E:04:3C:F9:E8:A8:62:CD:5C:57:A3:6B:BE:6B
FAQ
Is emSign ECC Root CA - G3 trusted by Chrome, Firefox, Safari and Windows?
As of 2026-11-10, Apple, Microsoft trust it for TLS server authentication; Chrome, Mozilla do not.
When does emSign ECC Root CA - G3 expire?
On 2043-02-18, about 16.3 years after the 2026-11-10 data snapshot.
How many intermediate certificates has emSign ECC Root CA - G3 issued?
The CCADB lists 15: 3 valid, 0 expired and 12 revoked. The newest valid one is emSign Root TLS CA - G3, valid until 2039-07-09.
Is emSign ECC Root CA - G3 cross-signed?
No. The CCADB has no certificate with the same subject and public key signed by another CA.
Other roots from eMudhra
- emSign ECC Root CA - C3 ECDSA P-384 · 2043-02-18
- emSign Root CA - C1 RSA 2048 · 2043-02-18
- emSign Root CA - G1 RSA 2048 · 2043-02-18
- emSign Root TLS CA - G1 RSA 4096 · 2049-02-07
- emSign Root TLS CA - G3 ECDSA P-384 · 2049-02-07
Sources
- CCADB — Resources (TLS Server Authentication report, All Included Root Certificate Trust Bit Settings)
- CCADB — All Certificate Information (root and intermediate), CSV V5
- CCADB — Mozilla Included CA Certificate Report
- CCADB — Chrome / Mozilla / Apple / Microsoft TLS Server Authentication CSV