Root certificate · SECOM Trust Systems

SECOM TLS RSA Root CA 2024

SECOM TLS RSA Root CA 2024 is a root CA certificate operated by SECOM Trust Systems (RSA 4096, valid until 2049-01-14, SHA-256 1435F225). As of the latest CCADB data it is trusted for TLS server authentication by 3 of 4 major root stores: Mozilla, Apple, Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeNot included Not includedNo—No
MozillaIncluded IncludedYes—No
AppleIncluded IncludedYes—No
MicrosoftIncluded IncludedYes—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 RSA Root CA 2024,O=SECOM Trust Systems Co.\, Ltd.,C=JP
SHA-256
1435F225C5D252D7A21948CC3CE62AECFA88001E3DD72D1CC3555100EB372F93
SHA-1 (Windows thumbprint)
FB97967CEF8D986306C03BB611F8E01397A298D3
SPKI SHA-256
F0E0B6FBE8B74D4F82D8ED8F8BD6A3D083DC19DB3D2CEDB1061CCB76D848EE7D
Valid from
2024-01-31
Expires
2049-01-14
Key
RSA 4096
Signature algorithm
sha384WithRSAEncryption
Serial number
EE8934D0CB80E0B2
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://evrsa2024v.secomtrust-verification.com · expired: https://evrsa2024e.secomtrust-verification.com · revoked: https://evrsa2024r.secomtrust-verification.com
CCADB record
A011780
PEM
secom-tls-rsa-root-ca-2024.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 7 intermediate CA certificates signed directly by SECOM TLS RSA Root CA 2024: 5 currently valid, 0 expired and 2 revoked (revoked includes those whose parent was revoked).

Showing 7 of 7: 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
NII Open Domain CA - G8 RSA SECOM Trust Systems Co., Ltd.2040-08-21Valid
SECOM Passport for Web EV RSA CA 2024 SECOM Trust Systems Co., Ltd.2039-01-12Valid
SECOM Passport for Web OV RSA CA 2024 SECOM Trust Systems Co., Ltd.2039-01-12Valid
JPRS OV RSA CA 2024 G1 Japan Registry Services Co., Ltd.2039-01-12Valid
JPRS DV RSA CA 2024 G1 Japan Registry Services Co., Ltd.2039-01-12Valid
Cybertrust iTrust EV TLS RSA4096 CA 2025 E1 Cybertrust Japan Co., Ltd.2029-07-31Revoked
Cybertrust iTrust OV TLS RSA4096 CA 2025 E1 Cybertrust Japan Co., Ltd.2029-07-31Revoked

Cross-signed versions

1 certificate(s) in the CCADB have the same subject and public key as SECOM TLS RSA 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 RSA Root CA 2024, can still build a chain.

Signed byCA ownerExpiresStatus
Security Communication RootCA2 crt.sh SECOM Trust Systems Co., Ltd.2029-05-29Valid

CRL and OCSP addresses

In the root certificate

SECOM TLS RSA 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/tlsrsa/tlsrsarootca2024.crl

Used by the intermediates it issued

Addresses found in the CRL Distribution Points and OCSP fields of the 5 valid intermediates signed by SECOM TLS RSA Root CA 2024; the number in brackets is how many of them use each address.

  • CRL: http://repo1.secomtrust.net/root/tlsrsa/tlsrsarootca2024.crl (5)
  • OCSP: http://tlsrsarootca2024.ocsp.secom-cert.jp (5)

What happens when it expires

SECOM TLS RSA 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 RSA Root CA 2024 by common name (SECOM TLS RSA 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 RSA Root CA 2024" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 1435F225C5D252D7A21948CC3CE62AECFA88001E3DD72D1CC3555100EB372F93

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 FB97967CEF8D986306C03BB611F8E01397A298D3

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 "SECOM TLS RSA 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 RSA 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 "14:35:F2:25:C5:D2:52:D7:A2:19:48:CC:3C:E6:2A:EC:FA:88:00:1E:3D:D7:2D:1C:C3:55:51:00:EB:37:2F:93"

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 RSA 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.

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 secom-tls-rsa-root-ca-2024.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=14:35:F2:25:C5:D2:52:D7:A2:19:48:CC:3C:E6:2A:EC:FA:88:00:1E:3D:D7:2D:1C:C3:55:51:00:EB:37:2F:93

FAQ

Is SECOM TLS RSA 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 RSA 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 RSA Root CA 2024 issued?

The CCADB lists 7: 5 valid, 0 expired and 2 revoked. The newest valid one is NII Open Domain CA - G8 RSA, valid until 2040-08-21.

Is SECOM TLS RSA Root CA 2024 cross-signed?

Yes. The CCADB has 1 cross-certificate(s) with its subject and key, signed by Security Communication RootCA2; 1 of them are still valid.

Other roots from SECOM Trust Systems

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