SaaS Ranking
Menu

Checkmk: what they publish

checkmk.com · Network monitoring · checked 2026-10-16

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

Public transparency score, not a product or security rating. Latest check: 2026-10-16. How the score works.

Evidence at a glance

Choose a check to see its source, date and scope.

Not found means not found at the addresses we checked. Not measured means we could not complete the check.

Start a vendor reviewDownload evidence (CSV)

Overview

1 day since the newest dated result, 1 since the oldest. 6 of 12 criteria have a measured result in the last 30 days. Failed checks and undated results are excluded.

Evidence freshness is a statement about our measurement and is kept apart from the transparency score, which is frozen at v1. How good our own measurement is.

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-10-16. 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.

Downloads include all checks, source URLs, dates and the snapshot ID for your procurement file. We do not issue badges.

The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating. We could measure 6 of 12 criteria, which is below our threshold, so there is no rank. That is a statement about our measurement, not about Checkmk.

Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that Checkmk has no such document.

What Checkmk states

The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.

Gaps, heaviest first

✗

Data processing agreement (DPA)

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-10-16.

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

Across the market: Data processing agreement in Network monitoring: 2 of 37 companies

✗

Subprocessors: the published list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-10-16.

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

Across the market: Subprocessor list in Network monitoring: 3 of 37 companies

✗

Status page with incident history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-10-16.

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

Across the market: Status page with history in Network monitoring: 12 of 38 companies

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Published, with a source 3
✓

Data location: where they say data is hosted

weight 3 of 3

The hosting location is stated on a public page.

  • Locations named next to the hosting wording Frankfurt, United States. This does not establish the company’s headquarters.
    Show the 2 exact wordings

    The technical implementation is carried out for the database via Supabase, hosted by Amazon Web Services in the Frankfurt region.

    Read at https://checkmk.com/privacy-policy

    The information obtained in this context may also be transferred to a Clickcease server in the USA and stored there.

    Read at https://checkmk.com/privacy-policy

Source: https://checkmk.com/privacy-policy · checked 2026-10-16

Across the market: Data location stated in Network monitoring: 10 of 37 companies

✓

Public pricing with figures

weight 2 of 3

Actual numbers on a public page.

Source: https://checkmk.com/pricing · checked 2026-10-16

Across the market: Public pricing in Network monitoring: 10 of 37 companies

✓

Certifications named (SOC 2, ISO 27001)

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page ISO/IEC 27001 (unclear from the sentence), SOC 2.
    Show the 2 exact wordings

    ssessment and Treatment Process Physical Security Policy Penetration Testing Policy Password Policy ISO 27001:2022 certificate pdf Information Security Policy Cryptography Policy Checkmk SOC 2 Type 1....

    Read at https://trust.checkmk.com/

    sword Policy ISO 27001:2022 certificate pdf Information Security Policy Cryptography Policy Checkmk SOC 2 Type 1 Report 2025 Checkmk Code of Conduct Change Management Policy Application Vulnerability....

    Read at https://trust.checkmk.com/

Source: https://trust.checkmk.com/ · checked 2026-10-16

Across the market: Certifications named in Network monitoring: 9 of 37 companies

Not measured by us 6
–

HTTPS enforced with HSTS

weight 2 of 3

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

Show the 2 addresses we checked
  1. http://checkmk.com/ – HTTP 503, no redirect to HTTPS
  2. https://checkmk.com/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Across the market: HTTPS enforced with HSTS in Network monitoring: 18 of 39 companies

–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

Across the market: No third-party tracking before consent in Network monitoring: 4 of 36 companies

–

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

Across the market: Notice before subprocessors change in Network monitoring: 3 of 36 companies

–

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

Across the market: Uptime SLA with a figure in Network monitoring: 3 of 36 companies

–

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

Across the market: security.txt (RFC 9116) in Network monitoring: 10 of 36 companies

–

Named privacy contact (DPO or privacy address)

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

Across the market: Named privacy contact in Network monitoring: 16 of 36 companies

History

Not enough completed runs yet to draw a line. The next runs fill this in.

Prepare your vendor review

A source is a starting point. Check the product, plan, legal entity and date before treating it as evidence for your purchase. These questions do not change the transparency score.

Checkmk

3 found · 3 not found · 6 not measured across 12 public checks.

6 of 12 criteria have a measured result from the last 30 days. Oldest dated result: 2026-10-16.

Investigate 9 open evidence questions
  1. Data processing agreement

    Please share the current data processing agreement for the product and plan we are considering, including its annexes and signing process.

    Inspect this check
  2. Subprocessor list

    Which subprocessors apply to our product, what does each process, and in which countries? Please share the current list.

    Inspect this check
  3. Status page with history

    Where can we review incident history for the service we will use, and how do we subscribe to incident updates?

    Inspect this check
  4. Uptime SLA with a figure

    Which availability commitment applies to our plan? Please include the measurement window, exclusions and credit claim process.

    Inspect this check
  5. HTTPS enforced with HSTS

    How is HTTPS enforced on the product and sign-in domains we will use? Please distinguish those domains from the public website.

    Inspect this check
  6. No third-party tracking before consent

    Which third-party requests occur before a visitor makes a choice, and for what purpose? Please distinguish the public website from the product.

    Inspect this check
  7. security.txt (RFC 9116)

    Where should we report a vulnerability, and what acknowledgement and follow-up process should we expect?

    Inspect this check
  8. Notice before subprocessors change

    How will you notify us before a subprocessor changes, with how much notice, and what response options apply to our contract?

    Inspect this check
  9. Named privacy contact

    Which privacy contact handles requests for our account, and what escalation path should we use?

    Inspect this check

Compare

A shortlist holds up to six vendors across categories and lives entirely in the address of its page: share the link, bookmark it, put it in a ticket. Nothing is stored, so we do not know it exists.