Root certificate · EDICOM

CAEDICOM Root

CAEDICOM Root is a root CA certificate operated by EDICOM (RSA 4096, valid until 2034-05-21, SHA-256 1501F89C). As of the latest CCADB data it is trusted for TLS server authentication by 1 of 4 major root stores: Microsoft.

Data updated Nov 10, 2026

Root store status

Root store	Status	Trusted for TLS	Distrust for TLS after	Constrained
Chrome	Not included Not included	No	—	No
Mozilla	Not included Not included	No	—	No
Apple	Not included Not included	No	—	No
Microsoft	Included Included	Yes	—	Yes

The CCADB lists no EV policy OID for CAEDICOM Root.

Not included Chrome

Status: Not included

Not included Mozilla

Status: Not included

Not included Apple

Status: Not included

Included Microsoft

Status: Included
Trusted EKUs: Server Authentication, Client Authentication, Code Signing, Document Signing, Secure Email, Time Stamping
Not-before cutoff: 2025-09-15 (Code Signing, 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: EDICOM
Subject: C=ES,O=EDICOM,CN=CAEDICOM Root
SHA-256: 1501F89C5C4DCF36CF588A17C9FD7CFCEB9EE01E8729BE355E25DE80EB6284B4
SHA-1 (Windows thumbprint): 559BBA7B0FFE80D6D3829B1FD07AA4D322194790
SPKI SHA-256: 9962AB1699B0EB7C7E8A578BC79893042031C1158C633613199A90B9652A2A75
Valid from: 2014-05-21
Expires: 2034-05-21
Key: RSA 4096
Signature algorithm: sha256WithRSAEncryption
Serial number: FB712658AD99E5
Country: ES
Trust bits (CCADB): Server Authentication, Client Authentication, Document Signing, Time Stamping
EV policy OIDs (CCADB): not EV-enabled · TLS EV capable: No
Test websites: valid: https://rootcertificateprograms.edicom.es/ · expired: https://rootcertificateprogramsexpired.edicom.es/ · revoked: https://rootcertificateprogramsrevoked.edicom.es
CCADB record: A003632
PEM: edicom-caedicom-root.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 1 intermediate CA certificates signed directly by CAEDICOM Root: 1 currently valid, 0 expired and 0 revoked (revoked includes those whose parent was revoked).

Showing 1 of 1: 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
CAEDICOM04	EDICOM	2034-05-21	Valid

Cross-signed versions

No certificate in the CCADB has the same subject and public key as CAEDICOM Root with a different issuer, so a client has to carry CAEDICOM Root itself in its root store to trust it.

CRL and OCSP addresses

In the root certificate

CAEDICOM Root 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)

https://acedicom.edicomgroup.com/caedicomroot.crl

Used by the intermediates it issued

Addresses found in the CRL Distribution Points and OCSP fields of the 1 valid intermediates signed by CAEDICOM Root; the number in brackets is how many of them use each address.

CRL: http://acedicom.edicomgroup.com/caedicomroot.crl (1)
OCSP: http://ocsp.acedicom.edicomgroup.com/caedicomroot (1)

What happens when it expires

CAEDICOM Root is valid until 2034-05-21, about 7.5 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 CAEDICOM Root by common name (CAEDICOM Root) 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 "CAEDICOM Root" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 1501F89C5C4DCF36CF588A17C9FD7CFCEB9EE01E8729BE355E25DE80EB6284B4

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 559BBA7B0FFE80D6D3829B1FD07AA4D322194790

Linux (ca-certificates follows Mozilla: Not included)

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 "CAEDICOM Root"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "CAEDICOM Root"

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 "15:01:F8:9C:5C:4D:CF:36:CF:58:8A:17:C9:FD:7C:FC:EB:9E:E0:1E:87:29:BE:35:5E:25:DE:80:EB:62:84:B4"

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 EDICOM → CAEDICOM Root.

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 edicom-caedicom-root.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=15:01:F8:9C:5C:4D:CF:36:CF:58:8A:17:C9:FD:7C:FC:EB:9E:E0:1E:87:29:BE:35:5E:25:DE:80:EB:62:84:B4

FAQ

Is CAEDICOM Root trusted by Chrome, Firefox, Safari and Windows?

As of 2026-11-10, Microsoft trust it for TLS server authentication; Chrome, Mozilla, Apple do not.

When does CAEDICOM Root expire?

On 2034-05-21, about 7.5 years after the 2026-11-10 data snapshot.

How many intermediate certificates has CAEDICOM Root issued?

The CCADB lists 1: 1 valid, 0 expired and 0 revoked. The newest valid one is CAEDICOM04, valid until 2034-05-21.

Is CAEDICOM Root cross-signed?

No. The CCADB has no certificate with the same subject and public key signed by another CA.

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