Root certificate · eMudhra
emSign Root CA - G1
emSign Root CA - G1 is a root CA certificate operated by eMudhra (RSA 2048, valid until 2043-02-18, SHA-256 40F6AF03). As of the latest CCADB data it is trusted for TLS server authentication by 4 of 4 major root stores: Chrome, Mozilla, Apple, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Included Included | Yes | 2026-11-16 | Yes |
| Mozilla | Included Included | Yes | 2026-11-16 | Yes |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | No |
Chrome stops trusting TLS certificates under this root whose SCTs are dated after 2026-11-16 (sct_not_after). Mozilla stops trusting TLS certificates from this root issued after 2026-11-16. Mozilla treats it as an EV root for policy OID 2.23.140.1.1.
Included Chrome
- Status
- Included
- Distrust for TLS after
- 2026-11-16
Included Mozilla
- Status
- Included
- Distrust for TLS after
- 2026-11-16
- Trust bits
- Websites
- EV policy OIDs
- 2.23.140.1.1
- First included in
- NSS 3.43 / Firefox 67
- Inclusion bug
- #1442337
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth, emailProtection
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client Authentication, Document Signing, Secure Email
"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 Root CA - G1,O=eMudhra Technologies Limited,OU=emSign PKI,C=IN
- SHA-256
40F6AF0346A99AA1CD1D555A4E9CCE62C7F9634603EE406615833DC8C8D00367- SHA-1 (Windows thumbprint)
8AC7AD8F73AC4EC1B5754DA540F4FCCF7CB58E8C- SPKI SHA-256
376A1A7082A593DCCC20D561D119E9AB8D30F11CC321D0A37FA41F0DF284E01C- Valid from
- 2018-02-18
- Expires
- 2043-02-18
- Key
- RSA 2048
- Signature algorithm
- sha256WithRSAEncryption
- Serial number
31F5E4620C6C58EDD6D8- Country
- IN
- Trust bits (CCADB)
- Server Authentication, Client Authentication, Document Signing, Secure Email
- EV policy OIDs (CCADB)
- 2.23.140.1.1 · TLS EV capable: Yes
- Test websites
- valid:
https://testevg1.emSign.com· expired:https://testevg1e.emsign.com· revoked:https://testevg1r.emsign.com - CCADB record
- A005754
- PEM
- emudhra-emsign-root-ca-g1.pem
Intermediate CAs issued by this root
The CCADB lists 10 intermediate CA certificates signed directly by emSign Root CA - G1: 3 currently valid, 0 expired and 7 revoked (revoked includes those whose parent was revoked).
Showing 10 of 10: 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 - G1 → emSign Root TLS CA - G1 | eMudhra Technologies Limited | 2039-07-09 | Valid |
| emSign SSL CA - G1 | eMudhra Technologies Limited | 2033-02-18 | Valid |
| emSign EV SSL CA - G1 | eMudhra Technologies Limited | 2033-02-18 | Valid |
| emSign Root SMIME CA - G1 | eMudhra Technologies Limited | 2039-07-09 | Revoked |
| emSign Root Client Auth CA - G1 | eMudhra Technologies Limited | 2039-07-09 | Revoked |
| emSign SMIME CA - G1 | eMudhra Technologies Limited | 2038-08-22 | Revoked |
| emSign Class 1 CA - G1 | eMudhra Technologies Limited | 2033-02-18 | Revoked |
| emSign Class 2 CA - G1 | eMudhra Technologies Limited | 2033-02-18 | Revoked |
| emSign Device CA - G1 | eMudhra Technologies Limited | 2033-02-18 | Revoked |
| emSign Class 3 CA - G1 | eMudhra Technologies Limited | 2033-02-18 | Revoked |
Cross-signed versions
No certificate in the CCADB has the same subject and public key as emSign Root CA - G1 with a different issuer, so a client has to carry emSign Root CA - G1 itself in its root store to trust it.
CRL and OCSP addresses
In the root certificate
emSign Root CA - G1 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?RootCAG1.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 Root CA - G1; the number in brackets is how many of them use each address.
- CRL:
http://crl.emsign.com?RootCAG1.crl(3) - OCSP:
http://ocsp.emsign.com(3)
What happens when it expires
emSign Root CA - G1 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. Root programs can stop trusting it before it expires: Chrome 2026-11-16, Mozilla 2026-11-16.
Check whether your device trusts it
Each platform keeps its own root store. The commands below look up emSign Root CA - G1 by common name (emSign Root CA - G1) 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 Root CA - G1" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 40F6AF0346A99AA1CD1D555A4E9CCE62C7F9634603EE406615833DC8C8D00367
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 8AC7AD8F73AC4EC1B5754DA540F4FCCF7CB58E8C
Linux (ca-certificates follows Mozilla: Included · Trusted for TLS)
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 Root CA - G1"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "emSign Root CA - G1"
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 "40:F6:AF:03:46:A9:9A:A1:CD:1D:55:5A:4E:9C:CE:62:C7:F9:63:46:03:EE:40:66:15:83:3D:C8:C8:D0:03:67"
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 Root CA - G1.
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-root-ca-g1.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=40:F6:AF:03:46:A9:9A:A1:CD:1D:55:5A:4E:9C:CE:62:C7:F9:63:46:03:EE:40:66:15:83:3D:C8:C8:D0:03:67
FAQ
Is emSign Root CA - G1 trusted by Chrome, Firefox, Safari and Windows?
Yes. As of 2026-11-10, Chrome, Mozilla (Firefox), Apple (Safari) and Microsoft (Windows) all trust it for TLS server authentication. Distrust-after dates already set: Chrome 2026-11-16, Mozilla 2026-11-16.
When does emSign Root CA - G1 expire?
On 2043-02-18, about 16.3 years after the 2026-11-10 data snapshot.
How many intermediate certificates has emSign Root CA - G1 issued?
The CCADB lists 10: 3 valid, 0 expired and 7 revoked. The newest valid one is emSign Root TLS CA - G1, valid until 2039-07-09.
Is emSign Root CA - G1 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 ECC Root CA - G3 ECDSA P-384 · 2043-02-18
- emSign Root CA - C1 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