Root certificate · eMudhra
emSign Root TLS CA - G1
emSign Root TLS CA - G1 is a root CA certificate operated by eMudhra (RSA 4096, valid until 2049-02-07, SHA-256 CEF71E70). As of the latest CCADB data it is trusted for TLS server authentication by 1 of 4 major root stores: Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Not included Not included | No | — | No |
| Mozilla | Not included Not included | No | — | No |
| Apple | Not included Not included | No | — | No |
| Microsoft | Included Included | Yes | — | No |
The CCADB lists no EV policy OID for emSign Root TLS CA - G1.
Not included Chrome
- Status
- Not included
Not included Mozilla
- Status
- Not included
Not included Apple
- Status
- Not included
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication
"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 TLS CA - G1,O=eMudhra Technologies Limited,C=IN
- SHA-256
CEF71E70B7C29ADDF6C30CD19E614B38FD5F02A435A0EEDDD0087E183D101A51- SHA-1 (Windows thumbprint)
A670CBDE482554129CAD3E1C4B1372F669F75CAD- SPKI SHA-256
ECE28E35289CE8621C72407949E5050052AD4607CC332EAF9B546029AACBFB7A- Valid from
- 2024-02-08
- Expires
- 2049-02-07
- Key
- RSA 4096
- Signature algorithm
- sha384WithRSAEncryption
- Serial number
2A27D4E346AEF4E4F04678B5BB6D9EE- Country
- IN
- Trust bits (CCADB)
- Server Authentication
- EV policy OIDs (CCADB)
- not EV-enabled · TLS EV capable: No
- Test websites
- valid:
https://testevg1-cr.emsign.com· expired:https://testevg1e-cr.emsign.com· revoked:https://testevg1r-cr.emsign.com - CCADB record
- A011505
- PEM
- emudhra-emsign-root-tls-ca-g1.pem
Intermediate CAs issued by this root
The CCADB lists 17 intermediate CA certificates signed directly by emSign Root TLS CA - G1: 8 currently valid, 0 expired and 9 revoked (revoked includes those whose parent was revoked).
Showing 17 of 17: 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 |
|---|---|---|---|
| InCommon RSA IGTF Server CA 4 | eMudhra Technologies Limited | 2029-04-07 | Valid |
| InCommon Intermediate CA - OVG2C | eMudhra Technologies Limited | 2029-04-07 | Valid |
| InCommon Intermediate CA - EVG2C | eMudhra Technologies Limited | 2029-04-07 | Valid |
| InCommon Intermediate CA - DVG2C | eMudhra Technologies Limited | 2029-04-07 | Valid |
| EM EV TLS CA - G2A-1 | eMudhra Technologies Limited | 2040-05-28 | Valid |
| EM DV TLS CA - G2A-1 | eMudhra Technologies Limited | 2040-05-28 | Valid |
| EM OV TLS CA - G2A-1 | eMudhra Technologies Limited | 2040-05-28 | Valid |
| emSign TLS CA - G1 | eMudhra Technologies Limited | 2039-07-08 | Valid |
| EM OV TLS CA - G2A | eMudhra Technologies Limited | 2040-04-28 | Revoked |
| EM EV TLS CA - G2B | eMudhra Technologies Limited | 2040-04-28 | Revoked |
| EM OV TLS CA - G2C | eMudhra Technologies Limited | 2040-04-28 | Revoked |
| EM DV TLS CA - G2A | eMudhra Technologies Limited | 2040-04-28 | Revoked |
| EM EV TLS CA - G2C | eMudhra Technologies Limited | 2040-04-28 | Revoked |
| EM DV TLS CA - G2B | eMudhra Technologies Limited | 2040-04-28 | Revoked |
| EM OV TLS CA - G2B | eMudhra Technologies Limited | 2040-04-28 | Revoked |
| EM EV TLS CA - G2A | eMudhra Technologies Limited | 2040-04-28 | Revoked |
| EM DV TLS CA - G2C | eMudhra Technologies Limited | 2040-04-28 | Revoked |
Cross-signed versions
1 certificate(s) in the CCADB have the same subject and public key as emSign Root TLS CA - G1 but a different issuer. A server can send one of them so that clients which trust the issuing root, but not emSign Root TLS CA - G1, can still build a chain.
| Signed by | CA owner | Expires | Status |
|---|---|---|---|
| emSign Root CA - G1 crt.sh | eMudhra Technologies Limited | 2039-07-09 | Valid |
CRL and OCSP addresses
In the root certificate
emSign Root TLS 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/?roottlscag1.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 8 valid intermediates signed by emSign Root TLS CA - G1; the number in brackets is how many of them use each address.
- CRL:
http://crl.emsign.com/?roottlscag1.crl(8) - OCSP:
http://ocsp-c.emsign.com(4) - OCSP:
http://ocsp-a.emsign.com(3) - OCSP:
http://ocsp.emsign.com(1)
What happens when it expires
emSign Root TLS CA - G1 is valid until 2049-02-07, about 22.2 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 Root TLS CA - G1 by common name (emSign Root TLS 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: Not included)
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 TLS CA - G1" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: CEF71E70B7C29ADDF6C30CD19E614B38FD5F02A435A0EEDDD0087E183D101A51Windows (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 A670CBDE482554129CAD3E1C4B1372F669F75CADLinux (ca-certificates follows Mozilla: Not included)
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 TLS 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 TLS 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 "CE:F7:1E:70:B7:C2:9A:DD:F6:C3:0C:D1:9E:61:4B:38:FD:5F:02:A4:35:A0:EE:DD:D0:08:7E:18:3D:10:1A:51"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 TLS 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-tls-ca-g1.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=CE:F7:1E:70:B7:C2:9A:DD:F6:C3:0C:D1:9E:61:4B:38:FD:5F:02:A4:35:A0:EE:DD:D0:08:7E:18:3D:10:1A:51FAQ
Is emSign Root TLS CA - G1 trusted by Chrome, Firefox, Safari and Windows?
As of 2026-11-10, Microsoft trust it for TLS server authentication; Chrome, Mozilla, Apple do not.
When does emSign Root TLS CA - G1 expire?
On 2049-02-07, about 22.2 years after the 2026-11-10 data snapshot.
How many intermediate certificates has emSign Root TLS CA - G1 issued?
The CCADB lists 17: 8 valid, 0 expired and 9 revoked. The newest valid one is InCommon RSA IGTF Server CA 4, valid until 2029-04-07.
Is emSign Root TLS CA - G1 cross-signed?
Yes. The CCADB has 1 cross-certificate(s) with its subject and key, signed by emSign Root CA - G1; 1 of them are still valid.
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 CA - G1 RSA 2048 · 2043-02-18
- 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