Skip to main content

Security report for k0rdent.io

Mirantis · Technology · N/a

Medium risk. 5 critical or high findings in SSL/TLS, Security headers and 1 other check.

Security score

51/100

Risk levelMedium

0–100, higher is better. How it is calculated

k0rdent.io is a professionally designed website representing an open-source Kubernetes-native distributed container management platform developed and originated by Mirantis. The platform targets platform engineering teams and enterprises managing multi-cloud, hybrid, and edge environments, focusing on modern workloads such as AI and ML. The website provides comprehensive content, including detailed descriptions, use cases, videos, and community engagement channels, reflecting a mature and well-positioned technology offering. Technically, the site is hosted on GitHub Pages, uses modern web technologies like Bootstrap and jQuery, and integrates Plausible Analytics for minimal user tracking. However, the site lacks a valid SSL/TLS certificate, resulting in no HTTPS support, which is a critical security deficiency. Security headers are partially implemented, but the absence of HTTPS significantly lowers the security posture. Privacy compliance is basic, with a privacy policy linked but no cookie consent mechanism despite analytics usage. Business credibility is strong due to clear branding, parent company association, and open-source transparency. Overall, the site is trustworthy and professional but requires urgent security improvements.

Scanned

NIS2 and GDPR posture

GDPR outside view
43/ 100 · High
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

5 findings rated critical or high. Fix these first.

  1. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • Critical

      Unable to retrieve SSL certificate

      Could not establish secure connection to retrieve certificate information

      What to do: Check if the server is accessible and SSL/TLS is properly configured

  2. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  3. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

Need hands-on remediation? Email guard@offseq.com

Keep watching k0rdent.io

This scan found 19 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
0
Security headers
30
Email security
50
DNS health
85
Network security
100
GDPR outside view
43
Average
51

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The business is positioned as an important player in the Kubernetes and platform engineering ecosystem, offering open-source software with enterprise-grade options through Mirantis. The target market includes platform engineering teams needing scalable, multi-cloud container management solutions, especially for AI/ML workloads. The business model leverages open-source community engagement and enterprise support. The website reflects a consistent brand identity aligned with Mirantis, with active community channels and documentation. External links reinforce partnerships and ecosystem integration. No direct revenue streams or pricing models are disclosed on the site, consistent with open-source projects. The company benefits from Mirantis' reputation and infrastructure.

Security posture

The security posture is currently weak due to the lack of a valid SSL certificate and HTTPS support, exposing users to potential interception and man-in-the-middle attacks. While HSTS is enabled, it is ineffective without HTTPS. Other security headers are present but minimal. No forms or sensitive data collection reduce attack surface, but the absence of secure transport is a critical vulnerability. No incident response or security policy information is provided. The site does not implement cookie consent mechanisms despite using analytics, indicating partial privacy compliance. Overall, the site requires immediate remediation of SSL/TLS issues and enhancement of security policies to meet modern standards.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS and secure all site traffic.
  2. Implement a cookie consent banner or mechanism to comply with privacy regulations given analytics usage.
  3. Add comprehensive security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  4. Publish a security policy and incident response contact information to improve transparency and trust.
  5. Regularly audit and update third-party scripts and dependencies to avoid vulnerabilities.
Technical notes

Notes

The website is built using a modern and popular front-end stack including Bootstrap, jQuery, and FontAwesome, ensuring responsive and accessible design. Hosting on GitHub Pages provides reliable infrastructure but lacks native SSL support without configuration. The site includes embedded YouTube videos and uses Plausible Analytics for privacy-focused tracking. Performance metrics are not provided, but the site structure and resources suggest moderate to good performance. SEO is supported by proper meta tags and Open Graph data. No CMS is detected, indicating a static site approach. The lack of SSL and session security mechanisms are technical risks that could impact user trust and business operations.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with k0rdent.io. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review k0rdent.io.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.