Root certificate · GlobalSign

GlobalSign

GlobalSign is a root CA certificate operated by GlobalSign (RSA 4096, valid until 2034-12-10, SHA-256 2CABEAFE). As of the latest CCADB data it is trusted for TLS server authentication by 4 of 4 major root stores: Chrome, Mozilla, Apple, Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeIncluded IncludedYes2026-09-30Yes
MozillaIncluded IncludedYes—No
AppleIncluded IncludedYes—No
MicrosoftIncluded IncludedYes—Yes

Chrome stops trusting TLS certificates under this root whose SCTs are dated after 2026-09-30 (sct_not_after). Mozilla treats it as an EV root for policy OID 2.23.140.1.1.

Included Chrome

Status
Included
Distrust for TLS after
2026-09-30

Included Mozilla

Status
Included
Trust bits
Websites, Email
EV policy OIDs
2.23.140.1.1
First included in
NSS 3.39 / Firefox 63
Inclusion bug
#1390803

Included Apple

Status
Included
Trust bits
serverAuth, clientAuth, emailProtection

Included Microsoft

Status
Included
Trusted EKUs
Server Authentication, Client Authentication, Code Signing, Document Signing, Encrypting File System, OCSP Signing, Secure Email, Time Stamping
Not-before cutoff
2021-08-01 (Code Signing, OCSP Signing)
Disallowed EKUs
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
GlobalSign nv-sa
Subject
CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R6
SHA-256
2CABEAFE37D06CA22ABA7391C0033D25982952C453647349763A3AB5AD6CCF69
SHA-1 (Windows thumbprint)
8094640EB5A7A1CA119C1FDDD59F810263A7FBD1
SPKI SHA-256
682747F8BA621B87CDD3BC295ED5CABCE722A1C0C0363D1D68B38928D2787F1E
Valid from
2014-12-10
Expires
2034-12-10
Key
RSA 4096
Signature algorithm
sha384WithRSAEncryption
Serial number
45E6BB038333C3856548E6FF4551
Trust bits (CCADB)
Server Authentication, Client Authentication, Document Signing, Secure Email, Encrypting File System, Time Stamping
EV policy OIDs (CCADB)
2.23.140.1.1, 1.3.6.1.4.1.4146.10.1.1, 1.3.6.1.4.1.4146.1.1, 2.23.140.1.3, 1.3.6.1.4.1.4146.1.2 · TLS EV capable: Yes
Test websites
valid: https://valid.r6.roots.globalsign.com/ · expired: https://expired.r6.roots.globalsign.com/ · revoked: https://revoked.r6.roots.globalsign.com/
CCADB record
A002469
PEM
globalsign-2cabeafe.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 60 intermediate CA certificates signed directly by GlobalSign: 35 currently valid, 17 expired and 8 revoked (revoked includes those whose parent was revoked).

Showing 20 of 60: 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
GlobalSign Client Authentication Root R45 GlobalSign nv-sa2034-12-10Valid
GlobalSign Client Authentication Root E45 GlobalSign nv-sa2034-12-10Valid
GlobalSign Atlas R6 EV TLS CA 2026 LT GlobalSign nv-sa2029-07-21Valid
GlobalSign Atlas R6 EV TLS CA 2026 Q3 GlobalSign nv-sa2028-04-22Valid
GlobalSign GCC R6 Authentication CA 2026 GlobalSign nv-sa2031-03-31Valid
GlobalSign Atlas R6 EV TLS CA 2026 Q2 GlobalSign nv-sa2028-01-21Valid
GlobalSign GCC R6 OV TLS CA 2025 V2 GlobalSign nv-sa2027-10-15Valid
GlobalSign Atlas R6 EV TLS CA 2026 Q1 GlobalSign nv-sa2027-10-15Valid
GlobalSign Atlas R6 EV TLS CA 2025 Q4 GlobalSign nv-sa2027-07-16Valid
GlobalSign GCC R6 AlphaSSL CA 2025 GlobalSign nv-sa2027-05-21Valid
GlobalSign Atlas R6 EV TLS CA 2025 Q3 GlobalSign nv-sa2027-04-16Valid
GlobalSign Atlas R6 EV TLS CA 2025 Q2 GlobalSign nv-sa2027-01-22Valid
Soluti V2 GR6 DV TLS CA 2024 GlobalSign nv-sa2029-11-20Valid
Soluti V2 GR6 EV TLS CA 2024 GlobalSign nv-sa2029-11-20Valid
Soluti V2 GR6 OV TLS CA 2024 GlobalSign nv-sa2029-11-20Valid
Banco Votorantim SA GR6 EV TLS CA 2024 GlobalSign nv-sa2029-11-20Valid
Prodrive Technologies GCC R6 OV TLS CA 2024 GlobalSign nv-sa2029-09-18Valid
sslTrus GCC R6 OV TLS CA 2024 GlobalSign nv-sa2027-09-18Valid
sslTrus GCC R6 EV TLS CA 2024 GlobalSign nv-sa2027-09-18Valid
sslTrus GCC R6 DV TLS CA 2024 GlobalSign nv-sa2027-09-18Valid

Cross-signed versions

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

Signed byCA ownerExpiresStatus
GlobalSign Root CA crt.sh GlobalSign nv-sa2028-01-28Valid
GlobalSign crt.sh GlobalSign nv-sa2029-03-18Valid

CRL and OCSP addresses

In the root certificate

GlobalSign 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.globalsign.com/root-r6.crl

Used by the intermediates it issued

Addresses found in the CRL Distribution Points and OCSP fields of the 35 valid intermediates signed by GlobalSign; the number in brackets is how many of them use each address.

  • CRL: http://crl.globalsign.com/root-r6.crl (35)
  • OCSP: http://ocsp2.globalsign.com/rootr6 (35)

What happens when it expires

GlobalSign is valid until 2034-12-10, about 8.1 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. Root programs can stop trusting it before it expires: Chrome 2026-09-30.

Check whether your device trusts it

Each platform keeps its own root store. The commands below look up GlobalSign by common name (GlobalSign) 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 "GlobalSign" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 2CABEAFE37D06CA22ABA7391C0033D25982952C453647349763A3AB5AD6CCF69

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 8094640EB5A7A1CA119C1FDDD59F810263A7FBD1

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

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 "2C:AB:EA:FE:37:D0:6C:A2:2A:BA:73:91:C0:03:3D:25:98:29:52:C4:53:64:73:49:76:3A:3A:B5:AD:6C:CF:69"

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 GlobalSign → GlobalSign.

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 globalsign-2cabeafe.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=2C:AB:EA:FE:37:D0:6C:A2:2A:BA:73:91:C0:03:3D:25:98:29:52:C4:53:64:73:49:76:3A:3A:B5:AD:6C:CF:69

FAQ

Is GlobalSign 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. Distrust-after dates already set: Chrome 2026-09-30.

When does GlobalSign expire?

On 2034-12-10, about 8.1 years after the 2026-11-10 data snapshot.

How many intermediate certificates has GlobalSign issued?

The CCADB lists 60: 35 valid, 17 expired and 8 revoked. The newest valid one is GlobalSign Client Authentication Root R45, valid until 2034-12-10.

Is GlobalSign cross-signed?

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

Other roots from GlobalSign

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