Root certificate · Certum

Certum TLS ECC Root CA

Certum TLS ECC Root CA is a root CA certificate operated by Certum (ECDSA P-384, valid until 2048-01-26, SHA-256 630CCB83). As of the latest CCADB data it is trusted for TLS server authentication by 1 of 4 major root stores: Microsoft.

Data updated Nov 10, 2026

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 Certum TLS ECC Root CA.

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: Asseco Data Systems S.A.
Subject: CN=Certum TLS ECC Root CA,O=Asseco Data Systems S.A.,C=PL
SHA-256: 630CCB83B0180A992495E039D2613C3287A8102F8A8D703DB1330A3E86D4E653
SHA-1 (Windows thumbprint): B57B6C6566C12BB2390DE27FE45194765E8B7FC7
SPKI SHA-256: DDF469B7A279BB252D97EE2D3B0ABF60F60D0FA54918AA95D30235800F9CDA1A
Valid from: 2023-01-27
Expires: 2048-01-26
Key: ECDSA P-384
Signature algorithm: ecdsa-with-SHA384
Serial number: B07EC0CB2E05E63C71DA0D7F997971F3
Country: PL
Trust bits (CCADB): Server Authentication
EV policy OIDs (CCADB): not EV-enabled · TLS EV capable: No
Test websites: valid: https://valid-certumtlseccrootca.certificates.certum.pl/ · expired: https://expired-certumtlseccrootca.certificates.certum.pl/ · revoked: https://revoked-certumtlseccrootca.certificates.certum.pl/
CCADB record: A011565
PEM: certum-tls-ecc-root-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 3 intermediate CA certificates signed directly by Certum TLS ECC Root CA: 3 currently valid, 0 expired and 0 revoked (revoked includes those whose parent was revoked).

Showing 3 of 3: 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
Certum EV TLS G3 E39 CA	Asseco Data Systems S.A.	2039-03-20	Valid
Certum DV TLS G3 E39 CA	Asseco Data Systems S.A.	2039-03-20	Valid
Certum OV TLS G3 E39 CA	Asseco Data Systems S.A.	2039-03-20	Valid

Cross-signed versions

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

Signed by	CA owner	Expires	Status
Certum Trusted Network CA crt.sh	Asseco Data Systems S.A.	2029-12-30	Valid
Certum EC-384 CA crt.sh	Asseco Data Systems S.A.	2036-04-15	Valid

CRL and OCSP addresses

In the root certificate

Certum TLS ECC 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://subca.crl.certum.pl/certumtlseccrootca.crl

Used by the intermediates it issued

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

CRL: http://subca.crl.certum.pl/certumtlseccrootca.crl (3)
OCSP: http://subca.ocsp-certum.com (3)

What happens when it expires

Certum TLS ECC Root CA is valid until 2048-01-26, about 21.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 Certum TLS ECC Root CA by common name (Certum TLS ECC 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: 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 "Certum TLS ECC Root CA" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 630CCB83B0180A992495E039D2613C3287A8102F8A8D703DB1330A3E86D4E653

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 B57B6C6566C12BB2390DE27FE45194765E8B7FC7

Linux (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 "Certum TLS ECC Root CA"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "Certum TLS ECC 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 "63:0C:CB:83:B0:18:0A:99:24:95:E0:39:D2:61:3C:32:87:A8:10:2F:8A:8D:70:3D:B1:33:0A:3E:86:D4:E6:53"

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 TLS ECC 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.

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-tls-ecc-root-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=63:0C:CB:83:B0:18:0A:99:24:95:E0:39:D2:61:3C:32:87:A8:10:2F:8A:8D:70:3D:B1:33:0A:3E:86:D4:E6:53

FAQ

Is Certum TLS ECC Root CA 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 Certum TLS ECC Root CA expire?

On 2048-01-26, about 21.2 years after the 2026-11-10 data snapshot.

How many intermediate certificates has Certum TLS ECC Root CA issued?

The CCADB lists 3: 3 valid, 0 expired and 0 revoked. The newest valid one is Certum EV TLS G3 E39 CA, valid until 2039-03-20.

Is Certum TLS ECC Root CA cross-signed?

Yes. The CCADB has 2 cross-certificate(s) with its subject and key, signed by Certum Trusted Network CA, Certum EC-384 CA; 2 of them are still valid.

Other roots from Certum

Certum EC-384 CA ECDSA P-384 · 2043-03-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
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