Root certificate · GlobalSign
GlobalSign
GlobalSign is a root CA certificate operated by GlobalSign (RSA 2048, valid until 2029-03-18, SHA-256 CBB522D7). As of the latest CCADB data it is trusted for TLS server authentication by 4 of 4 major root stores: Chrome, Mozilla, Apple, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Included Included | Yes | 2026-09-30 | Yes |
| Mozilla | Included Included | Yes | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | No |
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.12.8 / Firefox 3.6.12
- Inclusion bug
- #507360
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 Tunnel Termination, IP Security User, Secure Email, Time Stamping
"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 - R3
- SHA-256
CBB522D7B7F127AD6A0113865BDF1CD4102E7D0759AF635A7CF4720DC963C53B- SHA-1 (Windows thumbprint)
D69B561148F01C77C54578C10926DF5B856976AD- SPKI SHA-256
706BB1017C855C59169BAD5C1781CF597F12D2CAD2F63D1A4AA37493800FFB80- Valid from
- 2009-03-18
- Expires
- 2029-03-18
- Key
- RSA 2048
- Signature algorithm
- sha256WithRSAEncryption
- Serial number
4000000000121585308A2- Trust bits (CCADB)
- Server Authentication, Client Authentication, Code Signing, Secure Email, Encrypting File System, Time Stamping, IP Security Tunnel Termination, IP Security User
- 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.r3.roots.globalsign.com· expired:https://expired.r3.roots.globalsign.com· revoked:https://revoked.r3.roots.globalsign.com - CCADB record
- A000150
- PEM
- globalsign.pem
Intermediate CAs issued by this root
The CCADB lists 216 intermediate CA certificates signed directly by GlobalSign: 86 currently valid, 94 expired and 36 revoked (revoked includes those whose parent was revoked). 1 of the valid ones run past the expiry date of the root itself (2029-03-18).
Showing 20 of 216: 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.
Cross-signed versions
4 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 by | CA owner | Expires | Status |
|---|---|---|---|
| GlobalSign Root CA crt.sh | GlobalSign nv-sa | 2028-01-28 | Valid |
| GlobalSign Root CA crt.sh | GlobalSign nv-sa | 2019-03-18 | Expired |
| GlobalSign Root CA crt.sh | GlobalSign nv-sa | 2019-03-18 | Expired |
| GlobalSign Root CA crt.sh | GlobalSign nv-sa | 2028-01-28 | Revoked |
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-r3.crlhttp://crl.globalsign.net/root-r3.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 86 valid intermediates signed by GlobalSign; the number in brackets is how many of them use each address.
- CRL:
http://crl.globalsign.com/root-r3.crl(82) - CRL:
http://crl.globalsign.net/root-r3.crl(3) - CRL:
http://crl.globalsign.com/root-r5.crl(1) - OCSP:
http://ocsp2.globalsign.com/rootr3(49) - OCSP:
http://ocsp.globalsign.com/rootr3(34) - OCSP:
http://ocsp2.globalsign.com/rootr5(1)
What happens when it expires
GlobalSign is valid until 2029-03-18, about 2.4 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. 1 of its valid intermediates expire later than the root, so their operators need another path, such as a cross-sign from a newer root, before 2029-03-18. 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: CBB522D7B7F127AD6A0113865BDF1CD4102E7D0759AF635A7CF4720DC963C53BWindows (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 D69B561148F01C77C54578C10926DF5B856976ADLinux (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 "CB:B5:22:D7:B7:F1:27:AD:6A:01:13:86:5B:DF:1C:D4:10:2E:7D:07:59:AF:63:5A:7C:F4:72:0D:C9:63:C5:3B"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.
# 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.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=CB:B5:22:D7:B7:F1:27:AD:6A:01:13:86:5B:DF:1C:D4:10:2E:7D:07:59:AF:63:5A:7C:F4:72:0D:C9:63:C5:3BFAQ
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 2029-03-18, about 2.4 years after the 2026-11-10 data snapshot. 1 of the valid ones run past the expiry date of the root itself (2029-03-18).
How many intermediate certificates has GlobalSign issued?
The CCADB lists 216: 86 valid, 94 expired and 36 revoked. The newest valid one is GlobalSign Atlas R3 EV TLS CA 2026, valid until 2029-03-18.
Is GlobalSign cross-signed?
Yes. The CCADB has 4 cross-certificate(s) with its subject and key, signed by GlobalSign Root CA; 1 of them are still valid.
Other roots from GlobalSign
- GlobalSign ECDSA P-384 · 2038-01-19
- GlobalSign RSA 4096 · 2034-12-10
- GlobalSign Root CA RSA 2048 · 2028-01-28
- GlobalSign Root E46 ECDSA P-384 · 2046-03-20
- GlobalSign Root R46 RSA 4096 · 2046-03-20
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