Root certificate · SwissSign AG

SwissSign Silver CA - G2

SwissSign Silver CA - G2 is a root CA certificate operated by SwissSign AG (RSA 4096, valid until 2036-10-25, SHA-256 BE6C4DA2). 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
MozillaRemoved RemovedNo—No
AppleIncluded IncludedYes—No
MicrosoftIncluded (NotBefore cutoff) Included (NotBefore cutoff)Yes—Yes

The CCADB lists no EV policy OID for SwissSign Silver CA - G2.

Removed Chrome

Status
Removed

Removed Mozilla

Status
Removed

Included Apple

Status
Included
Trust bits
serverAuth, clientAuth, emailProtection

Included (NotBefore cutoff) Microsoft

Status
Included (NotBefore cutoff)
Trusted EKUs
Server Authentication, Client Authentication, Code 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
SwissSign AG
Subject
CN=SwissSign Silver CA - G2,O=SwissSign AG,C=CH
SHA-256
BE6C4DA2BBB9BA59B6F3939768374246C3C005993FA98F020D1DEDBED48A81D5
SHA-1 (Windows thumbprint)
9BAAE59F56EE21CB435ABE2593DFA7F040D11DCB
SPKI SHA-256
9318226F8C83AFE47F5F47C24F59CE12DBA8C73B181BEE6B2EA1F40A06BC1869
Valid from
2006-10-25
Expires
2036-10-25
Key
RSA 4096
Signature algorithm
sha1WithRSAEncryption
Serial number
4F1BD42F54BB2F4B
Country
CH
Trust bits (CCADB)
Server Authentication, Client Authentication, Secure Email
EV policy OIDs (CCADB)
not EV-enabled · TLS EV capable: No
CCADB record
A000205
PEM
swisssign-silver-ca-g2.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 12 intermediate CA certificates signed directly by SwissSign Silver CA - G2: 0 currently valid, 2 expired and 10 revoked (revoked includes those whose parent was revoked).

Showing 12 of 12: 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
AffirmTrust Networking SwissSign AG2017-11-01Expired
Trend Micro Silver CA SwissSign AG2017-11-01Expired
SwissSign Personal Silver CA 2014 - G22 SwissSign AG2029-09-15Revoked
SwissSign Server Silver CA 2014 - G22 SwissSign AG2029-09-15Revoked
SwissSign Server Silver CA 2014 - G22 SwissSign AG2029-09-11Revoked
SwissSign Personal Silver CA 2014 - G22 SwissSign AG2029-09-11Revoked
DOUGLAS Group CA - G1 SwissSign AG2026-09-29Revoked
Helsana Gruppe Service ICA 01 SwissSign AG2023-03-21Revoked
AffirmTrust Networking → AffirmTrust Networking SwissSign AG2019-11-02Revoked
Trend Micro Silver CA SwissSign AG2019-11-02Revoked
SwissSign Personal Silver CA 2008 - G2 SwissSign AG2023-07-09Revoked
SwissSign Server Silver CA 2008 - G2 SwissSign AG2023-07-07Revoked

Cross-signed versions

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

CRL and OCSP addresses

In the root certificate

SwissSign Silver CA - G2 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.swisssign.net/17A0CDC1E441B63A5B3BCB459DBD1CC298FA8658

What happens when it expires

SwissSign Silver CA - G2 is valid until 2036-10-25, about 10.0 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 SwissSign Silver CA - G2 by common name (SwissSign Silver CA - G2) 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 "SwissSign Silver CA - G2" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: BE6C4DA2BBB9BA59B6F3939768374246C3C005993FA98F020D1DEDBED48A81D5

Windows (Microsoft store: Included (NotBefore cutoff) · 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 9BAAE59F56EE21CB435ABE2593DFA7F040D11DCB

Linux (ca-certificates follows Mozilla: Removed)

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

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 "BE:6C:4D:A2:BB:B9:BA:59:B6:F3:93:97:68:37:42:46:C3:C0:05:99:3F:A9:8F:02:0D:1D:ED:BE:D4:8A:81:D5"

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 SwissSign AG → SwissSign Silver CA - G2.

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 swisssign-silver-ca-g2.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=BE:6C:4D:A2:BB:B9:BA:59:B6:F3:93:97:68:37:42:46:C3:C0:05:99:3F:A9:8F:02:0D:1D:ED:BE:D4:8A:81:D5

FAQ

Is SwissSign Silver CA - G2 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 SwissSign Silver CA - G2 expire?

On 2036-10-25, about 10.0 years after the 2026-11-10 data snapshot.

How many intermediate certificates has SwissSign Silver CA - G2 issued?

The CCADB lists 12: 0 valid, 2 expired and 10 revoked.

Is SwissSign Silver CA - G2 cross-signed?

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

Other roots from SwissSign AG

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