Root certificate · certSIGN
certSIGN ROOT CA
certSIGN ROOT CA is a root CA certificate operated by certSIGN (RSA 2048, valid until 2031-07-04, SHA-256 EAA962C4). As of the latest CCADB data it is trusted for TLS server authentication by 2 of 4 major root stores: Apple, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Removed Removed | No | — | No |
| Mozilla | Removed Removed | No | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included (NotBefore cutoff) Included (NotBefore cutoff) | Yes | — | Yes |
The CCADB lists no EV policy OID for certSIGN ROOT CA.
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, Encrypting File System, IP Security Tunnel Termination, IP Security User, Secure Email, Time Stamping
"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,O=certSIGN,C=RO
- SHA-256
EAA962C4FA4A6BAFEBE415196D351CCD888D4F53F3FA8AE6D7C466A94E6042BB- SHA-1 (Windows thumbprint)
FAB7EE36972662FB2DB02AF6BF03FDE87C4B2F9B- SPKI SHA-256
DBC1E3A15238A0483BCDB8FDEC616E03E705A48E2A501157CADF3B9C7311C5E5- Valid from
- 2006-07-04
- Expires
- 2031-07-04
- Key
- RSA 2048
- Signature algorithm
- sha1WithRSAEncryption
- Serial number
200605167002- Country
- RO
- Trust bits (CCADB)
- Server Authentication, Client Authentication, Secure Email
- EV policy OIDs (CCADB)
- not EV-enabled · TLS EV capable: No
- Test websites
- valid:
https://testssl-valid.certsign.ro/· expired:https://testssl-expired.certsign.ro/· revoked:https://testssl-revoked.certsign.ro/ - CCADB record
- A000100
- PEM
- certsign-root-ca.pem
Intermediate CAs issued by this root
The CCADB lists 16 intermediate CA certificates signed directly by certSIGN ROOT CA: 0 currently valid, 13 expired and 3 revoked (revoked includes those whose parent was revoked).
Showing 16 of 16: 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.
Cross-signed versions
No certificate in the CCADB has the same subject and public key as certSIGN ROOT CA with a different issuer, so a client has to carry certSIGN ROOT CA itself in its root store to trust it.
CRL and OCSP addresses
In the root certificate
certSIGN ROOT CA 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/root.crl
What happens when it expires
certSIGN ROOT CA is valid until 2031-07-04, about 4.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.
Check whether your device trusts it
Each platform keeps its own root store. The commands below look up certSIGN ROOT CA by common name (certSIGN 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: 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" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: EAA962C4FA4A6BAFEBE415196D351CCD888D4F53F3FA8AE6D7C466A94E6042BB
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 FAB7EE36972662FB2DB02AF6BF03FDE87C4B2F9B
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 "certSIGN ROOT CA"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "certSIGN 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 "EA:A9:62:C4:FA:4A:6B:AF:EB:E4:15:19:6D:35:1C:CD:88:8D:4F:53:F3:FA:8A:E6:D7:C4:66:A9:4E:60:42:BB"
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 → certSIGN 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.
# 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.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=EA:A9:62:C4:FA:4A:6B:AF:EB:E4:15:19:6D:35:1C:CD:88:8D:4F:53:F3:FA:8A:E6:D7:C4:66:A9:4E:60:42:BB
FAQ
Is certSIGN ROOT CA 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 certSIGN ROOT CA expire?
On 2031-07-04, about 4.6 years after the 2026-11-10 data snapshot.
How many intermediate certificates has certSIGN ROOT CA issued?
The CCADB lists 16: 0 valid, 13 expired and 3 revoked.
Is certSIGN ROOT CA 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 G2 RSA 4096 · 2042-02-06
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