Root certificate · ComSign

ComSign Global Root CA

ComSign Global Root CA is a root CA certificate operated by ComSign (RSA 4096, valid until 2036-07-16, SHA-256 2605875A). As of the latest CCADB data it is trusted for TLS server authentication by 1 of 4 major root stores: Microsoft.

Data updated Nov 10, 2026

Root store status

Root store	Status	Trusted for TLS	Distrust for TLS after	Constrained
Chrome	Not included Not included	No	—	No
Mozilla	Not included Not included	No	—	No
Apple	Blocked Blocked	No	—	No
Microsoft	Included Included	Yes	—	Yes

The CCADB lists no EV policy OID for ComSign Global Root CA.

Not included Chrome

Status: Not included

Not included Mozilla

Status: Not included

Blocked Apple

Status: Blocked

Included Microsoft

Status: Included
Trusted EKUs: Server Authentication, Client Authentication, OCSP Signing, Secure Email, Time Stamping
Not-before cutoff: 2026-05-19 (OCSP Signing, Secure Email)

"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: ComSign
Subject: C=IL,O=ComSign Ltd.,CN=ComSign Global Root CA
SHA-256: 2605875AFCC176B2D66DD66A995D7F8D5EBB86CE120D0E7E9E7C6EF294A27D4C
SHA-1 (Windows thumbprint): AE3B31BF8FD891079CF1DF34CBCE6E70D37FB5B0
SPKI SHA-256: C06C872FC2D0AC08D78D421981FBDA4E35500D0946F79894EDD21AC29DEC0719
Valid from: 2011-07-18
Expires: 2036-07-16
Key: RSA 4096
Signature algorithm: sha256WithRSAEncryption
Serial number: 8F617115BA7958178C7D113AACD6DBAE
Country: IL
Trust bits (CCADB): Server Authentication, Client Authentication, Time Stamping
EV policy OIDs (CCADB): not EV-enabled · TLS EV capable: No
Test websites: valid: https://fedir.comsign.co.il/test.html · expired: https://expired.comsign.co.uk/test.html · revoked: https://revoked.comsign.co.uk/test.html
CCADB record: A002501
PEM: comsign-global-root-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 6 intermediate CA certificates signed directly by ComSign Global Root CA: 6 currently valid, 0 expired and 0 revoked (revoked includes those whose parent was revoked).

Showing 6 of 6: 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.

Intermediate	Operated by	Expires	Status
ComSign Professionals CA	ComSign	2034-05-08	Valid
ComSign Corporations CA	ComSign	2034-05-08	Valid
ComSign IDF CA	ComSign	2034-05-08	Valid
Comsign eIDAS CA	ComSign	2031-07-12	Valid
ComSign Organizational CA	ComSign	2028-11-07	Valid
ComSign ISA Global CA	ComSign	2028-11-07	Valid

Cross-signed versions

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

CRL and OCSP addresses

In the root certificate

CRL: http://fedir.comsign.co.il/crl/comsignglobalrootca.crl
CRL: http://crl1.comsign.co.il/crl/comsignglobalrootca.crl

Full CRL this CA publishes (CCADB)

http://crl1.comsign.co.il/crl/comsignglobalrootca.crl

Used by the intermediates it issued

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

CRL: http://crl1.comsign.co.il/crl/ComSignGlobalRootCA.crl (5)
CRL: http://fedir.comsign.co.il/crl/ComSignGlobalRootCA.crl (5)
CRL: http://crl1.comsign.co.il/crl/comsignrootglobalca.crl (1)
CRL: http://fedir.comsign.co.il/crl/comsignrootglobalca.crl (1)
OCSP: http://ocsp1.comsign.co.il/ocsp (3)

What happens when it expires

ComSign Global Root CA is valid until 2036-07-16, about 9.7 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 ComSign Global Root CA by common name (ComSign Global 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: Blocked)

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 "ComSign Global Root CA" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 2605875AFCC176B2D66DD66A995D7F8D5EBB86CE120D0E7E9E7C6EF294A27D4C

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 AE3B31BF8FD891079CF1DF34CBCE6E70D37FB5B0

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 "ComSign Global Root CA"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "ComSign Global 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 "26:05:87:5A:FC:C1:76:B2:D6:6D:D6:6A:99:5D:7F:8D:5E:BB:86:CE:12:0D:0E:7E:9E:7C:6E:F2:94:A2:7D:4C"

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 ComSign Ltd. → ComSign Global 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 comsign-global-root-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=26:05:87:5A:FC:C1:76:B2:D6:6D:D6:6A:99:5D:7F:8D:5E:BB:86:CE:12:0D:0E:7E:9E:7C:6E:F2:94:A2:7D:4C

FAQ

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

On 2036-07-16, about 9.7 years after the 2026-11-10 data snapshot.

How many intermediate certificates has ComSign Global Root CA issued?

The CCADB lists 6: 6 valid, 0 expired and 0 revoked. The newest valid one is ComSign Professionals CA, valid until 2034-05-08.

Is ComSign Global Root CA cross-signed?

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

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