Skip to main content

Security report for spo.ch

Schweizerische Patientenorganisation SPO · Healthcare · Switzerland

Medium risk. 4 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

70/100

Risk levelMedium

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

The Schweizerische Patientenorganisation SPO is a well-established Swiss non-profit organization dedicated to patient advocacy and support in medical and dental treatments. With over 40 years of experience, SPO provides independent advice, legal protection insurance, and a platform for reporting critical treatment experiences. The organization actively engages in health policy and institutional collaboration to improve patient-centered healthcare in Switzerland. Their website reflects a mature digital presence with professional design, clear navigation, and multilingual support targeting Swiss patients and their families. Technically, the website leverages modern web technologies including Webflow CMS, Google Tag Manager, and Cloudflare Turnstile captcha for security. The site is hosted on Webflow's platform with CDN support, ensuring fast performance and excellent mobile optimization. Security best practices such as HTTPS enforcement and cookie consent mechanisms are implemented, though explicit security headers could be improved. From a security perspective, the site shows a strong posture with no detected vulnerabilities or exposed sensitive data. Privacy compliance is robust, with clear GDPR-aligned policies and user consent mechanisms. However, the absence of a published security policy or incident response contacts suggests room for maturity in security governance. Overall, SPO's website is trustworthy, professional, and well-aligned with its mission. The domain registration details corroborate the organization's legitimacy and history. Strategic recommendations include enhancing security headers, publishing incident response information, and maintaining vigilance on third-party scripts to sustain security and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 100 · Medium
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

4 findings rated critical or high. Fix these first.

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

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

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching spo.ch

This scan found 21 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
75
Security headers
30
Email security
70
DNS health
75
Network security
100
GDPR outside view
68
Average
70

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

SPO occupies a niche in the Swiss healthcare non-profit sector, focusing on patient rights and support. Its competitive advantage lies in its long-standing history, comprehensive advisory services, and integration into health policy forums. Revenue streams primarily come from donations and membership fees, supporting free patient consultations and advocacy work. The target customers are patients and their relatives seeking independent medical advice and legal protection. Growth indicators include active project engagement and digital service offerings such as online appointment booking. The partnership ecosystem includes health institutions and digital service providers like Libracore for appointment management. SPO demonstrates a stable operational model with strong community trust and a clear mission-driven approach.

Security posture

The website demonstrates a mature security posture with HTTPS enforced and use of Cloudflare Turnstile captcha to protect forms from automated abuse. Cookie consent is implemented in line with GDPR requirements. No sensitive data leakage or vulnerable libraries were detected in the HTML content. However, the absence of explicit security headers such as Content-Security-Policy and X-Frame-Options is a minor gap. There is no publicly available security policy or incident response contact, which limits transparency in security governance. Overall, the site is secure for its purpose but could benefit from formalizing security documentation and enhancing HTTP header protections to mitigate advanced threats.

Recommendations

  1. Implement and enforce security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  2. Publish a clear security policy and provide incident response contact information on the website.
  3. Add a vulnerability disclosure or security.txt file to encourage responsible reporting.
  4. Regularly audit and update third-party scripts and libraries to prevent vulnerabilities.
  5. Enhance server-side validation and monitoring of form submissions to prevent abuse.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Schweizerische Patientenorganisation SPO
Description
Die Schweizerische Patientenorganisation SPO berät Patient:innen rund um medizinische und zahnmedizinische Behandlungen und engagiert sich für ein patientenorientiertes Gesundheitssystem.
Key services
Medical and dental treatment advice, Anonymous reporting of critical treatment experiences, Patient advance directives (Patientenverfügung Plus), Patient legal protection insurance, Political and institutional engagement
Content quality
excellent
Branding
consistent

Technology

Stack
Google Tag Manager, Google Fonts, jQuery 3.5.1, Webflow CMS, Finsweet Cookie Consent, Cloudflare Turnstile Captcha
Frameworks
Webflow
Platforms
Webflow Hosting
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of Cloudflare Turnstile captcha on forms
  • Cookie consent banner implemented
  • No exposed sensitive data in HTML
  • No vulnerable libraries detected

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Marketing tools
Mailchimp (via spo.us11.list-manage.com)
Transparency
good

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is professionally designed and well-structured
  2. Content is comprehensive and relevant to patient advocacy
  3. Strong focus on GDPR compliance and user privacy
  4. Use of modern web technologies and security best practices
  5. Clear calls to action for donations, membership, and consultation booking
  6. No signs of malicious or suspicious activity
Technical notes

Notes

The website is built on Webflow CMS, leveraging modern front-end technologies and Google Tag Manager for analytics. It uses Google Fonts for typography and integrates Cloudflare Turnstile captcha for bot protection on forms. Hosting is via Webflow's platform with CDN support, resulting in fast load times and excellent mobile responsiveness. The site includes multilingual support for German, French, and Italian, targeting the Swiss market. SEO is well addressed with proper meta tags and Open Graph data. Accessibility is good with labeled form fields and ARIA attributes. The technical implementation is modern and well-maintained, with minor opportunities to improve security headers and formalize privacy and security documentation.
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 spo.ch. 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 spo.ch.

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.