Root certificate · certSIGN
certSIGN ROOT CA G2
certSIGN ROOT CA G2 is a root CA certificate operated by certSIGN (RSA 4096, valid until 2042-02-06, SHA-256 657CFE2F). As of the latest CCADB data it is trusted for TLS server authentication by 4 of 4 major root stores: Chrome, Mozilla, Apple, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Included Included | Yes | — | No |
| Mozilla | Included Included | Yes | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | Yes |
Mozilla treats it as an EV root for policy OID 2.23.140.1.1.
Included Chrome
- Status
- Included
Included Mozilla
- Status
- Included
- Trust bits
- Websites
- EV policy OIDs
- 2.23.140.1.1
- First included in
- NSS 3.54 / Firefox 79
- Inclusion bug
- #1403453
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth, emailProtection
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client Authentication, Document Signing, Secure Email
- Not-before cutoff
- 2025-09-15 (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
- certSIGN
- Subject
- OU=certSIGN ROOT CA G2,O=CERTSIGN SA,C=RO
- SHA-256
657CFE2FA73FAA38462571F332A2363A46FCE7020951710702CDFBB6EEDA3305- SHA-1 (Windows thumbprint)
26F993B4ED3D2827B0B94BA7E9151DA38D92E532- SPKI SHA-256
CBAD7B1D384849DF0946B7EE8E7F5F7CE3AED876FDA7BC9D30D8B16F29FF2C53- Valid from
- 2017-02-06
- Expires
- 2042-02-06
- Key
- RSA 4096
- Signature algorithm
- sha256WithRSAEncryption
- Serial number
110034B64EC6362D36- Country
- RO
- Trust bits (CCADB)
- Server Authentication, Client Authentication, Document Signing, Secure Email
- EV policy OIDs (CCADB)
- 2.23.140.1.1 · TLS EV capable: Yes
- Test websites
- valid:
https://testssl-valid-evcp-g2.certsign.ro/· expired:https://testssl-expired-evcp-g2.certsign.ro/· revoked:https://testssl-revoked-evcp-g2.certsign.ro/ - CCADB record
- A004907
- PEM
- certsign-root-ca-g2.pem
Intermediate CAs issued by this root
The CCADB lists 8 intermediate CA certificates signed directly by certSIGN ROOT CA G2: 5 currently valid, 0 expired and 3 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.
| Intermediate | Operated by | Expires | Status |
|---|---|---|---|
| certSIGN Web CA G4 EV | certSIGN | 2032-09-08 | Valid |
| certSIGN Web CA G4 DV | certSIGN | 2032-09-08 | Valid |
| certSIGN Web CA G4 OV | certSIGN | 2032-09-08 | Valid |
| certSIGN Web CA | certSIGN | 2027-02-06 | Valid |
| certSIGN Web CA G2 | certSIGN | 2033-01-21 | Valid |
| certSIGN Web CA | certSIGN | 2027-02-06 | Revoked |
| certSIGN Qualified CA | certSIGN | 2027-02-06 | Revoked |
| certSIGN Public CA | certSIGN | 2027-02-06 | Revoked |
Cross-signed versions
No certificate in the CCADB has the same subject and public key as certSIGN ROOT CA G2 with a different issuer, so a client has to carry certSIGN ROOT CA G2 itself in its root store to trust it.
CRL and OCSP addresses
In the root certificate
certSIGN ROOT 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.certsign.ro/certsign-rootg2.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 5 valid intermediates signed by certSIGN ROOT CA G2; the number in brackets is how many of them use each address.
- CRL:
http://pkipro.certsign.ro/certsign-rootg2.crl(4) - CRL:
http://crl.certsign.ro/certsign-rootg2.crl(1) - OCSP:
http://ocsp.certsign.ro(5)
What happens when it expires
certSIGN ROOT CA G2 is valid until 2042-02-06, about 15.2 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 certSIGN ROOT CA G2 by common name (certSIGN ROOT 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 "certSIGN ROOT CA G2" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 657CFE2FA73FAA38462571F332A2363A46FCE7020951710702CDFBB6EEDA3305Windows (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 26F993B4ED3D2827B0B94BA7E9151DA38D92E532Linux (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 "certSIGN ROOT CA G2"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "certSIGN ROOT 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 "65:7C:FE:2F:A7:3F:AA:38:46:25:71:F3:32:A2:36:3A:46:FC:E7:02:09:51:71:07:02:CD:FB:B6:EE:DA:33:05"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 CERTSIGN SA → certSIGN ROOT 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.
# 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 certsign-root-ca-g2.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=65:7C:FE:2F:A7:3F:AA:38:46:25:71:F3:32:A2:36:3A:46:FC:E7:02:09:51:71:07:02:CD:FB:B6:EE:DA:33:05FAQ
Is certSIGN ROOT CA G2 trusted by Chrome, Firefox, Safari and Windows?
Yes. As of 2026-11-10, Chrome, Mozilla (Firefox), Apple (Safari) and Microsoft (Windows) all trust it for TLS server authentication.
When does certSIGN ROOT CA G2 expire?
On 2042-02-06, about 15.2 years after the 2026-11-10 data snapshot.
How many intermediate certificates has certSIGN ROOT CA G2 issued?
The CCADB lists 8: 5 valid, 0 expired and 3 revoked. The newest valid one is certSIGN Web CA G4 EV, valid until 2032-09-08.
Is certSIGN ROOT CA G2 cross-signed?
No. The CCADB has no certificate with the same subject and public key signed by another CA.
Other roots from certSIGN
- certSIGN ROOT CA RSA 2048 · 2031-07-04
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