Skip to main content

Security report for medigo.ch

Medigo · Healthcare · Switzerland

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

Security score

55/100

Risk levelMedium

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

Medigo is a Swiss healthcare service platform providing real-time information on emergency medical centers, primarily serving the Canton of Vaud. The website targets patients seeking urgent care and medical centers wanting visibility. It offers key services such as real-time wait times, center recommendations based on location and transport, and coverage of six medical specialties. The company positions itself as a regional leader in emergency medical information within Swiss Romandy. Technically, the website uses modern JavaScript libraries including Alpine.js and FontAwesome, integrates Google Tag Manager for analytics, and implements a comprehensive cookie consent mechanism. The site is mobile optimized with good SEO practices and moderate performance. However, no CMS or hosting provider details are evident. From a security perspective, the site enforces HTTPS, includes CSRF tokens, and uses cookie consent for analytics tracking. Security headers are not explicitly detected, and no formal security or incident response policies are published. There are no visible vulnerabilities or exposed sensitive data. Privacy compliance is good with a clear privacy policy and cookie management. Overall, the website is professional, trustworthy, and secure with minor areas for improvement such as adding security policies and terms of service. The domain WHOIS data aligns well with the business claims, supporting legitimacy. No blocking or WAF mechanisms interfere with content access.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 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

7 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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • 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 Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

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

Keep watching medigo.ch

This scan found 24 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
72
Security headers
15
Email security
65
DNS health
85
Network security
40
GDPR outside view
50
Average
55

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

Medigo operates in the healthcare sector, focusing on emergency medical services information in Switzerland. Its competitive advantage lies in providing real-time, official data directly from emergency centers, enhancing patient decision-making. The business model revolves around a digital platform accessible via web and mobile apps, targeting patients and medical centers. Revenue streams are not explicit but likely include partnerships or service agreements with medical centers. The company maintains a clear partnership ecosystem with social media presence and app store distribution. Growth indicators include regional expansion potential beyond Canton Vaud. Strategic observations suggest focusing on expanding specialty coverage and enhancing B2B relationships with centers.

Security posture

The website demonstrates a mature security posture with HTTPS enforcement, CSRF protection, and cookie consent mechanisms aligned with GDPR. However, the absence of published security policies, incident response contacts, and vulnerability disclosure reduces transparency and preparedness. No critical vulnerabilities or exposed sensitive data were detected. Tracking technologies are used responsibly with opt-in consent. Compliance with GDPR is evident but could be strengthened by publishing detailed data retention policies and security frameworks. Incident response readiness is unclear due to lack of contact channels for security issues. Overall, security culture appears adequate but could benefit from formal documentation and communication.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and frameworks.
  2. Add an incident response contact email or page to improve transparency and readiness.
  3. Implement and serve security headers such as Content-Security-Policy and X-Frame-Options.
  4. Create and publish a terms of service page to clarify user agreements.
  5. Consider establishing a vulnerability disclosure policy or security.txt file.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Medigo
Description
Medigo provides real-time information on medical emergency centers, focusing on availability and wait times in the Canton of Vaud, Switzerland.
Key services
Real-time wait times for emergency centers, Recommendations for most suitable centers based on location and transport, Coverage of six medical specialties
Content quality
good
Branding
consistent

Technology

Stack
Alpine.js, FontAwesome, CookieConsent.js, Google Tag Manager
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • CSRF token present in meta tag
  • Cookie consent with opt-in/out for analytics

Analytics and tracking

Services
Google Analytics, Meta Pixel
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Meta Pixel (Facebook Pixel)
Marketing tools
CookieConsent.js
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is professionally presented in French targeting Swiss users.
  3. Strong privacy and cookie consent mechanisms are implemented.
  4. No explicit security policy or incident response information found.
  5. No terms of service page detected.
  6. Contact information is clear and includes phone, address, and contact page.
  7. Use of modern JavaScript libraries and tracking tools is evident.
  8. No suspicious or malicious content detected.
  9. Social media presence on Facebook and Instagram is linked.
  10. No explicit business certifications or security certifications displayed.
Technical notes

Notes

The website uses a modern and lightweight JavaScript framework (Alpine.js) and standard iconography (FontAwesome). CookieConsent.js is used for GDPR-compliant cookie management. Google Tag Manager and Meta Pixel are integrated for analytics and marketing. The site is responsive and mobile-friendly with good SEO metadata. No CMS or hosting provider is explicitly identified, suggesting a custom or static site deployment. Performance is moderate with room for optimization. Accessibility features are basic but present. Technical risks are low with no detected vulnerable libraries or exposed credentials. Opportunities include adding progressive web app features and improving accessibility compliance.
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 medigo.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 medigo.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.