Skip to main content

Security report for cannerald.com

Cannerald AG · Healthcare · Switzerland

High risk. 6 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

49/100

Risk levelHigh

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

Cannerald AG is a Swiss-based medical cannabis producer specializing in pharmaceutical-grade cannabis products. The company operates a high-tech indoor vertical farming facility in Switzerland, targeting an international clientele with a focus on quality, safety, and sustainability. Their business model centers on B2B supply of medical cannabis with rigorous quality controls and upcoming GMP certification. Technically, the website is built on Webflow and uses modern frontend technologies, but lacks a valid SSL certificate, resulting in no HTTPS support which is a critical security gap. The site includes a cookie consent mechanism compliant with GDPR and provides contact via a form, but lacks explicit email or phone contact details. Social media presence is active on major platforms. Security posture is weak due to missing SSL/TLS, but no other major vulnerabilities are detected. Overall, the site is professional and content-rich but requires urgent security improvements to protect user data and trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
18/ 100 · Critical
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. GDPR outside view

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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • 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

  2. 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

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. 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';…

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

Keep watching cannerald.com

This scan found 22 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
60
DNS health
85
Network security
100
GDPR outside view
18
Average
49

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 company positions itself as a premium medical cannabis producer leveraging Swiss quality standards and innovative indoor farming techniques. Their competitive advantage lies in consistent pharmaceutical-grade products and sustainable cultivation methods. The business targets medical and pharmaceutical sectors internationally, emphasizing trust and compliance. The website supports this positioning with detailed content on quality and production capabilities. However, the lack of explicit business contact details and security certifications may limit trust for some partners. The company appears to be medium-sized with a clear focus on healthcare and medical cannabis. No parent or subsidiary companies are identified. The marketing ecosystem includes social media but no visible advertising or analytics beyond cookie consent.

Security posture

The website currently lacks a valid SSL certificate and does not support any TLS protocols, exposing users to potential data interception risks. Security headers are partially implemented but HSTS is not effectively enabled. No incident response or security policy information is published. Cookie consent is implemented with opt-in and preference management, supporting GDPR compliance. No vulnerable libraries or known exploits are detected. The absence of HTTPS is a critical issue that severely impacts the overall security posture and user trust. Recommendations include immediate deployment of a valid SSL certificate, enabling modern TLS protocols, and publishing security and incident response policies to enhance transparency and readiness.

Recommendations

  1. Acquire and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 or TLS 1.3) and configure strong cipher suites.
  3. Implement and enable HSTS with includeSubDomains and preload flags to enforce HTTPS.
  4. Publish a security policy and incident response contact information (e.g., security@ or abuse@ emails).
  5. Enhance contact information by adding verified company emails and phone numbers for better trust.
Technical notes

Notes

The website is hosted behind Cloudflare CDN and built using Webflow CMS, leveraging jQuery and Finsweet cookie consent scripts. The site is mobile optimized with responsive design and clear navigation. Performance metrics are not available but the use of CDN and modern frameworks suggests moderate to good performance. Accessibility features are basic but present. SEO optimization is basic with proper meta viewport and title tags but no advanced structured data or Open Graph tags detected. The lack of HTTPS and SSL certificate is the most significant technical risk. No analytics or tracking scripts beyond cookie consent are detected, indicating a privacy-conscious approach.
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 cannerald.com. 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 cannerald.com.

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.