Root certificate · SECOM Trust Systems
SECOM TLS ECC Root CA 2024
SECOM TLS ECC Root CA 2024 is a root CA certificate operated by SECOM Trust Systems (ECDSA P-384, valid until 2049-01-14, SHA-256 6AB2AB75). As of the latest CCADB data it is trusted for TLS server authentication by 3 of 4 major root stores: Mozilla, Apple, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Not included Not included | No | — | No |
| Mozilla | Included Included | Yes | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | No |
Mozilla treats it as an EV root for policy OID 2.23.140.1.1.
Not included Chrome
- Status
- Not included
Included Mozilla
- Status
- Included
- Trust bits
- Websites
- EV policy OIDs
- 2.23.140.1.1
- First included in
- 3.126 / 154
- Inclusion bug
- #1943001
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client 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
- SECOM Trust Systems Co., Ltd.
- Subject
- CN=SECOM TLS ECC Root CA 2024,O=SECOM Trust Systems Co.\, Ltd.,C=JP
- SHA-256
6AB2AB75F51CB4F4F0156203FBF6F646232F514BE059F62833308B82B4D72DB1- SHA-1 (Windows thumbprint)
7A1F222D72B2C3198744DB6169E8A64BD70D440E- SPKI SHA-256
294679E0F97FFD474F19567B36382394E1B4960E030975E66353452034A3C5EA- Valid from
- 2024-01-31
- Expires
- 2049-01-14
- Key
- ECDSA P-384
- Signature algorithm
- ecdsa-with-SHA384
- Serial number
817A2CEF8F237A44- Country
- JP
- Trust bits (CCADB)
- Server Authentication, Client Authentication
- EV policy OIDs (CCADB)
- 2.23.140.1.1 · TLS EV capable: Yes
- Test websites
- valid:
https://evecc2024v.secomtrust-verification.com· expired:https://evecc2024e.secomtrust-verification.com· revoked:https://evecc2024r.secomtrust-verification.com - CCADB record
- A011781
- PEM
- secom-tls-ecc-root-ca-2024.pem
Intermediate CAs issued by this root
The CCADB lists 5 intermediate CA certificates signed directly by SECOM TLS ECC Root CA 2024: 3 currently valid, 0 expired and 2 revoked (revoked includes those whose parent was revoked).
Showing 5 of 5: 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 |
|---|---|---|---|
| NII Open Domain CA - G8 ECC | SECOM Trust Systems Co., Ltd. | 2029-06-05 | Valid |
| SECOM Passport for Web OV ECC CA 2024 | SECOM Trust Systems Co., Ltd. | 2039-01-12 | Valid |
| SECOM Passport for Web EV ECC CA 2024 | SECOM Trust Systems Co., Ltd. | 2039-01-12 | Valid |
| Cybertrust iTrust EV TLS ECCP384 CA 2025 E1 | Cybertrust Japan Co., Ltd. | 2029-07-31 | Revoked |
| Cybertrust iTrust OV TLS ECCP384 CA 2025 E1 | Cybertrust Japan Co., Ltd. | 2029-07-31 | Revoked |
Cross-signed versions
1 certificate(s) in the CCADB have the same subject and public key as SECOM TLS ECC Root CA 2024 but a different issuer. A server can send one of them so that clients which trust the issuing root, but not SECOM TLS ECC Root CA 2024, can still build a chain.
| Signed by | CA owner | Expires | Status |
|---|---|---|---|
| Security Communication ECC RootCA1 crt.sh | SECOM Trust Systems Co., Ltd. | 2038-01-18 | Valid |
CRL and OCSP addresses
In the root certificate
SECOM TLS ECC Root CA 2024 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://repo1.secomtrust.net/root/tlsecc/tlseccrootca2024.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 3 valid intermediates signed by SECOM TLS ECC Root CA 2024; the number in brackets is how many of them use each address.
- CRL:
http://repo1.secomtrust.net/root/tlsecc/tlseccrootca2024.crl(3) - OCSP:
http://tlseccrootca2024.ocsp.secom-cert.jp(3)
What happens when it expires
SECOM TLS ECC Root CA 2024 is valid until 2049-01-14, about 22.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 SECOM TLS ECC Root CA 2024 by common name (SECOM TLS ECC Root CA 2024) 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 "SECOM TLS ECC Root CA 2024" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 6AB2AB75F51CB4F4F0156203FBF6F646232F514BE059F62833308B82B4D72DB1Windows (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 7A1F222D72B2C3198744DB6169E8A64BD70D440ELinux (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 "SECOM TLS ECC Root CA 2024"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "SECOM TLS ECC Root CA 2024"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 "6A:B2:AB:75:F5:1C:B4:F4:F0:15:62:03:FB:F6:F6:46:23:2F:51:4B:E0:59:F6:28:33:30:8B:82:B4:D7:2D:B1"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 SECOM Trust Systems Co., Ltd. → SECOM TLS ECC Root CA 2024.
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 secom-tls-ecc-root-ca-2024.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=6A:B2:AB:75:F5:1C:B4:F4:F0:15:62:03:FB:F6:F6:46:23:2F:51:4B:E0:59:F6:28:33:30:8B:82:B4:D7:2D:B1FAQ
Is SECOM TLS ECC Root CA 2024 trusted by Chrome, Firefox, Safari and Windows?
As of 2026-11-10, Mozilla, Apple, Microsoft trust it for TLS server authentication; Chrome do not.
When does SECOM TLS ECC Root CA 2024 expire?
On 2049-01-14, about 22.2 years after the 2026-11-10 data snapshot.
How many intermediate certificates has SECOM TLS ECC Root CA 2024 issued?
The CCADB lists 5: 3 valid, 0 expired and 2 revoked. The newest valid one is NII Open Domain CA - G8 ECC, valid until 2029-06-05.
Is SECOM TLS ECC Root CA 2024 cross-signed?
Yes. The CCADB has 1 cross-certificate(s) with its subject and key, signed by Security Communication ECC RootCA1; 1 of them are still valid.
Other roots from SECOM Trust Systems
- SECOM TLS RSA Root CA 2024 RSA 4096 · 2049-01-14
- Security Communication ECC RootCA1 ECDSA P-384 · 2038-01-18
- Security Communication RootCA2 RSA 2048 · 2029-05-29
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