Root certificate · Certum
Certum Trusted Root CA
Certum Trusted Root CA is a root CA certificate operated by Certum (RSA 4096, valid until 2043-03-16, SHA-256 FE769657). 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 2.23.140.1.1.
Included Chrome
- Status
- Included
Included Mozilla
- Status
- Included
- Trust bits
- Websites, Email
- EV policy OIDs
- 2.23.140.1.1
- First included in
- NSS 3.66 / Firefox 90
- Inclusion bug
- #1598577
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth, emailProtection
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client Authentication, Code Signing, 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 Root CA,OU=Certum Certification Authority,O=Asseco Data Systems S.A.,C=PL
- SHA-256
FE7696573855773E37A95E7AD4D9CC96C30157C15D31765BA9B15704E1AE78FD- SHA-1 (Windows thumbprint)
C88344C018AE9FCCF187B78F22D1C5D74584BAE5- SPKI SHA-256
681DC482C296C8402C6EBB20E68309A3BC846523AE34B984A84EE697A3312DB7- Valid from
- 2018-03-16
- Expires
- 2043-03-16
- Key
- RSA 4096
- Signature algorithm
- sha512WithRSAEncryption
- Serial number
1EBF5950B8C980374C06F7EB554FB5ED- Country
- PL
- Trust bits (CCADB)
- Server Authentication, Client Authentication, Code Signing, Secure Email, Time Stamping
- EV policy OIDs (CCADB)
- 2.23.140.1.1 · TLS EV capable: Yes
- Test websites
- valid:
https://valid-ctrca.certificates.certum.pl/· expired:https://expired-ctrca.certificates.certum.pl/· revoked:https://revoked-ctrca.certificates.certum.pl/ - CCADB record
- A006709
- PEM
- certum-trusted-root-ca.pem
Intermediate CAs issued by this root
The CCADB lists 40 intermediate CA certificates signed directly by Certum Trusted Root CA: 39 currently valid, 0 expired and 1 revoked (revoked includes those whose parent was revoked).
Showing 20 of 40: 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 |
|---|---|---|---|
| AutonTrust PRO DV TLS G2 R31 CA | Asseco Data Systems S.A. | 2031-06-06 | Valid |
| Certum TLS RSA Root CA → Certum TLS RSA Root CA | Asseco Data Systems S.A. | 2036-04-15 | Valid |
| CNSSL OV TLS G2 R36 CA | Asseco Data Systems S.A. | 2036-01-30 | Valid |
| home pl DV TLS G2 R36 CA | Asseco Data Systems S.A. | 2036-01-02 | Valid |
| CNSSL DV TLS G2 R36 CA | Asseco Data Systems S.A. | 2036-01-02 | Valid |
| home pl OV TLS G2 R36 CA | Asseco Data Systems S.A. | 2036-01-02 | Valid |
| Certum Document Signing G2 R40 CA | Asseco Data Systems S.A. | 2040-06-03 | Valid |
| AnTrust OV SSL G2 R30 CA | Asseco Data Systems S.A. | 2030-06-06 | Valid |
| home pl DV TLS G2 R35 CA | Asseco Data Systems S.A. | 2035-05-16 | Valid |
| home pl OV TLS G2 R35 CA | Asseco Data Systems S.A. | 2035-05-16 | Valid |
| TrustAsia SMIME CA 2025 | Asseco Data Systems S.A. | 2035-01-03 | Valid |
| TrustAsia OV TLS RSA CA C5 | Asseco Data Systems S.A. | 2035-01-03 | Valid |
| TrustAsia EV TLS RSA CA C5 | Asseco Data Systems S.A. | 2035-01-03 | Valid |
| iTrust DV TLS CA | Asseco Data Systems S.A. | 2035-01-03 | Valid |
| 宝塔 DV TLS CA | Asseco Data Systems S.A. | 2035-01-03 | Valid |
| iTrust OV TLS CA | Asseco Data Systems S.A. | 2035-01-03 | Valid |
| TrustAsia DV TLS RSA CA C5 | Asseco Data Systems S.A. | 2035-01-03 | Valid |
| TLC OV TLS CA | Asseco Data Systems S.A. | 2034-12-05 | Valid |
| GeoSSL DV TLS CA | Asseco Data Systems S.A. | 2034-12-05 | Valid |
| TLC DV TLS CA | Asseco Data Systems S.A. | 2034-12-05 | Valid |
Cross-signed versions
1 certificate(s) in the CCADB have the same subject and public key as Certum Trusted Root CA but a different issuer. A server can send one of them so that clients which trust the issuing root, but not Certum Trusted Root CA, can still build a chain.
| Signed by | CA owner | Expires | Status |
|---|---|---|---|
| Certum Trusted Network CA crt.sh | Asseco Data Systems S.A. | 2028-09-19 | Valid |
CRL and OCSP addresses
In the root certificate
Certum Trusted Root 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://crl.certum.pl/ctrca.crlhttp://subca.crl.certum.pl/ctrca.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 39 valid intermediates signed by Certum Trusted Root CA; the number in brackets is how many of them use each address.
- CRL:
http://subca.crl.certum.pl/ctrca.crl(37) - CRL:
http://crl.certum.pl/ctrca.crl(2) - OCSP:
http://subca.ocsp-certum.com(39)
What happens when it expires
Certum Trusted Root CA is valid until 2043-03-16, 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 Certum Trusted Root CA by common name (Certum Trusted Root 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 Root CA" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: FE7696573855773E37A95E7AD4D9CC96C30157C15D31765BA9B15704E1AE78FD
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 C88344C018AE9FCCF187B78F22D1C5D74584BAE5
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 Root CA"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "Certum Trusted Root 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 "FE:76:96:57:38:55:77:3E:37:A9:5E:7A:D4:D9:CC:96:C3:01:57:C1:5D:31:76:5B:A9:B1:57:04:E1:AE:78:FD"
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 Asseco Data Systems S.A. → Certum Trusted Root 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.
# 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-root-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=FE:76:96:57:38:55:77:3E:37:A9:5E:7A:D4:D9:CC:96:C3:01:57:C1:5D:31:76:5B:A9:B1:57:04:E1:AE:78:FD
FAQ
Is Certum Trusted Root 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.
When does Certum Trusted Root CA expire?
On 2043-03-16, about 16.3 years after the 2026-11-10 data snapshot.
How many intermediate certificates has Certum Trusted Root CA issued?
The CCADB lists 40: 39 valid, 0 expired and 1 revoked. The newest valid one is AutonTrust PRO DV TLS G2 R31 CA, valid until 2031-06-06.
Is Certum Trusted Root CA 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 Network CA 2 RSA 4096 · 2046-10-06
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