Skip to main content

Security report for k8slens.dev

Mirantis · Technology · N/a

Medium risk. 6 critical or high findings in SSL/TLS, Security headers and 2 other checks.

Security score

53/100

Risk levelMedium

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

Lens, operated by Mirantis, is a leading Kubernetes IDE designed for developers and DevOps engineers to manage and troubleshoot Kubernetes clusters efficiently. With over 1 million users globally, Lens holds a strong market position as the most popular Kubernetes IDE, offering a comprehensive and intuitive context-aware UI. The website reflects a professional and enterprise-grade product with strong trust indicators such as ISO 27001 and SOC2 Type 1 certifications and testimonials from reputable organizations. Technically, the site is built on modern frameworks like Next.js and React, hosted on AWS infrastructure with CDN support, ensuring good performance and mobile optimization. However, a critical security concern is the invalid or missing SSL certificate, which undermines the security posture despite the presence of HSTS and other security headers. Privacy compliance is generally good with a comprehensive privacy policy and GDPR indicators, though no explicit cookie consent mechanism was detected. Contact information is primarily via a contact form, with no direct emails or phone numbers publicly listed. Overall, Lens demonstrates strong business credibility and technical maturity but must address SSL issues to enhance trust and security.

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

6 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 k8slens.dev

This scan found 20 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
40
Email security
65
DNS health
85
Network security
85
GDPR outside view
43
Average
53

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

Mirantis positions Lens as an essential tool in the Kubernetes ecosystem, targeting developers and DevOps professionals seeking to simplify cluster management. The business model includes free and paid offerings, with a focus on enterprise customers as evidenced by the large user base and partnerships with major companies. The website content emphasizes productivity gains, security improvements, and cost efficiency, appealing to organizations aiming to optimize Kubernetes adoption. The presence of extensive documentation, forums, and support channels indicates a mature ecosystem supporting customer success. Mirantis leverages its brand and certifications to build trust, while the technical infrastructure supports scalability and performance. The company’s strategic focus on cloud-native technologies and Kubernetes aligns with current market trends, positioning Lens for continued growth and adoption.

Security posture

The website employs several security best practices including HSTS with subdomain inclusion, X-Content-Type-Options, and use of a reputable CDN (Imperva). Vulnerability scans indicate no presence of common SSL/TLS vulnerabilities such as Heartbleed, POODLE, FREAK, or Logjam. However, the SSL certificate is invalid or missing, and no TLS protocols are enabled, which is a critical security flaw that could expose users to man-in-the-middle attacks and erode trust. Additionally, OCSP stapling and session resumption are not implemented, which could impact both security and performance. No explicit incident response or vulnerability disclosure policies were found, which could be improved to enhance security transparency. Overall, while the site shows good security hygiene, the SSL/TLS configuration must be rectified urgently to meet enterprise security standards.

Recommendations

  1. Immediately fix and renew the SSL certificate to ensure valid HTTPS connections.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable deprecated protocols.
  3. Implement OCSP stapling and session resumption to improve security and performance.
  4. Add a cookie consent mechanism to comply with privacy regulations and enhance user trust.
  5. Publish a clear vulnerability disclosure policy and incident response contact information to improve security transparency and readiness.
Technical notes

Notes

The website is built using Next.js and React, leveraging server-side rendering and modern JavaScript frameworks for a responsive and performant user experience. Hosting is on AWS with DNS managed by AWS Route 53, and content delivery is accelerated via Imperva CDN. The site uses Google Fonts and Google Analytics for typography and analytics respectively. Meta tags and Open Graph data are well implemented for SEO and social media sharing. The site is mobile optimized and accessible with good navigation clarity. However, performance metrics were not provided, so load times and resource counts are unknown. The invalid SSL certificate is a significant technical risk. Overall, the technical infrastructure is modern and robust but requires immediate attention to SSL/TLS configuration to avoid security risks and potential user trust issues.
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 k8slens.dev. 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 k8slens.dev.

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.