Certificate authority
ComSign
ComSign operates 1 root certificate(s) trusted for TLS by at least one major root store (CCADB owner: ComSign; country: IL). See fingerprints, expiry and Chrome, Mozilla, Apple and Microsoft status.
Details
- CCADB CA owner
- ComSign
- Country
- IL
- Country (CCADB)
- Israel
- Roots
- 1
- Roots trusted for TLS
- Chrome 0 · Mozilla 0 · Apple 0 · Microsoft 1
- Intermediates under its roots
- 6 (6 valid)
- Auditor
- BDO Israel – Ziv Haft CPA
- CAA
comsigneurope.com
CAA records
The CCADB lists 3 CAA issuer domain(s) recognized by the currently valid intermediate certificates of ComSign. One issue record with any of them lets ComSign 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 3 domain(s):
example.com. CAA 0 issue "comsigneurope.com"
example.com. CAA 0 issue "comsign.co.il"
example.com. CAA 0 issue "comsign.co.uk"
| Domain | Valid intermediates |
|---|---|
comsigneurope.com | 6 |
comsign.co.il | 6 |
comsign.co.uk | 6 |
For issuewild, iodef or DNS-provider formats, use the CAA record generator: CAA Generator
Root certificates (CCADB)
ComSign has 1 root certificate(s) in the CCADB TLS report. Together they have signed 6 intermediate CA certificates, 6 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 |
|---|---|---|---|---|---|---|---|
| ComSign Global Root CA | RSA 4096 | 2036-07-16 | Not included | Not included | Blocked | Included | 6 (6) |
Audits
Audit data the CCADB records for the TLS roots of ComSign. Auditor(s): BDO Israel – Ziv Haft CPA. The most recent audit period ended on 2026-04-26.
| Audit | Scheme | Period | Statement | Report |
|---|---|---|---|---|
| Standard audit | WebTrust | 2025-04-27 – 2026-04-26 | 2026-04-27 | cpacanada.ca |
| Network security | WebTrust | 2025-04-27 – 2026-04-26 | 2026-04-27 | cpacanada.ca |
| TLS Baseline Requirements | WebTrust | 2025-04-27 – 2026-04-26 | 2026-04-27 | cpacanada.ca |
CP/CPS documents
The CCADB has no CP/CPS link for the TLS roots of ComSign.
- Document repository: https://www.comsign.co.il/repository
Report a certificate problem
To report a mis-issued certificate, a compromised private key or other abuse, use the channels ComSign lists in the CCADB (replace [at] and [dot] in addresses):
support[at]comsign[dot]co[dot]ilyaire[at]comda[dot]co[dot]il- https://www.comsign.co.il/
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 “ComSign”:
FAQ
What CAA record allows ComSign to issue certificates?
Publish example.com. CAA 0 issue "comsigneurope.com". The CCADB lists 3 recognized domain(s) for ComSign: comsigneurope.com, comsign.co.il, comsign.co.uk.
Who audits ComSign?
BDO Israel – Ziv Haft CPA, according to the CCADB. The latest TLS Baseline Requirements audit (WebTrust) covers 2025-04-27 to 2026-04-26; the statement is dated 2026-04-27.
How do I report a problem certificate to ComSign?
Use the channel(s) listed in the CCADB: support[at]comsign[dot]co[dot]il, yaire[at]comda[dot]co[dot]il, https://www.comsign.co.il/.
How many root certificates does ComSign have?
1 in the CCADB TLS report. Trusted for TLS: Chrome 0, Mozilla 0, Apple 0, Microsoft 1. They have signed 6 intermediates, 6 of them still valid.