中文

Root certificate · DigiCert

QuoVadis TLS RSA 4096 Root G4

QuoVadis TLS RSA 4096 Root G4 is a root CA certificate operated by DigiCert (RSA 4096, valid until 2048-03-09, SHA-256 C8A2D38A). As of the latest CCADB data it is trusted for TLS server authentication by 1 of 4 major root stores: Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeNot included Not includedNo—No
MozillaNot included Not includedNo—No
AppleNot included Not includedNo—No
MicrosoftIncluded IncludedYes—No

The CCADB lists EV policy OID 2.23.140.1.1 for this root, but Mozilla does not mark it as EV-enabled.

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
DigiCert
Subject
CN=QuoVadis TLS RSA 4096 Root G4,O=QuoVadis Trustlink B.V.,C=NL
SHA-256
C8A2D38A24F5AC302D8A08EBD38923D9A750B49220F092E82D1C53249E1533D0
SHA-1 (Windows thumbprint)
20AFEA8DCB031F0684DF8FFD2598C8B7967FCD3C
SPKI SHA-256
FAD2D9A49B5EC58616A052D82B459BC42725C8ED13070C6CFB82307F115593FE
Valid from
2023-03-16
Expires
2048-03-09
Key
RSA 4096
Signature algorithm
sha384WithRSAEncryption
Serial number
25FE5839FB3AABDC3721EED699E7649FF6634FE
Country
NL
Trust bits (CCADB)
Server Authentication, Client Authentication
EV policy OIDs (CCADB)
2.23.140.1.1 · TLS EV capable: Yes
Test websites
valid: https://quovadis-tls-rsa4096-root-g4.chain-demos.digicert.com · expired: https://quovadis-tls-rsa4096-root-g4-expired.chain-demos.digicert.com · revoked: https://quovadis-tls-rsa4096-root-g4-revoked.chain-demos.digicert.com
CCADB record
A011347
PEM
digicert-quovadis-tls-rsa-4096-root-g4.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 1 intermediate CA certificates signed directly by QuoVadis TLS RSA 4096 Root G4: 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.

IntermediateOperated byExpiresStatus
DigiCert QuoVadis G4 TLS RSA4096 SHA384 2023 CA1 DigiCert2033-03-13Valid

Cross-signed versions

No certificate in the CCADB has the same subject and public key as QuoVadis TLS RSA 4096 Root G4 with a different issuer, so a client has to carry QuoVadis TLS RSA 4096 Root G4 itself in its root store to trust it.

CRL and OCSP addresses

In the root certificate

QuoVadis TLS RSA 4096 Root G4 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/qvtlsrsa4096rootg4.crl

Used by the intermediates it issued

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

  • CRL: http://crl.quovadisglobal.com/qvtlsrsa4096rootg4.crl (1)
  • OCSP: http://ocsp.quovadisglobal.com (1)

What happens when it expires

QuoVadis TLS RSA 4096 Root G4 is valid until 2048-03-09, about 21.3 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 TLS RSA 4096 Root G4 by common name (QuoVadis TLS RSA 4096 Root G4) 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 "QuoVadis TLS RSA 4096 Root G4" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: C8A2D38A24F5AC302D8A08EBD38923D9A750B49220F092E82D1C53249E1533D0

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 20AFEA8DCB031F0684DF8FFD2598C8B7967FCD3C

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

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 "C8:A2:D3:8A:24:F5:AC:30:2D:8A:08:EB:D3:89:23:D9:A7:50:B4:92:20:F0:92:E8:2D:1C:53:24:9E:15:33:D0"

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 Trustlink B.V. → QuoVadis TLS RSA 4096 Root G4.

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 digicert-quovadis-tls-rsa-4096-root-g4.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=C8:A2:D3:8A:24:F5:AC:30:2D:8A:08:EB:D3:89:23:D9:A7:50:B4:92:20:F0:92:E8:2D:1C:53:24:9E:15:33:D0

FAQ

Is QuoVadis TLS RSA 4096 Root G4 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 QuoVadis TLS RSA 4096 Root G4 expire?

On 2048-03-09, about 21.3 years after the 2026-11-10 data snapshot.

How many intermediate certificates has QuoVadis TLS RSA 4096 Root G4 issued?

The CCADB lists 1: 1 valid, 0 expired and 0 revoked. The newest valid one is DigiCert QuoVadis G4 TLS RSA4096 SHA384 2023 CA1, valid until 2033-03-13.

Is QuoVadis TLS RSA 4096 Root G4 cross-signed?

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

Other roots from DigiCert

Sources

  1. CCADB — Resources (TLS Server Authentication report, All Included Root Certificate Trust Bit Settings)
  2. CCADB — All Certificate Information (root and intermediate), CSV V5
  3. CCADB — Mozilla Included CA Certificate Report
  4. CCADB — Chrome / Mozilla / Apple / Microsoft TLS Server Authentication CSV