Root certificate · GlobalSign

GlobalSign Root R46

GlobalSign Root R46 is a root CA certificate operated by GlobalSign (RSA 4096, valid until 2046-03-20, SHA-256 4FA3126D). 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 IncludedYes—No
MozillaIncluded IncludedYes—No
AppleIncluded IncludedYes—No
MicrosoftIncluded IncludedYes—No

Mozilla treats it as an EV root for policy OID 2.23.140.1.1.

Included Chrome

Status
Included

Included Mozilla

Status
Included
Trust bits
Websites
EV policy OIDs
2.23.140.1.1
First included in
NSS 3.63 / Firefox 88
Inclusion bug
#1570724

Included Apple

Status
Included
Trust bits
serverAuth, clientAuth

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
GlobalSign nv-sa
Subject
CN=GlobalSign Root R46,O=GlobalSign nv-sa,C=BE
SHA-256
4FA3126D8D3A11D1C4855A4F807CBAD6CF919D3A5A88B03BEA2C6372D93C40C9
SHA-1 (Windows thumbprint)
53A2B04BCA6BD645E6398A8EC40DD2BF77C3A290
SPKI SHA-256
AE7F962CB9E6A7DBF7B833FB18FA9B71A89175DF949C232B6A9EF7CB3DF2BBFC
Valid from
2019-03-20
Expires
2046-03-20
Key
RSA 4096
Signature algorithm
sha384WithRSAEncryption
Serial number
11D2BBB9D723189E405F0A9D2DD0DF2567D1
Country
BE
Trust bits (CCADB)
Server Authentication, Client Authentication
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 · TLS EV capable: Yes
Test websites
valid: https://valid.r46.roots.globalsign.com · expired: https://expired.r46.roots.globalsign.com · revoked: https://revoked.r46.roots.globalsign.com
CCADB record
A006509
PEM
globalsign-root-r46.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 74 intermediate CA certificates signed directly by GlobalSign Root R46: 54 currently valid, 14 expired and 6 revoked (revoked includes those whose parent was revoked).

Showing 20 of 74: 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 Atlas R46 EV TLS CA 2027 H1 GlobalSign nv-sa2029-10-21Valid
GlobalSign Atlas R46 DV TLS CA 2027 H1 GlobalSign nv-sa2029-10-21Valid
GlobalSign Atlas R46 OV TLS CA 2027 H1 GlobalSign nv-sa2029-10-21Valid
Alibaba Cloud Atlas R46 OV TLS CA 2026 GlobalSign nv-sa2029-10-21Valid
GlobalSign Atlas R46 OV TLS CA SHA256 2026 GlobalSign nv-sa2029-09-15Valid
GlobalSign GCC R46 OV TLS CA 2026 GlobalSign nv-sa2029-09-15Valid
Alibaba Cloud Atlas R46 DV TLS CA 2026 GlobalSign nv-sa2029-08-18Valid
AC Prodesp Site Seguro AR46 OV TLS CA 2026 GlobalSign nv-sa2029-08-18Valid
Alibaba Cloud GCC R46 OV TLS CA 2026 GlobalSign nv-sa2029-08-18Valid
DHL Global TLS CA I7 GlobalSign nv-sa2036-07-30Valid
GlobalSign Atlas R46 DV TLS CA 2026 Q4 GlobalSign nv-sa2028-07-21Valid
GlobalSign Atlas R46 EV TLS CA 2026 Q4 GlobalSign nv-sa2028-07-21Valid
GlobalSign Atlas R46 OV TLS CA 2026 Q4 GlobalSign nv-sa2028-07-21Valid
CrowdStrike GCC R46 OV TLS CA 2026 GlobalSign nv-sa2029-06-23Valid
GlobalSign TLS Root R41 GlobalSign nv-sa2041-03-31Valid
CrowdStrike Atlas R46 OV TLS CA 2026 GlobalSign nv-sa2029-05-19Valid
GlobalSign Atlas R46 DV TLS CA 2026 Q3 GlobalSign nv-sa2028-04-22Valid
GlobalSign Atlas R46 EV TLS CA 2026 Q3 GlobalSign nv-sa2028-04-22Valid
GlobalSign Atlas R46 OV TLS CA 2026 Q3 GlobalSign nv-sa2028-04-22Valid
GlobalSign Atlas R46 AlphaSSL CA 2026 Q3 GlobalSign nv-sa2028-04-22Valid

Cross-signed versions

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

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

CRL and OCSP addresses

In the root certificate

GlobalSign Root R46 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/rootr46.crl

Used by the intermediates it issued

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

  • CRL: http://crl.globalsign.com/rootr46.crl (54)
  • OCSP: http://ocsp.globalsign.com/rootr46 (54)

What happens when it expires

GlobalSign Root R46 is valid until 2046-03-20, about 19.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.

Check whether your device trusts it

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

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 53A2B04BCA6BD645E6398A8EC40DD2BF77C3A290

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

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 "4F:A3:12:6D:8D:3A:11:D1:C4:85:5A:4F:80:7C:BA:D6:CF:91:9D:3A:5A:88:B0:3B:EA:2C:63:72:D9:3C:40:C9"

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 R46.

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-r46.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=4F:A3:12:6D:8D:3A:11:D1:C4:85:5A:4F:80:7C:BA:D6:CF:91:9D:3A:5A:88:B0:3B:EA:2C:63:72:D9:3C:40:C9

FAQ

Is GlobalSign Root R46 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.

When does GlobalSign Root R46 expire?

On 2046-03-20, about 19.4 years after the 2026-11-10 data snapshot.

How many intermediate certificates has GlobalSign Root R46 issued?

The CCADB lists 74: 54 valid, 14 expired and 6 revoked. The newest valid one is GlobalSign Atlas R46 EV TLS CA 2027 H1, valid until 2029-10-21.

Is GlobalSign Root R46 cross-signed?

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