Root certificate · DigiCert
QuoVadis Root CA 3
QuoVadis Root CA 3 is a root CA certificate operated by DigiCert (RSA 4096, valid until 2031-11-24, SHA-256 18F1FC7F). As of the latest CCADB data it is trusted for TLS server authentication by 2 of 4 major root stores: Apple, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Removed Removed | No | — | No |
| Mozilla | Included Included | No | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | Yes |
The CCADB lists no EV policy OID for QuoVadis Root CA 3.
Removed Chrome
- Status
- Removed
Included Mozilla
- Status
- Included
- Trust bits
- EV policy OIDs
- not EV-enabled
- First included in
- NSS 3.11.8 / Firefox 2
- Inclusion bug
- #365281
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth, emailProtection
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client Authentication, Code Signing, OCSP Signing, Secure Email, Time Stamping
- Not-before cutoff
- 2021-08-01 (Code Signing, OCSP 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
- DigiCert
- Subject
- CN=QuoVadis Root CA 3,O=QuoVadis Limited,C=BM
- SHA-256
18F1FC7F205DF8ADDDEB7FE007DD57E3AF375A9C4D8D73546BF4F1FED1E18D35- SHA-1 (Windows thumbprint)
1F4914F7D874951DDDAE02C0BEFD3A2D82755185- SPKI SHA-256
0C7ACAA710226720BBC940349EE2E6148652A89DBF406A232C895F6DC78EBB9A- Valid from
- 2006-11-24
- Expires
- 2031-11-24
- Key
- RSA 4096
- Signature algorithm
- sha1WithRSAEncryption
- Serial number
5C6- Country
- BM
- Trust bits (CCADB)
- Server Authentication, Client Authentication, Secure Email, Time Stamping
- EV policy OIDs (CCADB)
- not EV-enabled · TLS EV capable: No
- Test websites
- valid:
https://quovadis-root-ca-3.chain-demos.digicert.com· expired:https://quovadis-root-ca-3-expired.chain-demos.digicert.com· revoked:https://quovadis-root-ca-3-revoked.chain-demos.digicert.com - CCADB record
- A000176
- PEM
- digicert-quovadis-root-ca-3.pem
Intermediate CAs issued by this root
The CCADB lists 35 intermediate CA certificates signed directly by QuoVadis Root CA 3: 2 currently valid, 1 expired and 32 revoked (revoked includes those whose parent was revoked).
Showing 20 of 35: 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 |
|---|---|---|---|
| BEKB - BCBE Issuing CA G2 | DigiCert | 2031-11-24 | Valid |
| DigiCert QuoVadis TLS ICA QV Root CA 3 | DigiCert | 2031-01-04 | Valid |
| BEKB - BCBE Issuing CA G2 | DigiCert | 2023-10-10 | Expired |
| QuoVadis RCA3G1 TLS CA | DigiCert | 2030-10-19 | Revoked |
| QuoVadis RCA3G1 TLS CA | DigiCert | 2030-10-19 | Revoked |
| QuoVadis QVRCA3G1 SSL ICA | DigiCert | 2027-04-19 | Revoked |
| Bayerische SSL-CA-2016-02 | DigiCert | 2026-12-02 | Revoked |
| Bayerische SSL-CA-2016-02 | DigiCert | 2026-12-02 | Revoked |
| Bayerische SSL-CA-2016-02 | DigiCert | 2026-12-02 | Revoked |
| FMH CA G2 | DigiCert | 2026-11-30 | Revoked |
| Bayerische SSL-CA-2016-01 | DigiCert | 2026-06-06 | Revoked |
| Bayerische SSL-CA-2016-01 | DigiCert | 2026-06-06 | Revoked |
| Bayerische SSL-CA-2016-01 | DigiCert | 2026-06-06 | Revoked |
| Bayerische SSL-CA-2015-02 | DigiCert | 2025-11-09 | Revoked |
| Suva Root CA 1 | DigiCert | 2025-08-28 | Revoked |
| FMH CA G1 | DigiCert | 2025-06-25 | Revoked |
| Bayerische SSL-CA-2015-01 | DigiCert | 2025-05-12 | Revoked |
| Intec Client ICA | DigiCert | 2024-12-29 | Revoked |
| Bayerische SSL-CA-2014-02 | DigiCert | 2024-11-17 | Revoked |
| Suva Root CA 1 | DigiCert | 2024-11-12 | Revoked |
Cross-signed versions
No certificate in the CCADB has the same subject and public key as QuoVadis Root CA 3 with a different issuer, so a client has to carry QuoVadis Root CA 3 itself in its root store to trust it.
CRL and OCSP addresses
In the root certificate
QuoVadis Root CA 3 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.quovadisglobal.com/qvrca3.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 2 valid intermediates signed by QuoVadis Root CA 3; the number in brackets is how many of them use each address.
- CRL:
http://crl.quovadisglobal.com/qvrca3.crl(2) - OCSP:
http://ocsp.quovadisglobal.com(2)
What happens when it expires
QuoVadis Root CA 3 is valid until 2031-11-24, about 5.0 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 QuoVadis Root CA 3 by common name (QuoVadis Root CA 3) 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 "QuoVadis Root CA 3" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 18F1FC7F205DF8ADDDEB7FE007DD57E3AF375A9C4D8D73546BF4F1FED1E18D35
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 1F4914F7D874951DDDAE02C0BEFD3A2D82755185
Linux (ca-certificates follows Mozilla: 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 "QuoVadis Root CA 3"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "QuoVadis Root CA 3"
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 "18:F1:FC:7F:20:5D:F8:AD:DD:EB:7F:E0:07:DD:57:E3:AF:37:5A:9C:4D:8D:73:54:6B:F4:F1:FE:D1:E1:8D:35"
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 QuoVadis Limited → QuoVadis Root CA 3.
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 digicert-quovadis-root-ca-3.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=18:F1:FC:7F:20:5D:F8:AD:DD:EB:7F:E0:07:DD:57:E3:AF:37:5A:9C:4D:8D:73:54:6B:F4:F1:FE:D1:E1:8D:35
FAQ
Is QuoVadis Root CA 3 trusted by Chrome, Firefox, Safari and Windows?
As of 2026-11-10, Apple, Microsoft trust it for TLS server authentication; Chrome, Mozilla do not.
When does QuoVadis Root CA 3 expire?
On 2031-11-24, about 5.0 years after the 2026-11-10 data snapshot.
How many intermediate certificates has QuoVadis Root CA 3 issued?
The CCADB lists 35: 2 valid, 1 expired and 32 revoked. The newest valid one is BEKB - BCBE Issuing CA G2, valid until 2031-11-24.
Is QuoVadis Root CA 3 cross-signed?
No. The CCADB has no certificate with the same subject and public key signed by another CA.
Other roots from DigiCert
- DigiCert Assured ID Root CA RSA 2048 · 2031-11-10
- DigiCert Assured ID Root G2 RSA 2048 · 2038-01-15
- DigiCert Assured ID Root G3 ECDSA P-384 · 2038-01-15
- DigiCert ECC P384 Root G5 ECDSA P-384 · 2046-01-14
- DigiCert Global Root CA RSA 2048 · 2031-11-10
- DigiCert Global Root G2 RSA 2048 · 2038-01-15
- DigiCert Global Root G3 ECDSA P-384 · 2038-01-15
- DigiCert High Assurance EV Root CA RSA 2048 · 2031-11-10
- DigiCert RSA4096 Root G5 RSA 4096 · 2046-01-14
- DigiCert TLS ECC P384 Root G5 ECDSA P-384 · 2046-01-14
- DigiCert TLS RSA4096 Root G5 RSA 4096 · 2046-01-14
- DigiCert Trusted Root G4 RSA 4096 · 2038-01-15
- QuoVadis Root CA 1 G3 RSA 4096 · 2042-01-12
- QuoVadis Root CA 2 RSA 4096 · 2031-11-24
- QuoVadis Root CA 2 G3 RSA 4096 · 2042-01-12
- QuoVadis Root CA 3 G3 RSA 4096 · 2042-01-12
- QuoVadis TLS ECC P384 Root G4 ECDSA P-384 · 2048-03-09
- QuoVadis TLS RSA 4096 Root G4 RSA 4096 · 2048-03-09
- Verizon Global Root CA RSA 2048 · 2034-07-30
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