Root certificate · GlobalSign

GlobalSign Root CA

GlobalSign Root CA is a root CA certificate operated by GlobalSign (RSA 2048, valid until 2028-01-28, SHA-256 EBD41040). As of the latest CCADB data it is trusted for TLS server authentication by 2 of 4 major root stores: Apple, Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeRemoved RemovedNo—No
MozillaIncluded IncludedNo—No
AppleIncluded IncludedYes—No
MicrosoftIncluded IncludedYes—Yes

The CCADB lists EV policy OID 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 for this root, but Mozilla does not mark it as EV-enabled.

Removed Chrome

Status
Removed

Included Mozilla

Status
Included
Trust bits
Email
EV policy OIDs
not EV-enabled
First included in
NSS 3.11.10 / Firefox 3.0.2
Inclusion bug
#406794

Included Apple

Status
Included
Trust bits
serverAuth, clientAuth, emailProtection

Included Microsoft

Status
Included
Trusted EKUs
Server Authentication, Client Authentication, Code Signing, Encrypting File System, IP Security IKE Intermediate, IP Security Tunnel Termination, IP Security User, OCSP Signing, Secure Email, Time Stamping
Not-before cutoff
2019-10-01 (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 Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE
SHA-256
EBD41040E4BB3EC742C9E381D31EF2A41A48B6685C96E7CEF3C1DF6CD4331C99
SHA-1 (Windows thumbprint)
B1BC968BD4F49D622AA89A81F2150152A41D829C
SPKI SHA-256
2BCEE858158CF5465FC9D76F0DFA312FEF25A4DCA8501DA9B46B67D1FBFA1B64
Valid from
1998-09-01
Expires
2028-01-28
Key
RSA 2048
Signature algorithm
sha1WithRSAEncryption
Serial number
40000000001154B5AC394
Country
BE
Trust bits (CCADB)
Server Authentication, Client Authentication, Code Signing, Secure Email, Encrypting File System, Time Stamping, IP Security Tunnel Termination, IP Security User, IP Security IKE Intermediate
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 · TLS EV capable: Yes
Test websites
valid: https://valid.r1.roots.globalsign.com · expired: https://expired.r1.roots.globalsign.com · revoked: https://revoked.r1.roots.globalsign.com
CCADB record
A000151
PEM
globalsign-root-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 73 intermediate CA certificates signed directly by GlobalSign Root CA: 12 currently valid, 30 expired and 31 revoked (revoked includes those whose parent was revoked).

Showing 20 of 73: 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 Root R46 → GlobalSign Root R46 GlobalSign nv-sa2028-01-28Valid
GlobalSign GCC R1 OV TLS CA 2025 GlobalSign nv-sa2028-01-28Valid
GTS Root R4 → GTS Root R4 Google Trust Services LLC2028-01-28Valid
GlobalSign Atlas R1 EV TLS CA 2023 GlobalSign nv-sa2028-01-28Valid
AlphaSSL CA - SHA256 - G4 GlobalSign nv-sa2027-10-12Valid
GTS Root R1 → GTS Root R1 Google Trust Services LLC2028-01-28Valid
GlobalSign Timestamping CA - G3 GlobalSign nv-sa2028-01-28Valid
GlobalSign Root R46 → GlobalSign Root R46 GlobalSign nv-sa2028-01-28Valid
GlobalSign Root E46 → GlobalSign Root E46 GlobalSign nv-sa2028-01-28Valid
GlobalSign → GlobalSign GlobalSign nv-sa2028-01-28Valid
GlobalSign → GlobalSign GlobalSign nv-sa2028-01-28Valid
GlobalSign → GlobalSign GlobalSign nv-sa2028-01-28Valid
GlobalSign CodeSigning CA - G3 GlobalSign nv-sa2024-03-16Expired
GlobalSign Organization Validation CA - SHA256 - G3 GlobalSign nv-sa2025-09-04Expired
GlobalSign Domain Validation CA - SHA256 - G3 GlobalSign nv-sa2025-09-04Expired
GlobalSign CloudSSL CA - SHA1 - G3 GlobalSign nv-sa2017-08-19Expired
GlobalSign CloudSSL CA - SHA256 - G3 GlobalSign nv-sa2025-08-19Expired
GlobalSign CloudSSL CA - SHA1 - G3 GlobalSign nv-sa2017-07-09Expired
GlobalSign CloudSSL CA - SHA1 - G3 GlobalSign nv-sa2017-04-30Expired
AlphaSSL CA - SHA256 - G2 GlobalSign nv-sa2024-02-20Expired

Cross-signed versions

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

Signed byCA ownerExpiresStatus
GlobalSign crt.sh Google Trust Services LLC2021-12-15Revoked

CRL and OCSP addresses

In the root certificate

GlobalSign Root CA 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.crl
  • http://crl.globalsign.com/Root.crl
  • http://crl.globalsign.net/Root.crl
  • http://crl.globalsign.net/root.crl
  • http://secure.globalsign.net/crl/Root.crl
  • http://secure.globalsign.net/crl/root.crl
  • http://c.pki.goog/r/gsr1.crl
  • http://crl.pki.goog/gsr1/gsr1.crl

Used by the intermediates it issued

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

  • CRL: http://crl.globalsign.com/root.crl (10)
  • CRL: http://c.pki.goog/r/gsr1.crl (1)
  • CRL: http://crl.pki.goog/gsr1/gsr1.crl (1)
  • OCSP: http://ocsp.globalsign.com/rootr1 (10)
  • OCSP: http://ocsp.pki.goog/gsr1 (1)

What happens when it expires

GlobalSign Root CA is valid until 2028-01-28, about 1.2 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 GlobalSign Root CA by common name (GlobalSign Root CA) 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 Root CA" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: EBD41040E4BB3EC742C9E381D31EF2A41A48B6685C96E7CEF3C1DF6CD4331C99

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 B1BC968BD4F49D622AA89A81F2150152A41D829C

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

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 "EB:D4:10:40:E4:BB:3E:C7:42:C9:E3:81:D3:1E:F2:A4:1A:48:B6:68:5C:96:E7:CE:F3:C1:DF:6C:D4:33:1C:99"

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 nv-sa → GlobalSign Root CA.

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-root-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=EB:D4:10:40:E4:BB:3E:C7:42:C9:E3:81:D3:1E:F2:A4:1A:48:B6:68:5C:96:E7:CE:F3:C1:DF:6C:D4:33:1C:99

FAQ

Is GlobalSign Root CA 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 GlobalSign Root CA expire?

On 2028-01-28, about 1.2 years after the 2026-11-10 data snapshot.

How many intermediate certificates has GlobalSign Root CA issued?

The CCADB lists 73: 12 valid, 30 expired and 31 revoked. The newest valid one is GlobalSign Root R46, valid until 2028-01-28.

Is GlobalSign Root CA cross-signed?

Yes. The CCADB has 1 cross-certificate(s) with its subject and key, signed by GlobalSign; 0 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