Root certificate · Disig, a.s.

CA Disig TLS Root R3

CA Disig TLS Root R3 is a root CA certificate operated by Disig, a.s. (RSA 4096, valid until 2040-09-14, SHA-256 6248199F). 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 CA Disig TLS Root R3.

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: Disig, a.s.
Subject: CN=CA Disig TLS Root R3,O=Disig a.s.,L=Bratislava,C=SK
SHA-256: 6248199FEA4811FD34AA96EF0A26DE52134B73A9A2A99678F0C2EBADF8663EF8
SHA-1 (Windows thumbprint): AF250F267724C554652607D70985DE93DD33AFC0
SPKI SHA-256: 6C40941018EEC3846B13FAFE074704894EDF95A64C393150FD2F703F4C43D3FD
Valid from: 2025-09-18
Expires: 2040-09-14
Key: RSA 4096
Signature algorithm: sha256WithRSAEncryption
Serial number: 5B99ABC2B008CF8441D62E523909B41B
Country: SK
Trust bits (CCADB): Server Authentication
EV policy OIDs (CCADB): not EV-enabled · TLS EV capable: No
Test websites: valid: https://testssl-valid-r3i1.disig.sk/ · expired: https://testssl-expire-r3i1.disig.sk/ · revoked: https://testssl-revoked-r3i1.disig.sk/
CCADB record: A013052
PEM: disig-ca-disig-tls-root-r3.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

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

Showing 1 of 1: 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 R3I1 TLS Certification Service	Disig, a.s.	2029-04-12	Valid

Cross-signed versions

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

Signed by	CA owner	Expires	Status
CA Disig Root R2 crt.sh	Disig, a.s.	2029-04-12	Valid

CRL and OCSP addresses

In the root certificate

CA Disig TLS Root R3 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://cdp.disig.sk/rootcar3/crl/rootcar3.crl

Used by the intermediates it issued

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

CRL: http://cdp.disig.sk/rootcar3/crl/rootcar3.crl (1)

None of the valid intermediates under this root lists an OCSP responder.

What happens when it expires

CA Disig TLS Root R3 is valid until 2040-09-14, about 13.8 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 TLS Root R3 by common name (CA Disig TLS Root R3) 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 "CA Disig TLS Root R3" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 6248199FEA4811FD34AA96EF0A26DE52134B73A9A2A99678F0C2EBADF8663EF8

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 AF250F267724C554652607D70985DE93DD33AFC0

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

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 "62:48:19:9F:EA:48:11:FD:34:AA:96:EF:0A:26:DE:52:13:4B:73:A9:A2:A9:96:78:F0:C2:EB:AD:F8:66:3E:F8"

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 TLS Root R3.

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 disig-ca-disig-tls-root-r3.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=62:48:19:9F:EA:48:11:FD:34:AA:96:EF:0A:26:DE:52:13:4B:73:A9:A2:A9:96:78:F0:C2:EB:AD:F8:66:3E:F8

FAQ

Is CA Disig TLS Root R3 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 CA Disig TLS Root R3 expire?

On 2040-09-14, about 13.8 years after the 2026-11-10 data snapshot.

How many intermediate certificates has CA Disig TLS Root R3 issued?

The CCADB lists 1: 1 valid, 0 expired and 0 revoked. The newest valid one is CA Disig R3I1 TLS Certification Service, valid until 2029-04-12.

Is CA Disig TLS Root R3 cross-signed?

Yes. The CCADB has 1 cross-certificate(s) with its subject and key, signed by CA Disig Root R2; 1 of them are still valid.

Other roots from Disig, a.s.

CA Disig Root R2 RSA 4096 · 2042-07-19

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