Root certificate · ACCV (Spain)
ACCVRAIZ1
ACCVRAIZ1 is a root CA certificate operated by ACCV (Spain) (RSA 4096, valid until 2030-12-31, SHA-256 9A6EC012). As of the latest CCADB data it is trusted for TLS server authentication by 4 of 4 major root stores: Chrome, Mozilla, Apple, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Included Included | Yes | — | No |
| Mozilla | Included Included | Yes | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | Yes |
The CCADB lists no EV policy OID for ACCVRAIZ1.
Included Chrome
- Status
- Included
Included Mozilla
- Status
- Included
- Trust bits
- Websites
- EV policy OIDs
- not EV-enabled
- First included in
- NSS 3.15.4 / Firefox 27
- Inclusion bug
- #811352
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth, emailProtection
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client Authentication, Code Signing, Secure Email
- 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
- Government of Spain, Autoritat de Certificació de la Comunitat Valenciana (ACCV)
- Subject
- C=ES,O=ACCV,OU=PKIACCV,CN=ACCVRAIZ1
- SHA-256
9A6EC012E1A7DA9DBE34194D478AD7C0DB1822FB071DF12981496ED104384113- SHA-1 (Windows thumbprint)
93057A8815C64FCE882FFA9116522878BC536417- SPKI SHA-256
05570AE6EB0FCEB4210E6DB79486B7094CAF200401E149B6677441B5F25E449B- Valid from
- 2011-05-05
- Expires
- 2030-12-31
- Key
- RSA 4096
- Signature algorithm
- sha1WithRSAEncryption
- Serial number
5EC3B7A6437FA4E0- Country
- ES
- Trust bits (CCADB)
- Server Authentication, Client Authentication, Secure Email
- EV policy OIDs (CCADB)
- not EV-enabled · TLS EV capable: No
- Test websites
- valid:
https://activo.accv.es/test/hola.html· expired:https://caducado.accv.es:444/test/hola.html· revoked:https://revocado.accv.es:442/test/hola.html - CCADB record
- A000071
- PEM
- accv-accvraiz1.pem
Intermediate CAs issued by this root
The CCADB lists 8 intermediate CA certificates signed directly by ACCVRAIZ1: 3 currently valid, 0 expired and 5 revoked (revoked includes those whose parent was revoked).
Showing 8 of 8: 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 |
|---|---|---|---|
| ACCV ROOT RSA TLS 2024 | Government of Spain, Autoritat de Certificació de la Comunitat Valenciana (ACCV) | 2030-11-30 | Valid |
| ACCV RSA1 TLS | Government of Spain, Autoritat de Certificació de la Comunitat Valenciana (ACCV) | 2030-11-30 | Valid |
| ACCVCA-120 | Government of Spain, Autoritat de Certificació de la Comunitat Valenciana (ACCV) | 2026-12-31 | Valid |
| ACCVCA-110 | Government of Spain, Autoritat de Certificació de la Comunitat Valenciana (ACCV) | 2026-12-31 | Revoked |
| ACCVCA-130 | Government of Spain, Autoritat de Certificació de la Comunitat Valenciana (ACCV) | 2026-12-31 | Revoked |
| ACCVCA-130 | Government of Spain, Autoritat de Certificació de la Comunitat Valenciana (ACCV) | 2026-12-31 | Revoked |
| ACCVCA-120 | Government of Spain, Autoritat de Certificació de la Comunitat Valenciana (ACCV) | 2026-12-31 | Revoked |
| ACCVCA-110 | Government of Spain, Autoritat de Certificació de la Comunitat Valenciana (ACCV) | 2026-12-31 | Revoked |
Cross-signed versions
No certificate in the CCADB has the same subject and public key as ACCVRAIZ1 with a different issuer, so a client has to carry ACCVRAIZ1 itself in its root store to trust it.
CRL and OCSP addresses
In the root certificate
- CRL:
http://www.accv.es/fileadmin/Archivos/certificados/raizaccv1_der.crl - OCSP:
http://ocsp.accv.es
Full CRL this CA publishes (CCADB)
http://www.accv.es/fileadmin/Archivos/certificados/raizaccv1_der.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 3 valid intermediates signed by ACCVRAIZ1; the number in brackets is how many of them use each address.
- CRL:
http://www.accv.es/fileadmin/Archivos/certificados/raizaccv1_der.crl(3) - OCSP:
http://ocsp.accv.es(3)
What happens when it expires
ACCVRAIZ1 is valid until 2030-12-31, about 4.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.
Check whether your device trusts it
Each platform keeps its own root store. The commands below look up ACCVRAIZ1 by common name (ACCVRAIZ1) 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 "ACCVRAIZ1" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 9A6EC012E1A7DA9DBE34194D478AD7C0DB1822FB071DF12981496ED104384113
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 93057A8815C64FCE882FFA9116522878BC536417
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 "ACCVRAIZ1"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "ACCVRAIZ1"
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 "9A:6E:C0:12:E1:A7:DA:9D:BE:34:19:4D:47:8A:D7:C0:DB:18:22:FB:07:1D:F1:29:81:49:6E:D1:04:38:41:13"
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 ACCV → ACCVRAIZ1.
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 accv-accvraiz1.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=9A:6E:C0:12:E1:A7:DA:9D:BE:34:19:4D:47:8A:D7:C0:DB:18:22:FB:07:1D:F1:29:81:49:6E:D1:04:38:41:13
FAQ
Is ACCVRAIZ1 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.
When does ACCVRAIZ1 expire?
On 2030-12-31, about 4.1 years after the 2026-11-10 data snapshot.
How many intermediate certificates has ACCVRAIZ1 issued?
The CCADB lists 8: 3 valid, 0 expired and 5 revoked. The newest valid one is ACCV ROOT RSA TLS 2024, valid until 2030-11-30.
Is ACCVRAIZ1 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