Root certificate · SwissSign AG
SwissSign RSA TLS Root CA 2022 - 1
SwissSign RSA TLS Root CA 2022 - 1 is a root CA certificate operated by SwissSign AG (RSA 4096, valid until 2047-06-08, SHA-256 193144F4). As of the latest CCADB data it is trusted for TLS server authentication by 3 of 4 major root stores: Chrome, Mozilla, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Included Included | Yes | 2027-06-14 | Yes |
| Mozilla | Included Included | Yes | — | No |
| Apple | Not included Not included | No | — | No |
| Microsoft | Included Included | Yes | — | No |
Chrome stops trusting TLS certificates under this root whose SCTs are dated after 2027-06-14 (sct_not_after). Mozilla treats it as an EV root for policy OID 2.23.140.1.1.
Included Chrome
- Status
- Included
- Distrust for TLS after
- 2027-06-14
Included Mozilla
- Status
- Included
- Trust bits
- Websites
- EV policy OIDs
- 2.23.140.1.1
- First included in
- 3.114 / 142
Not included Apple
- Status
- Not included
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server 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
- SwissSign AG
- Subject
- CN=SwissSign RSA TLS Root CA 2022 - 1,O=SwissSign AG,C=CH
- SHA-256
193144F431E0FDDB740717D4DE926A571133884B4360D30E272913CBE660CE41- SHA-1 (Windows thumbprint)
81340ABE4CCDCECCE77DCC8AD457E245A0775DCE- SPKI SHA-256
EBC978AE0DD9E5822D6B19652596F620C93D7CAEFA952191CB050A632CA9005F- Valid from
- 2022-06-08
- Expires
- 2047-06-08
- Key
- RSA 4096
- Signature algorithm
- sha256WithRSAEncryption
- Serial number
43FA0C5F4E1B801844EFD1B44F351F44F480EDCB- Country
- CH
- EV policy OIDs (CCADB)
- not EV-enabled · TLS EV capable: Yes
- CCADB record
- A010364
- PEM
- swisssign-rsa-tls-root-ca-2022-1.pem
Intermediate CAs issued by this root
The CCADB lists no intermediate CA certificate signed directly by SwissSign RSA TLS Root CA 2022 - 1.
Cross-signed versions
1 certificate(s) in the CCADB have the same subject and public key as SwissSign RSA TLS Root CA 2022 - 1 but a different issuer. A server can send one of them so that clients which trust the issuing root, but not SwissSign RSA TLS Root CA 2022 - 1, can still build a chain.
| Signed by | CA owner | Expires | Status |
|---|---|---|---|
| SwissSign Gold CA - G2 crt.sh | SwissSign AG | 2036-09-22 | Valid |
CRL and OCSP addresses
In the root certificate
SwissSign RSA TLS Root CA 2022 - 1 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.ch/cdp-9661c29f-9121-4f46-acd8-ead4a22f7160
What happens when it expires
SwissSign RSA TLS Root CA 2022 - 1 is valid until 2047-06-08, about 20.6 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. Root programs can stop trusting it before it expires: Chrome 2027-06-14.
Check whether your device trusts it
Each platform keeps its own root store. The commands below look up SwissSign RSA TLS Root CA 2022 - 1 by common name (SwissSign RSA TLS Root CA 2022 - 1) 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 "SwissSign RSA TLS Root CA 2022 - 1" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 193144F431E0FDDB740717D4DE926A571133884B4360D30E272913CBE660CE41
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 81340ABE4CCDCECCE77DCC8AD457E245A0775DCE
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 "SwissSign RSA TLS Root CA 2022 - 1"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "SwissSign RSA TLS Root CA 2022 - 1"
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 "19:31:44:F4:31:E0:FD:DB:74:07:17:D4:DE:92:6A:57:11:33:88:4B:43:60:D3:0E:27:29:13:CB:E6:60:CE:41"
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 RSA TLS Root CA 2022 - 1.
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.
# 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-rsa-tls-root-ca-2022-1.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=19:31:44:F4:31:E0:FD:DB:74:07:17:D4:DE:92:6A:57:11:33:88:4B:43:60:D3:0E:27:29:13:CB:E6:60:CE:41
FAQ
Is SwissSign RSA TLS Root CA 2022 - 1 trusted by Chrome, Firefox, Safari and Windows?
As of 2026-11-10, Chrome, Mozilla, Microsoft trust it for TLS server authentication; Apple do not. Distrust-after dates already set: Chrome 2027-06-14.
When does SwissSign RSA TLS Root CA 2022 - 1 expire?
On 2047-06-08, about 20.6 years after the 2026-11-10 data snapshot.
How many intermediate certificates has SwissSign RSA TLS Root CA 2022 - 1 issued?
The CCADB lists no intermediate certificate signed directly by SwissSign RSA TLS Root CA 2022 - 1.
Is SwissSign RSA TLS Root CA 2022 - 1 cross-signed?
Yes. The CCADB has 1 cross-certificate(s) with its subject and key, signed by SwissSign Gold CA - G2; 1 of them are still valid.
Other roots from SwissSign AG
- SwissSign Gold CA - G2 RSA 4096 · 2036-10-25
- SwissSign Silver CA - G2 RSA 4096 · 2036-10-25
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