Certificate authority
EDICOM
EDICOM operates 1 root certificate(s) trusted for TLS by at least one major root store (CCADB owner: EDICOM; country: ES). See fingerprints, expiry and Chrome, Mozilla, Apple and Microsoft status.
Details
- CCADB CA owner
- EDICOM
- Country
- ES
- Country (CCADB)
- Spain
- Roots
- 1
- Roots trusted for TLS
- Chrome 0 · Mozilla 0 · Apple 0 · Microsoft 1
- Intermediates under its roots
- 1 (1 valid)
- Auditor
- AENOR CONFIA, S.A. (Unipersonal)
- CAA
edicomgroup.com
CAA records
The CCADB lists 1 CAA issuer domain(s) recognized by the currently valid intermediate certificates of EDICOM. One issue record with any of them lets EDICOM issue for your domain. Domains that contain the CA's name come first, the rest by how many valid intermediates recognize them.
Copy-ready record(s) for the first 1 domain(s):
example.com. CAA 0 issue "edicomgroup.com"| Domain | Valid intermediates |
|---|---|
edicomgroup.com | 1 |
For issuewild, iodef or DNS-provider formats, use the CAA record generator: CAA Generator
Root certificates (CCADB)
EDICOM has 1 root certificate(s) in the CCADB TLS report. Together they have signed 1 intermediate CA certificates, 1 of them still valid.
Roots this CA owner has in the CCADB TLS Server Authentication report, with current status in each root store.
- trusted for TLS
- included with limits (NotBefore / no TLS bit)
- removed or blocked
- not included
| Root certificate | Key | Expires | Ch | Mo | Ap | MS | Intermediates |
|---|---|---|---|---|---|---|---|
| CAEDICOM Root | RSA 4096 | 2034-05-21 | Not included | Not included | Not included | Included | 1 (1) |
Audits
Audit data the CCADB records for the TLS roots of EDICOM. Auditor(s): AENOR CONFIA, S.A. (Unipersonal). The most recent audit period ended on 2026-04-24.
| Audit | Scheme | Period | Statement | Report |
|---|---|---|---|---|
| Standard audit | ETSI EN 319 411 | 2025-04-25 – 2026-04-24 | 2026-05-13 | eidas.aenor.com |
| TLS Baseline Requirements | ETSI EN 319 411 | 2025-04-25 – 2026-04-24 | 2026-05-13 | eidas.aenor.com |
CP/CPS documents
Certificate Policy and Certification Practice Statement links that EDICOM has disclosed in the CCADB for its TLS roots, with effective dates:
- CPS: https://acedicom.edicomgroup.com/eu/CAEDICOM%20-%20Declaraci%C3%B3n%20de%20Pr%C3%A1cticas%20de%20Certificaci%C3%B3n.pdf (effective 2026-03-13)
- CP: https://acedicom.edicomgroup.com/eu/CAEDICOM-PoliticaCertificadosTLS.pdf (effective 2026-04-27)
- Document repository: https://acedicom.edicomgroup.com/eu/caedicom_en.xml
Report a certificate problem
To report a mis-issued certificate, a compromised private key or other abuse, use the channels EDICOM lists in the CCADB (replace [at] and [dot] in addresses):
Incident reports
CAs in Mozilla's root program file compliance incident reports in Mozilla's Bugzilla (product CA Program, component CA Certificate Compliance). This search lists the bugs whose title contains the words “EDICOM”:
FAQ
What CAA record allows EDICOM to issue certificates?
Publish example.com. CAA 0 issue "edicomgroup.com". The CCADB lists 1 recognized domain(s) for EDICOM: edicomgroup.com.
Who audits EDICOM?
AENOR CONFIA, S.A. (Unipersonal), according to the CCADB. The latest TLS Baseline Requirements audit (ETSI EN 319 411) covers 2025-04-25 to 2026-04-24; the statement is dated 2026-05-13.
How do I report a problem certificate to EDICOM?
Use the channel(s) listed in the CCADB: http://www.edicomgroup.com/auxiliar/contact.html.
How many root certificates does EDICOM have?
1 in the CCADB TLS report. Trusted for TLS: Chrome 0, Mozilla 0, Apple 0, Microsoft 1. They have signed 1 intermediates, 1 of them still valid.