Root certificate · SwissSign AG

SwissSign Gold CA - G2

SwissSign Gold CA - G2 is a root CA certificate operated by SwissSign AG (RSA 4096, valid until 2036-10-25, SHA-256 62DD0BE9). 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
MozillaIncluded IncludedNo—No
AppleIncluded IncludedYes—No
MicrosoftIncluded IncludedYes—Yes

The CCADB lists EV policy OID 2.23.140.1.1, 2.16.756.1.89.1.2.1.1 for this root, but Mozilla does not mark it as EV-enabled.

Removed Chrome

Status
Removed

Included Mozilla

Status
Included
Trust bits
Email
EV policy OIDs
not EV-enabled
First included in
NSS 3.11.9 / Firefox 2
Inclusion bug
#343756

Included Apple

Status
Included
Trust bits
serverAuth, clientAuth, emailProtection

Included Microsoft

Status
Included
Trusted EKUs
Server Authentication, Client Authentication, Code Signing, Secure Email
Not-before cutoff
2021-08-01 (Code 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
SwissSign AG
Subject
CN=SwissSign Gold CA - G2,O=SwissSign AG,C=CH
SHA-256
62DD0BE9B9F50A163EA0F8E75C053B1ECA57EA55C8688F647C6881F2C8357B95
SHA-1 (Windows thumbprint)
D8C5388AB7301B1B6ED47AE645253A6F9F1A2761
SPKI SHA-256
40FCFC28875DCCBFEBCBDF6CD7433312DA63C4EFCF3BD7B1B505C22020AE0274
Valid from
2006-10-25
Expires
2036-10-25
Key
RSA 4096
Signature algorithm
sha1WithRSAEncryption
Serial number
BB401C43F55E4FB0
Country
CH
Trust bits (CCADB)
Server Authentication, Client Authentication, Secure Email
EV policy OIDs (CCADB)
2.23.140.1.1, 2.16.756.1.89.1.2.1.1 · TLS EV capable: Yes
Test websites
valid: https://ev-rsa-tls-2022-valid-cert-demo.swisssign.com · expired: https://ev-rsa-tls-2022-expired-cert-demo.swisssign.com · revoked: https://ev-rsa-tls-2022-revoked-cert-demo.swisssign.com
CCADB record
A000203
PEM
swisssign-gold-ca-g2.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 23 intermediate CA certificates signed directly by SwissSign Gold CA - G2: 3 currently valid, 1 expired and 19 revoked (revoked includes those whose parent was revoked).

Showing 20 of 23: 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
SwissSign RSA SMIME Root CA 2022 - 1 SwissSign AG2036-09-22Valid
SwissSign RSA TLS Root CA 2022 - 1 → SwissSign RSA TLS Root CA 2022 - 1 SwissSign AG2036-09-22Valid
SwissSign RSA SMIME Root CA 2021 - 1 SwissSign AG2036-10-23Valid
Trend Micro Gold CA SwissSign AG2017-11-01Expired
SwissSign RSA TLS Root CA 2021 - 1 SwissSign AG2036-10-23Revoked
SwissSign CH Person Gold CA 2017 - G22 SwissSign AG2032-12-18Revoked
SwissSign Personal Gold CA 2014 - G22 SwissSign AG2029-09-15Revoked
SwissSign Server Gold CA 2014 - G22 SwissSign AG2029-09-15Revoked
SwissSign EV Gold CA 2014 - G22 SwissSign AG2035-03-04Revoked
SwissSign Personal Gold CA 2014 - G22 SwissSign AG2029-09-11Revoked
SwissSign Server Gold CA 2014 - G22 SwissSign AG2029-09-11Revoked
PKI SwissPost EXT Machine CA TEST SwissSign AG2026-04-02Revoked
PKI SwissPost EXT Machine CA SwissSign AG2026-04-02Revoked
Nestle External CA SwissSign AG2018-02-10Revoked
AffirmTrust Networking → AffirmTrust Networking SwissSign AG2019-11-02Revoked
AffirmTrust Commercial → AffirmTrust Commercial SwissSign AG2019-11-02Revoked
Trend Micro Gold CA SwissSign AG2019-11-01Revoked
Trend Micro Gold CA SwissSign AG2019-11-02Revoked
AffirmTrust Networking SwissSign AG2019-11-01Revoked
SwissSign EV Gold CA 2009 - G2 SwissSign AG2024-06-06Revoked

Cross-signed versions

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

CRL and OCSP addresses

In the root certificate

SwissSign Gold 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/5B257B96A465517EB839F3C078665EE83AE7F0EE

Used by the intermediates it issued

Addresses found in the CRL Distribution Points and OCSP fields of the 3 valid intermediates signed by SwissSign Gold CA - G2; the number in brackets is how many of them use each address.

  • CRL: http://crl.swisssign.net/5B257B96A465517EB839F3C078665EE83AE7F0EE (3)
  • CRL: ldap://directory.swisssign.net/CN=5B257B96A465517EB839F3C078665EE83AE7F0EE%2CO=SwissSign%2CC=CH?certificateRevocationList?base?objectClass=cRLDistributionPoint (1)

None of the valid intermediates under this root lists an OCSP responder.

What happens when it expires

SwissSign Gold 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 Gold CA - G2 by common name (SwissSign Gold 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 Gold CA - G2" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 62DD0BE9B9F50A163EA0F8E75C053B1ECA57EA55C8688F647C6881F2C8357B95

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 D8C5388AB7301B1B6ED47AE645253A6F9F1A2761

Linux (ca-certificates follows Mozilla: 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 "SwissSign Gold CA - G2"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "SwissSign Gold 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 "62:DD:0B:E9:B9:F5:0A:16:3E:A0:F8:E7:5C:05:3B:1E:CA:57:EA:55:C8:68:8F:64:7C:68:81:F2:C8:35:7B:95"

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 Gold 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-gold-ca-g2.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=62:DD:0B:E9:B9:F5:0A:16:3E:A0:F8:E7:5C:05:3B:1E:CA:57:EA:55:C8:68:8F:64:7C:68:81:F2:C8:35:7B:95

FAQ

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

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

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

The CCADB lists 23: 3 valid, 1 expired and 19 revoked. The newest valid one is SwissSign RSA SMIME Root CA 2022 - 1, valid until 2036-09-22.

Is SwissSign Gold 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