Root certificate · eMudhra

emSign Root CA - C1

emSign Root CA - C1 is a root CA certificate operated by eMudhra (RSA 2048, valid until 2043-02-18, SHA-256 125609AA). As of the latest CCADB data it is trusted for TLS server authentication by 1 of 4 major root stores: Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeRemoved RemovedNo—No
MozillaRemoved RemovedNo—No
AppleNot included Not includedNo—No
MicrosoftIncluded IncludedYes—No

The CCADB lists EV policy OID 2.23.140.1.1 for this root, but Mozilla does not mark it as EV-enabled.

Removed Chrome

Status
Removed

Removed Mozilla

Status
Removed

Not included Apple

Status
Not included

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 - C1,O=eMudhra Inc,OU=emSign PKI,C=US
SHA-256
125609AA301DA0A249B97A8239CB6A34216F44DCAC9F3954B14292F2E8C8608F
SHA-1 (Windows thumbprint)
E72EF1DFFCB20928CF5DD4D56737B151CB864F01
SPKI SHA-256
B7408B4D2BE0238BA37004DD34E276C6019BD2F24C9DB7D4980F5F6C359A4BCC
Valid from
2018-02-18
Expires
2043-02-18
Key
RSA 2048
Signature algorithm
sha256WithRSAEncryption
Serial number
AECF00BAC4CF32F843B2
Country
US
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://testevc1.emsign.com · expired: https://testevc1e.emsign.com · revoked: https://testevc1r.emsign.com
CCADB record
A005757
PEM
emudhra-emsign-root-ca-c1.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 16 intermediate CA certificates signed directly by emSign Root CA - C1: 16 currently valid, 0 expired and 0 revoked (revoked includes those whose parent was revoked).

Showing 16 of 16: 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.

IntermediateOperated byExpiresStatus
UAE QTSP Qualified eSeal CA LP eMudhra Technologies Limited2036-08-05Valid
UAE QTSP Qualified eSignature CA NP-QSCD eMudhra Technologies Limited2036-08-05Valid
UAE QTSP Device and Management CA eMudhra Technologies Limited2036-08-05Valid
UAE QTSP Qualified eSignature CA (NP) eMudhra Technologies Limited2036-08-05Valid
UAE QTSP Qualified eSeal CA LP-QSCD eMudhra Technologies Limited2036-08-05Valid
UAE QTSP TSA Issuing CA eMudhra Technologies Limited2036-08-05Valid
UAE QTSP Validation Service CA eMudhra Technologies Limited2036-08-05Valid
UAE QTSP Advanced CA eMudhra Technologies Limited2036-08-05Valid
Soft-Net Secure Signing CA - C1 eMudhra Technologies Limited2035-08-12Valid
emSign Time Stamping CA - C1 eMudhra Technologies Limited2035-08-12Valid
emSign SSL CA - C1 eMudhra Technologies Limited2033-02-18Valid
emSign EV SSL CA - C1 eMudhra Technologies Limited2033-02-18Valid
emSign Device CA - C1 eMudhra Technologies Limited2033-02-18Valid
emSign Class 3 CA - C1 eMudhra Technologies Limited2033-02-18Valid
emSign Class 1 CA - C1 eMudhra Technologies Limited2033-02-18Valid
emSign Class 2 CA - C1 eMudhra Technologies Limited2033-02-18Valid

Cross-signed versions

No certificate in the CCADB has the same subject and public key as emSign Root CA - C1 with a different issuer, so a client has to carry emSign Root CA - C1 itself in its root store to trust it.

CRL and OCSP addresses

In the root certificate

emSign Root CA - C1 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?RootCAC1.crl

Used by the intermediates it issued

Addresses found in the CRL Distribution Points and OCSP fields of the 16 valid intermediates signed by emSign Root CA - C1; the number in brackets is how many of them use each address.

  • CRL: http://crl.emsign.com?RootCAC1.crl (16)
  • OCSP: http://ocsp.emsign.com (16)

What happens when it expires

emSign Root CA - C1 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 Root CA - C1 by common name (emSign Root CA - C1) 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 CA - C1" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 125609AA301DA0A249B97A8239CB6A34216F44DCAC9F3954B14292F2E8C8608F

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 E72EF1DFFCB20928CF5DD4D56737B151CB864F01

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 Root CA - C1"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "emSign Root CA - C1"

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 "12:56:09:AA:30:1D:A0:A2:49:B9:7A:82:39:CB:6A:34:21:6F:44:DC:AC:9F:39:54:B1:42:92:F2:E8:C8:60:8F"

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 Inc → emSign Root CA - C1.

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.

Download PEM

# 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-c1.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=12:56:09:AA:30:1D:A0:A2:49:B9:7A:82:39:CB:6A:34:21:6F:44:DC:AC:9F:39:54:B1:42:92:F2:E8:C8:60:8F

FAQ

Is emSign Root CA - C1 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 CA - C1 expire?

On 2043-02-18, about 16.3 years after the 2026-11-10 data snapshot.

How many intermediate certificates has emSign Root CA - C1 issued?

The CCADB lists 16: 16 valid, 0 expired and 0 revoked. The newest valid one is UAE QTSP Qualified eSeal CA LP, valid until 2036-08-05.

Is emSign Root CA - C1 cross-signed?

No. The CCADB has no certificate with the same subject and public key signed by another CA.

Other roots from eMudhra

Sources

  1. CCADB — Resources (TLS Server Authentication report, All Included Root Certificate Trust Bit Settings)
  2. CCADB — All Certificate Information (root and intermediate), CSV V5
  3. CCADB — Mozilla Included CA Certificate Report
  4. CCADB — Chrome / Mozilla / Apple / Microsoft TLS Server Authentication CSV