SaaS Ranking

Engineering and data / Network monitoring

Checkmk

What Checkmk publishes on checkmk.com, measured on 2026-09-02. Every line links the page we found it on, or lists the addresses we checked.

Not enough data: 6 of 12 criteria measured, so no transparency score

Not ranked: we could measure 6 of 12 criteria, below our thresholdchecked 2026-09-02

3 gaps found: 3 criteria not found at the addresses we checked. 3 found3 not found6 not measured

Public transparency score, not a product or security rating. That is a statement about our measurement, not about Checkmk.

Transparency labelsaas-ranking.com

Checkmk

checkmk.com · Network monitoring

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
Not enough data6 of 12 measured, no score

Published commitments3 of 6 found, 3 not measured

Measured behaviour3 not measured

Checked 2026-09-02. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.

We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.

Show the full transparency label

Transparency labelsaas-ranking.com

Checkmk

checkmk.com · Network monitoring

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
Not enough data6 of 12 measured, no score

Published commitments3 of 6 found, 3 not measured

Measured behaviour3 not measured

Checked 2026-09-02. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.

We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.

Not found, heaviest first

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-02.

Show the 8 addresses we checked
  1. https://checkmk.com/legal/dpa – Not the expected content type but "application/pdf".
  2. https://checkmk.com/dpa – reached, no match (HTTP 404)
  3. https://checkmk.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://checkmk.com/data-processing-agreement – reached, no match (HTTP 404)
  5. https://checkmk.com/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://checkmk.com/legal/gdpr – reached, no match (HTTP 404)
  7. https://checkmk.com/trust/dpa – reached, no match (HTTP 404)
  8. https://checkmk.com/privacy/dpa – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-02.

Show the 7 addresses we checked
  1. https://checkmk.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://checkmk.com/subprocessors – reached, no match (HTTP 404)
  3. https://checkmk.com/sub-processors – reached, no match (HTTP 404)
  4. https://checkmk.com/legal/sub-processors – Not the expected content type but "application/pdf".
  5. https://checkmk.com/trust/subprocessors – reached, no match (HTTP 404)
  6. https://checkmk.com/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://checkmk.com/legal/subprocessor-list – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Status page with history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-02.

Show the 3 addresses we checked
  1. https://status.checkmk.com/ – The name "status.checkmk.com" could not be resolved.
  2. https://checkmk.com/status – reached, no match (HTTP 404)
  3. https://checkmk.com.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Published evidence 3

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

Source: https://checkmk.com/privacy-policy · checked 2026-09-02

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://checkmk.com/pricing · checked 2026-09-02

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

Source: https://trust.checkmk.com/ · checked 2026-09-02

Not measured by us 6

HTTPS enforced with HSTS

weight 2 of 3

Not measured. The plain HTTP endpoint could not be reached, so this was not measured.

Show the 1 address we checked
  1. http://checkmk.com/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

No third-party tracking before consent

weight 2 of 3

Not measured. The page could not be loaded in a browser, so this was not measured.

Show the 1 address we checked
  1. https://checkmk.com/ – page.goto: net::ERR_CONNECTION_REFUSED at https://checkmk.com/ Call log: - navigating to "https://checkmk.com/", waiting until "domcontentloaded"

Is this wrong? Send us the URL

Notice before subprocessors change

weight 2 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 8 addresses we checked
  1. https://checkmk.com/legal/subprocessors – Could not be fetched: fetch failed.
  2. https://checkmk.com/subprocessors – Could not be fetched: fetch failed.
  3. https://checkmk.com/sub-processors – Could not be fetched: fetch failed.
  4. https://checkmk.com/legal/dpa – Could not be fetched: fetch failed.
  5. https://checkmk.com/dpa – Could not be fetched: fetch failed.
  6. https://checkmk.com/legal/data-processing-agreement – Could not be fetched: fetch failed.
  7. https://checkmk.com/trust/subprocessors – Could not be fetched: fetch failed.
  8. https://checkmk.com/legal/sub-processors – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Uptime SLA with a figure

weight 1 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 6 addresses we checked
  1. https://checkmk.com/legal/sla – Could not be fetched: fetch failed.
  2. https://checkmk.com/sla – Could not be fetched: fetch failed.
  3. https://checkmk.com/legal/service-level-agreement – Could not be fetched: fetch failed.
  4. https://checkmk.com/trust/sla – Could not be fetched: fetch failed.
  5. https://checkmk.com/uptime – Could not be fetched: fetch failed.
  6. https://checkmk.com/legal/uptime-sla – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

security.txt (RFC 9116)

weight 1 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 1 address we checked
  1. https://checkmk.com/.well-known/security.txt – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Named privacy contact

weight 1 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 7 addresses we checked
  1. https://checkmk.com/legal/privacy – Could not be fetched: fetch failed.
  2. https://checkmk.com/privacy – Could not be fetched: fetch failed.
  3. https://checkmk.com/privacy-policy – Could not be fetched: fetch failed.
  4. https://checkmk.com/legal/privacy-policy – Could not be fetched: fetch failed.
  5. https://checkmk.com/legal/privacy-notice – Could not be fetched: fetch failed.
  6. https://checkmk.com/trust/privacy – Could not be fetched: fetch failed.
  7. https://checkmk.com/datenschutz – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Keep going