Root certificate · e-commerce monitoring (GLOBALTRUST)

GLOBALTRUST

GLOBALTRUST is a root CA certificate operated by e-commerce monitoring (GLOBALTRUST) (RSA 4096, valid until 2036-09-18, SHA-256 5E3571F3). 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—Yes

The CCADB lists no EV policy OID for GLOBALTRUST.

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, Code Signing, Document Signing, Encrypting File System, IP Security IKE Intermediate, IP Security Tunnel Termination, IP Security User, OCSP Signing, Secure Email, Time Stamping
Not-before cutoff
2020-08-01 (Encrypting File System, IP Security End System, IP Security Tunnel Termination, IP Security User)
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
e-commerce monitoring GmbH
Subject
1.2.840.113549.1.9.1=info@globaltrust.info,CN=GLOBALTRUST,OU=GLOBALTRUST Certification Service,O=ARGE DATEN - Austrian Society for Data Protection,ST=Austria,L=Vienna,C=AT
SHA-256
5E3571F33F45A7DF1537A68B5FFB9E036AF9D2F5BC4C9717130DC43D7175AAC7
SHA-1 (Windows thumbprint)
342CD9D3062DA48C346965297F081EBC2EF68FDC
SPKI SHA-256
9E5A34B08929BC0A581C8936AAFD6AB7517BB15188B4F6FC02C45906F71595B0
Valid from
2006-08-07
Expires
2036-09-18
Key
RSA 4096
Signature algorithm
sha1WithRSAEncryption
Serial number
0
Country
AT
Trust bits (CCADB)
Server Authentication, Client Authentication, Code Signing, Document Signing, Secure Email, Time Stamping, IP Security IKE Intermediate
EV policy OIDs (CCADB)
not EV-enabled · TLS EV capable: No
Test websites
valid: https://testok-2006-server-ov-1.e-monitoring.at/ · expired: https://testold-2006-server-ov-1.e-monitoring.at/ · revoked: https://testrevoked-2006-server-ov-1.e-monitoring.at/
CCADB record
A002416
PEM
globaltrust.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 8 intermediate CA certificates signed directly by GLOBALTRUST: 7 currently valid, 1 expired and 0 revoked (revoked includes those whose parent was revoked).

Showing 8 of 8: 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
GLOBALTRUST QUALIFIED TIMESTAMP 2 e-commerce monitoring GmbH2036-09-18Valid
GLOBALTRUST COMPANYCLIENT 1 e-commerce monitoring GmbH2036-09-18Valid
GLOBALTRUST SERVER OV 1 e-commerce monitoring GmbH2036-09-18Valid
GLOBALTRUST QUALIFIED 1 e-commerce monitoring GmbH2036-09-18Valid
GLOBALTRUST ADVANCED 1 e-commerce monitoring GmbH2036-09-18Valid
GLOBALTRUST GOVERNMENT 1 e-commerce monitoring GmbH2036-09-18Valid
GLOBALTRUST CLIENT 1 e-commerce monitoring GmbH2036-09-18Valid
GLOBALTRUST CODESIGNING e-commerce monitoring GmbH2020-12-31Expired

Cross-signed versions

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

CRL and OCSP addresses

In the root certificate

GLOBALTRUST 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)

  • https://www.globaltrust.eu/static/globaltrust2006.crl

Used by the intermediates it issued

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

  • CRL: http://service.globaltrust.eu/static/globaltrust2006.crl (6)
  • CRL: http://www.globaltrust.eu/static/globaltrust2006.crl (1)
  • OCSP: http://ocsp.globaltrust.eu (7)

What happens when it expires

GLOBALTRUST is valid until 2036-09-18, about 9.9 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 GLOBALTRUST by common name (GLOBALTRUST) 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 "GLOBALTRUST" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 5E3571F33F45A7DF1537A68B5FFB9E036AF9D2F5BC4C9717130DC43D7175AAC7

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 342CD9D3062DA48C346965297F081EBC2EF68FDC

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

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 "5E:35:71:F3:3F:45:A7:DF:15:37:A6:8B:5F:FB:9E:03:6A:F9:D2:F5:BC:4C:97:17:13:0D:C4:3D:71:75:AA:C7"

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 ARGE DATEN - Austrian Society for Data Protection → GLOBALTRUST.

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 globaltrust.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=5E:35:71:F3:3F:45:A7:DF:15:37:A6:8B:5F:FB:9E:03:6A:F9:D2:F5:BC:4C:97:17:13:0D:C4:3D:71:75:AA:C7

FAQ

Is GLOBALTRUST 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 GLOBALTRUST expire?

On 2036-09-18, about 9.9 years after the 2026-11-10 data snapshot.

How many intermediate certificates has GLOBALTRUST issued?

The CCADB lists 8: 7 valid, 1 expired and 0 revoked. The newest valid one is GLOBALTRUST QUALIFIED TIMESTAMP 2, valid until 2036-09-18.

Is GLOBALTRUST cross-signed?

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

Other roots from e-commerce monitoring (GLOBALTRUST)

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