Root certificate · Certum
Certum Trusted Network CA 2
Certum Trusted Network CA 2 is a root CA certificate operated by Certum (RSA 4096, valid until 2046-10-06, SHA-256 B676F2ED). 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 | — | No |
| Mozilla | Included Included | Yes | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | No |
Mozilla treats it as an EV root for policy OID 1.2.616.1.113527.2.5.1.1.
Included Chrome
- Status
- Included
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.23 / Firefox 46
- Inclusion bug
- #999378
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth, emailProtection
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client Authentication, Code 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
- Asseco Data Systems S.A.
- Subject
- CN=Certum Trusted Network CA 2,OU=Certum Certification Authority,O=Unizeto Technologies S.A.,C=PL
- SHA-256
B676F2EDDAE8775CD36CB0F63CD1D4603961F49E6265BA013A2F0307B6D0B804- SHA-1 (Windows thumbprint)
D3DD483E2BBF4C05E8AF10F5FA7626CFD3DC3092- SPKI SHA-256
6B3B57E9EC88D1BB3D01637FF33C7698B3C9758255E9F01EA9178F3E7F3B2B52- Valid from
- 2011-10-06
- Expires
- 2046-10-06
- Key
- RSA 4096
- Signature algorithm
- sha512WithRSAEncryption
- Serial number
21D6D04A4F250FC93237FCAA5E128DE9- Country
- PL
- Trust bits (CCADB)
- Server Authentication, Client Authentication, Code Signing, Secure Email
- 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-ctnca2.certificates.certum.pl· expired:https://expired-certum-ctnca2.certificates.certum.pl· revoked:https://revoked-certum-ctnca2.certificates.certum.pl - CCADB record
- A000815
- PEM
- certum-trusted-network-ca-2.pem
Intermediate CAs issued by this root
The CCADB lists 12 intermediate CA certificates signed directly by Certum Trusted Network CA 2: 11 currently valid, 0 expired and 1 revoked (revoked includes those whose parent was revoked).
Showing 12 of 12: 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 |
|---|---|---|---|
| IKARUS mail.security SMIME G1 R36 CA | Asseco Data Systems S.A. | 2036-04-23 | Valid |
| Certum SMIME G1 R36 CA 2 | Asseco Data Systems S.A. | 2036-02-21 | Valid |
| Certum SMIME G1 R36 CA | Asseco Data Systems S.A. | 2036-02-06 | Valid |
| Onmime SMIME G1 R36 CA | Asseco Data Systems S.A. | 2036-01-30 | Valid |
| WoTrus Code Signing 2021 CA | Asseco Data Systems S.A. | 2027-05-18 | Valid |
| Certum Timestamping 2021 CA | Asseco Data Systems S.A. | 2036-05-18 | Valid |
| Certum Extended Validation Code Signing 2021 CA | Asseco Data Systems S.A. | 2036-05-18 | Valid |
| Certum Code Signing 2021 CA | Asseco Data Systems S.A. | 2036-05-18 | Valid |
| Certum Extended Validation CA | Asseco Data Systems S.A. | 2028-01-24 | Valid |
| Certum Class I CA | Asseco Data Systems S.A. | 2028-01-24 | Valid |
| Certum Code Signing CA | Asseco Data Systems S.A. | 2028-01-24 | Valid |
| Certum Trusted Network CA 2 → Certum Trusted Network CA 2 | Asseco Data Systems S.A. | 2046-10-06 | Revoked |
Cross-signed versions
1 certificate(s) in the CCADB have the same subject and public key as Certum Trusted Network CA 2 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 2, can still build a chain.
| Signed by | CA owner | Expires | Status |
|---|---|---|---|
| Certum Trusted Network CA crt.sh | Asseco Data Systems S.A. | 2029-09-17 | Valid |
CRL and OCSP addresses
In the root certificate
Certum Trusted Network CA 2 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.certum.pl/ctnca2.crlhttp://subca.crl.certum.pl/ctnca2.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 11 valid intermediates signed by Certum Trusted Network CA 2; the number in brackets is how many of them use each address.
- CRL:
http://crl.certum.pl/ctnca2.crl(7) - CRL:
http://subca.crl.certum.pl/ctnca2.crl(4) - OCSP:
http://subca.ocsp-certum.com(11)
What happens when it expires
Certum Trusted Network CA 2 is valid until 2046-10-06, about 19.9 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 Certum Trusted Network CA 2 by common name (Certum Trusted Network CA 2) 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 2" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: B676F2EDDAE8775CD36CB0F63CD1D4603961F49E6265BA013A2F0307B6D0B804
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 D3DD483E2BBF4C05E8AF10F5FA7626CFD3DC3092
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 2"
# 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 2"
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 "B6:76:F2:ED:DA:E8:77:5C:D3:6C:B0:F6:3C:D1:D4:60:39:61:F4:9E:62:65:BA:01:3A:2F:03:07:B6:D0:B8:04"
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 2.
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 certum-trusted-network-ca-2.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=B6:76:F2:ED:DA:E8:77:5C:D3:6C:B0:F6:3C:D1:D4:60:39:61:F4:9E:62:65:BA:01:3A:2F:03:07:B6:D0:B8:04
FAQ
Is Certum Trusted Network CA 2 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.
When does Certum Trusted Network CA 2 expire?
On 2046-10-06, about 19.9 years after the 2026-11-10 data snapshot.
How many intermediate certificates has Certum Trusted Network CA 2 issued?
The CCADB lists 12: 11 valid, 0 expired and 1 revoked. The newest valid one is IKARUS mail.security SMIME G1 R36 CA, valid until 2036-04-23.
Is Certum Trusted Network CA 2 cross-signed?
Yes. The CCADB has 1 cross-certificate(s) with its subject and key, signed by Certum Trusted Network CA; 1 of them are still valid.
Other roots from Certum
- Certum EC-384 CA ECDSA P-384 · 2043-03-26
- Certum TLS ECC Root CA ECDSA P-384 · 2048-01-26
- Certum TLS RSA Root CA RSA 4096 · 2048-01-26
- Certum Trusted Network CA RSA 2048 · 2029-12-31
- Certum Trusted Root CA RSA 4096 · 2043-03-16
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