Root certificate · Certum

Certum Trusted Network CA

Certum Trusted Network CA is a root CA certificate operated by Certum (RSA 2048, valid until 2029-12-31, SHA-256 5C58468D). As of the latest CCADB data it is trusted for TLS server authentication by 4 of 4 major root stores: Chrome, Mozilla, Apple, Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeIncluded IncludedYes2026-09-30Yes
MozillaIncluded IncludedYes—No
AppleIncluded IncludedYes—No
MicrosoftIncluded IncludedYes—No

Chrome stops trusting TLS certificates under this root whose SCTs are dated after 2026-09-30 (sct_not_after). Mozilla treats it as an EV root for policy OID 1.2.616.1.113527.2.5.1.1.

Included Chrome

Status
Included
Distrust for TLS after
2026-09-30

Included Mozilla

Status
Included
Trust bits
Websites, Email
EV policy OIDs
1.2.616.1.113527.2.5.1.1
First included in
NSS 3.12.10 / Firefox 6.0
Inclusion bug
#532377

Included Apple

Status
Included
Trust bits
serverAuth, clientAuth, emailProtection

Included Microsoft

Status
Included
Trusted EKUs
Server Authentication, Client Authentication, Code Signing, Encrypting File System, IP Security Tunnel Termination, IP Security User, 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
Asseco Data Systems S.A.
Subject
CN=Certum Trusted Network CA,OU=Certum Certification Authority,O=Unizeto Technologies S.A.,C=PL
SHA-256
5C58468D55F58E497E743982D2B50010B6D165374ACF83A7D4A32DB768C4408E
SHA-1 (Windows thumbprint)
07E032E020B72C3F192F0628A2593A19A70F069E
SPKI SHA-256
AA2630A7B617B04D0A294BAB7A8CAAA5016E6DBE604837A83A85719FAB667EB5
Valid from
2008-10-22
Expires
2029-12-31
Key
RSA 2048
Signature algorithm
sha1WithRSAEncryption
Serial number
444C0
Country
PL
Trust bits (CCADB)
Server Authentication, Client Authentication, Code Signing, Secure Email, Encrypting File System, Time Stamping, IP Security Tunnel Termination, IP Security User
EV policy OIDs (CCADB)
1.2.616.1.113527.2.5.1.1, 2.23.140.1.1, 2.23.140.1.3, 1.2.616.1.113527.2.5.1.7 · TLS EV capable: Yes
Test websites
valid: https://valid-certum-ctnca.certificates.certum.pl · expired: https://expired-certum-ctnca.certificates.certum.pl · revoked: https://revoked-certum-ctnca.certificates.certum.pl
CCADB record
A000102
PEM
certum-trusted-network-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 46 intermediate CA certificates signed directly by Certum Trusted Network CA: 28 currently valid, 9 expired and 9 revoked (revoked includes those whose parent was revoked).

Showing 20 of 46: 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
Certum TLS ECC Root CA → Certum TLS ECC Root CA Asseco Data Systems S.A.2029-12-30Valid
Certum TLS RSA Root CA → Certum TLS RSA Root CA Asseco Data Systems S.A.2029-12-30Valid
Certum KWT G1 R29 CA Asseco Data Systems S.A.2029-12-20Valid
TrustAsia TLS ECC Root CA → TrustAsia TLS ECC Root CA TrustAsia Technologies, Inc.2029-01-14Valid
TrustAsia TLS RSA Root CA → TrustAsia TLS RSA Root CA TrustAsia Technologies, Inc.2029-01-14Valid
UCA Global G2 Root → UCA Global G2 Root Shanghai Electronic Certification Authority Co., Ltd.2029-01-06Valid
UCA Global G2 Root → UCA Global G2 Root Shanghai Electronic Certification Authority Co., Ltd.2029-01-06Valid
Certum Trusted Root CA → Certum Trusted Root CA Asseco Data Systems S.A.2028-09-19Valid
Certum EC-384 CA → Certum EC-384 CA Asseco Data Systems S.A.2028-09-19Valid
Root Networks CA Asseco Data Systems S.A.2028-09-09Valid
SSL Secure Site CA Asseco Data Systems S.A.2027-09-28Valid
Xcc Trust DV SSL CA Asseco Data Systems S.A.2027-06-30Valid
Xcc Trust OV SSL CA Asseco Data Systems S.A.2027-06-30Valid
Certum Trusted Network CA 2 → Certum Trusted Network CA 2 Asseco Data Systems S.A.2029-09-17Valid
WoTrus OV SSL CA Asseco Data Systems S.A.2027-05-18Valid
WoTrus EV SSL CA Asseco Data Systems S.A.2027-05-18Valid
WoTrus DV SSL CA Asseco Data Systems S.A.2027-05-18Valid
WoTrus Code Signing CA Asseco Data Systems S.A.2027-05-18Valid
WoSign DV SSL CA Asseco Data Systems S.A.2027-05-18Valid
WoSign EV SSL CA Asseco Data Systems S.A.2026-11-10Valid

Cross-signed versions

3 certificate(s) in the CCADB have the same subject and public key as Certum Trusted Network CA but a different issuer. A server can send one of them so that clients which trust the issuing root, but not Certum Trusted Network CA, can still build a chain.

Signed byCA ownerExpiresStatus
Certum CA crt.sh Asseco Data Systems S.A.2027-06-10Valid
Certum CA crt.sh Asseco Data Systems S.A.2025-12-30Revoked
Certum CA crt.sh Asseco Data Systems S.A.2025-12-30Expired

CRL and OCSP addresses

In the root certificate

Certum Trusted Network CA 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://certum-crl.wt.trustasia.com/ctnca.crl
  • http://certum.crl.sheca.com/ctnca.crl
  • http://crl.certum.pl/ctnca.crl
  • http://sslcom.crl.certum.pl/ctnca.crl
  • http://subca.crl.certum.pl/ctnca.crl
  • http://trustasia.crl.certum.pl/ctnca.crl

Used by the intermediates it issued

Addresses found in the CRL Distribution Points and OCSP fields of the 28 valid intermediates signed by Certum Trusted Network CA; the number in brackets is how many of them use each address.

  • CRL: http://crl.certum.pl/ctnca.crl (15)
  • CRL: http://subca.crl.certum.pl/ctnca.crl (11)
  • CRL: http://certum-crl.wt.trustasia.com/ctnca.crl (2)
  • CRL: http://certum.crl.sheca.com/ctnca.crl (2)
  • CRL: http://trustasia.crl.certum.pl/ctnca.crl (2)
  • OCSP: http://subca.ocsp-certum.com (28)

What happens when it expires

Certum Trusted Network CA is valid until 2029-12-31, about 3.1 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-09-30.

Check whether your device trusts it

Each platform keeps its own root store. The commands below look up Certum Trusted Network CA by common name (Certum Trusted Network CA) 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 "Certum Trusted Network CA" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 5C58468D55F58E497E743982D2B50010B6D165374ACF83A7D4A32DB768C4408E

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 07E032E020B72C3F192F0628A2593A19A70F069E

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

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 "5C:58:46:8D:55:F5:8E:49:7E:74:39:82:D2:B5:00:10:B6:D1:65:37:4A:CF:83:A7:D4:A3:2D:B7:68:C4:40:8E"

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 Unizeto Technologies S.A. → Certum Trusted Network CA.

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 certum-trusted-network-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=5C:58:46:8D:55:F5:8E:49:7E:74:39:82:D2:B5:00:10:B6:D1:65:37:4A:CF:83:A7:D4:A3:2D:B7:68:C4:40:8E

FAQ

Is Certum Trusted Network CA 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-09-30.

When does Certum Trusted Network CA expire?

On 2029-12-31, about 3.1 years after the 2026-11-10 data snapshot.

How many intermediate certificates has Certum Trusted Network CA issued?

The CCADB lists 46: 28 valid, 9 expired and 9 revoked. The newest valid one is Certum TLS ECC Root CA, valid until 2029-12-30.

Is Certum Trusted Network CA cross-signed?

Yes. The CCADB has 3 cross-certificate(s) with its subject and key, signed by Certum CA; 1 of them are still valid.

Other roots from Certum

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