Root certificate · První certifikační autorita (I.CA)

I.CA TLS Root CA/RSA 05/2022

I.CA TLS Root CA/RSA 05/2022 is a root CA certificate operated by První certifikační autorita (I.CA) (RSA 4096, valid until 2047-05-03, SHA-256 F9A17A00). 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 I.CA TLS Root CA/RSA 05/2022.

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, Client 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: První certifikační autorita, a.s.
Subject: C=CZ,2.5.4.97=NTRCZ-26439395,O=První certifikační autorita\, a.s.,CN=I.CA TLS Root CA/RSA 05/2022
SHA-256: F9A17A00E5C294BA9614A715819AF57F3FD48CC413453FBB8A5FC7E97964E2BC
SHA-1 (Windows thumbprint): 83E5E5DE325414970B263011084456E5FAA13FFA
SPKI SHA-256: CFE016B124E93C7BB4F1D8D01C2A209391D8EC3C310E6EABC14BDBF0F52C1F60
Valid from: 2022-05-03
Expires: 2047-05-03
Key: RSA 4096
Signature algorithm: sha512WithRSAEncryption
Serial number: 5F5E104
Country: CZ
Trust bits (CCADB): Server Authentication, Client Authentication
EV policy OIDs (CCADB): not EV-enabled · TLS EV capable: No
Test websites: valid: https://test-evssl.ica.cz:1446/test-EVSSL-valid-ica22.html · expired: https://test-evssl.ica.cz:2446/test-EVSSL-expired-ica22.html · revoked: https://test-evssl.ica.cz:3446/test-EVSSL-revoked-ica22.html
CCADB record: A010692
PEM: ica-cz-i-ca-tls-root-ca-rsa-05-2022.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 2 intermediate CA certificates signed directly by I.CA TLS Root CA/RSA 05/2022: 2 currently valid, 0 expired and 0 revoked (revoked includes those whose parent was revoked).

Showing 2 of 2: 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
I.CA TLS EV CA/RSA 06/2022	První certifikační autorita, a.s.	2032-06-19	Valid
I.CA TLS DV/OV CA/RSA 06/2022	První certifikační autorita, a.s.	2032-06-19	Valid

Cross-signed versions

No certificate in the CCADB has the same subject and public key as I.CA TLS Root CA/RSA 05/2022 with a different issuer, so a client has to carry I.CA TLS Root CA/RSA 05/2022 itself in its root store to trust it.

CRL and OCSP addresses

In the root certificate

I.CA TLS Root CA/RSA 05/2022 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://qcrldp1.ica.cz/rcatls22_rsa.crl

Used by the intermediates it issued

Addresses found in the CRL Distribution Points and OCSP fields of the 2 valid intermediates signed by I.CA TLS Root CA/RSA 05/2022; the number in brackets is how many of them use each address.

CRL: http://qcrldp1.ica.cz/rcatls22_rsa.crl (2)
CRL: http://qcrldp2.ica.cz/rcatls22_rsa.crl (2)
CRL: http://qcrldp3.ica.cz/rcatls22_rsa.crl (2)
OCSP: http://ocsp.ica.cz/rcatls22_rsa (2)

What happens when it expires

I.CA TLS Root CA/RSA 05/2022 is valid until 2047-05-03, about 20.5 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 I.CA TLS Root CA/RSA 05/2022 by common name (I.CA TLS Root CA/RSA 05/2022) 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 "I.CA TLS Root CA/RSA 05/2022" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: F9A17A00E5C294BA9614A715819AF57F3FD48CC413453FBB8A5FC7E97964E2BC

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 83E5E5DE325414970B263011084456E5FAA13FFA

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

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 "F9:A1:7A:00:E5:C2:94:BA:96:14:A7:15:81:9A:F5:7F:3F:D4:8C:C4:13:45:3F:BB:8A:5F:C7:E9:79:64:E2:BC"

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 První certifikační autorita, a.s. → I.CA TLS Root CA/RSA 05/2022.

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 ica-cz-i-ca-tls-root-ca-rsa-05-2022.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=F9:A1:7A:00:E5:C2:94:BA:96:14:A7:15:81:9A:F5:7F:3F:D4:8C:C4:13:45:3F:BB:8A:5F:C7:E9:79:64:E2:BC

FAQ

Is I.CA TLS Root CA/RSA 05/2022 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 I.CA TLS Root CA/RSA 05/2022 expire?

On 2047-05-03, about 20.5 years after the 2026-11-10 data snapshot.

How many intermediate certificates has I.CA TLS Root CA/RSA 05/2022 issued?

The CCADB lists 2: 2 valid, 0 expired and 0 revoked. The newest valid one is I.CA TLS EV CA/RSA 06/2022, valid until 2032-06-19.

Is I.CA TLS Root CA/RSA 05/2022 cross-signed?

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

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