Root certificate · Izenpe S.A.

Izenpe.com

Izenpe.com is a root CA certificate operated by Izenpe S.A. (RSA 4096, valid until 2037-12-13, SHA-256 2530CC8E). As of the latest CCADB data it is trusted for TLS server authentication by 4 of 4 major root stores: Chrome, Mozilla, Apple, Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeIncluded IncludedYes2026-04-14Yes
MozillaIncluded IncludedYes2026-04-15Yes
AppleIncluded IncludedYes—No
MicrosoftIncluded IncludedYes—No

Chrome stops trusting TLS certificates under this root whose SCTs are dated after 2026-04-14 (sct_not_after). Mozilla stops trusting TLS certificates from this root issued after 2026-04-15. Mozilla treats it as an EV root for policy OID 1.3.6.1.4.1.14777.6.1.1, 1.3.6.1.4.1.14777.6.1.2.

Included Chrome

Status
Included
Distrust for TLS after
2026-04-14

Included Mozilla

Status
Included
Distrust for TLS after
2026-04-15
Trust bits
Websites
EV policy OIDs
1.3.6.1.4.1.14777.6.1.1, 1.3.6.1.4.1.14777.6.1.2
First included in
NSS 3.12.9 / Firefox 4.0
Inclusion bug
#361957

Included Apple

Status
Included
Trust bits
serverAuth, clientAuth

Included Microsoft

Status
Included
Trusted EKUs
Server 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
Izenpe S.A.
Subject
CN=Izenpe.com,O=IZENPE S.A.,C=ES
SHA-256
2530CC8E98321502BAD96F9B1FBA1B099E2D299E0F4548BB914F363BC0D4531F
SHA-1 (Windows thumbprint)
2F783D255218A74A653971B52CA29C45156FE919
SPKI SHA-256
952C2039C0243EB515DD73D83FC3643184874FEB0862A9837731ED9B4742E17A
Valid from
2007-12-13
Expires
2037-12-13
Key
RSA 4096
Signature algorithm
sha256WithRSAEncryption
Serial number
B0B75A16485FBFE1CBF58BD719E67D
Country
ES
Trust bits (CCADB)
Server Authentication, Client Authentication
EV policy OIDs (CCADB)
1.3.6.1.4.1.14777.6.1.1, 1.3.6.1.4.1.14777.6.1.2, 2.23.140.1.1 · TLS EV capable: Yes
Test websites
valid: https://test-ev-qualified.izenpe.eus · expired: https://test-expired-ev.izenpe.eus · revoked: https://test-revoked-ev.izenpe.eus
CCADB record
A000161
PEM
izenpe-com.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 17 intermediate CA certificates signed directly by Izenpe.com: 6 currently valid, 3 expired and 8 revoked (revoked includes those whose parent was revoked).

Showing 17 of 17: 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
CA de Certificados SSL EV Izenpe S.A.2028-07-06Valid
EAEko Herri Administrazioen CA - CA AAPP Vascas (2) Izenpe S.A.2037-12-12Valid
Herritar eta Erakundeen CA - CA de Ciudadanos y Entidades (4) Izenpe S.A.2037-12-12Valid
Herritar eta Erakundeen CA - CA de Ciudadanos y Entidades (3) Izenpe S.A.2037-12-12Valid
CA Teknikoa - CA Tecnica Izenpe S.A.2037-12-12Valid
EAEko HAetako langileen CA - CA personal de AAPP vascas (2) Izenpe S.A.2037-12-12Valid
CA de Certificados SSL EV Izenpe S.A.2020-10-20Expired
Eusko Jaurlaritzako langileen CA - CA personal Gobierno Vasco Izenpe S.A.2020-02-11Expired
CA de Certificados SSL EV Izenpe S.A.2018-11-19Expired
CA de Certificados SSL EV Izenpe S.A.2020-10-20Revoked
Eusko Jaurlaritzako langileen CA - CA personal Gobierno Vasco Izenpe S.A.2020-02-11Revoked
EAEko Herri Administrazioen CA - CA AAPP Vascas (2) Izenpe S.A.2037-12-12Revoked
Herritar eta Erakundeen CA - CA de Ciudadanos y Entidades (4) Izenpe S.A.2037-12-12Revoked
EAEko HAetako langileen CA - CA personal de AAPP vascas (2) Izenpe S.A.2037-12-12Revoked
CA Teknikoa - CA Tecnica Izenpe S.A.2037-12-12Revoked
Herritar eta Erakundeen CA - CA de Ciudadanos y Entidades (3) Izenpe S.A.2037-12-12Revoked
Izenpe.com → Izenpe.com Izenpe S.A.2037-12-13Revoked

Cross-signed versions

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

CRL and OCSP addresses

In the root certificate

Izenpe.com 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.izenpe.com/cgi-bin/arl2

Used by the intermediates it issued

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

  • CRL: http://crl.izenpe.com/cgi-bin/arl2 (6)
  • OCSP: http://ocsp.izenpe.com:8094 (5)
  • OCSP: http://ocsp.izenpe.com (1)

What happens when it expires

Izenpe.com is valid until 2037-12-13, about 11.1 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. Root programs can stop trusting it before it expires: Chrome 2026-04-14, Mozilla 2026-04-15.

Check whether your device trusts it

Each platform keeps its own root store. The commands below look up Izenpe.com by common name (Izenpe.com) 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 "Izenpe.com" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 2530CC8E98321502BAD96F9B1FBA1B099E2D299E0F4548BB914F363BC0D4531F

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 2F783D255218A74A653971B52CA29C45156FE919

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

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 "25:30:CC:8E:98:32:15:02:BA:D9:6F:9B:1F:BA:1B:09:9E:2D:29:9E:0F:45:48:BB:91:4F:36:3B:C0:D4:53:1F"

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 IZENPE S.A. → Izenpe.com.

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 izenpe-com.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=25:30:CC:8E:98:32:15:02:BA:D9:6F:9B:1F:BA:1B:09:9E:2D:29:9E:0F:45:48:BB:91:4F:36:3B:C0:D4:53:1F

FAQ

Is Izenpe.com 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. Distrust-after dates already set: Chrome 2026-04-14, Mozilla 2026-04-15.

When does Izenpe.com expire?

On 2037-12-13, about 11.1 years after the 2026-11-10 data snapshot.

How many intermediate certificates has Izenpe.com issued?

The CCADB lists 17: 6 valid, 3 expired and 8 revoked. The newest valid one is CA de Certificados SSL EV, valid until 2028-07-06.

Is Izenpe.com cross-signed?

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

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