Root certificate · Disig, a.s.
CA Disig Root R2
CA Disig Root R2 is a root CA certificate operated by Disig, a.s. (RSA 4096, valid until 2042-07-19, SHA-256 E23D4A03). 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 | — | Yes |
The CCADB lists no EV policy OID for CA Disig Root R2.
Included Chrome
- Status
- Included
Included Mozilla
- Status
- Included
- Trust bits
- Websites, Email
- EV policy OIDs
- not EV-enabled
- First included in
- NSS 3.15 / Firefox 23
- Inclusion bug
- #792377
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth, emailProtection
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client Authentication, Code Signing, Encrypting File System, Secure Email, Time Stamping
- Not-before cutoff
- 2020-06-01 (Code Signing)
"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
- Disig, a.s.
- Subject
- CN=CA Disig Root R2,O=Disig a.s.,L=Bratislava,C=SK
- SHA-256
E23D4A036D7B70E9F595B1422079D2B91EDFBB1FB651A0633EAA8A9DC5F80703- SHA-1 (Windows thumbprint)
B561EBEAA4DEE4254B691A98A55747C234C7D971- SPKI SHA-256
702116CCD8BF23E16466F0E0DBA0ED6A239A9C1CD6A8F5A66B39AF3595020385- Valid from
- 2012-07-19
- Expires
- 2042-07-19
- Key
- RSA 4096
- Signature algorithm
- sha256WithRSAEncryption
- Serial number
92B888DBB08AC163- Country
- SK
- Trust bits (CCADB)
- Server Authentication, Client Authentication, Secure Email, Encrypting File System, Time Stamping
- EV policy OIDs (CCADB)
- not EV-enabled · TLS EV capable: No
- Test websites
- valid:
https://testssl-valid-r2i2.disig.sk/· expired:https://testssl-expire-r2i2.disig.sk/· revoked:https://testssl-revoked-r2i2.disig.sk/ - CCADB record
- A000095
- PEM
- disig-ca-disig-root-r2.pem
Intermediate CAs issued by this root
The CCADB lists 5 intermediate CA certificates signed directly by CA Disig Root R2: 3 currently valid, 0 expired and 2 revoked (revoked includes those whose parent was revoked).
Showing 5 of 5: 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 |
|---|---|---|---|
| CA Disig TLS Root R3 → CA Disig TLS Root R3 | Disig, a.s. | 2029-04-12 | Valid |
| CA Disig R2I5 Certification Service | Disig, a.s. | 2033-04-20 | Valid |
| CA Disig R2I2 Certification Service | Disig, a.s. | 2029-09-28 | Valid |
| CA Disig R2I3 Certification Service | Disig, a.s. | 2029-09-28 | Revoked |
| CA Disig R2I1 Certification Service | Disig, a.s. | 2027-09-08 | Revoked |
Cross-signed versions
No certificate in the CCADB has the same subject and public key as CA Disig Root R2 with a different issuer, so a client has to carry CA Disig Root R2 itself in its root store to trust it.
CRL and OCSP addresses
In the root certificate
CA Disig Root R2 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://cdp1.disig.sk/rootcar2/crl/rootcar2.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 3 valid intermediates signed by CA Disig Root R2; the number in brackets is how many of them use each address.
- CRL:
http://cdp.disig.sk/rootcar2/crl/rootcar2.crl(2) - CRL:
http://cdp1.disig.sk/rootcar2/crl/rootcar2.crl(1) - CRL:
http://cdp2.disig.sk/rootcar2/crl/rootcar2.crl(1) - OCSP:
http://rootcar2-ocsp.disig.sk/ocsp/rootcar2(2)
What happens when it expires
CA Disig Root R2 is valid until 2042-07-19, about 15.7 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 CA Disig Root R2 by common name (CA Disig Root R2) 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 "CA Disig Root R2" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: E23D4A036D7B70E9F595B1422079D2B91EDFBB1FB651A0633EAA8A9DC5F80703
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 B561EBEAA4DEE4254B691A98A55747C234C7D971
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 "CA Disig Root R2"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "CA Disig Root R2"
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 "E2:3D:4A:03:6D:7B:70:E9:F5:95:B1:42:20:79:D2:B9:1E:DF:BB:1F:B6:51:A0:63:3E:AA:8A:9D:C5:F8:07:03"
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 Disig a.s. → CA Disig Root R2.
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 disig-ca-disig-root-r2.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=E2:3D:4A:03:6D:7B:70:E9:F5:95:B1:42:20:79:D2:B9:1E:DF:BB:1F:B6:51:A0:63:3E:AA:8A:9D:C5:F8:07:03
FAQ
Is CA Disig Root R2 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 CA Disig Root R2 expire?
On 2042-07-19, about 15.7 years after the 2026-11-10 data snapshot.
How many intermediate certificates has CA Disig Root R2 issued?
The CCADB lists 5: 3 valid, 0 expired and 2 revoked. The newest valid one is CA Disig TLS Root R3, valid until 2029-04-12.
Is CA Disig Root R2 cross-signed?
No. The CCADB has no certificate with the same subject and public key signed by another CA.
Other roots from Disig, a.s.
- CA Disig TLS Root R3 RSA 4096 · 2040-09-14
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