Skip to main content

Security report for hug-ge.ch

Hôpitaux Universitaires Genève · Healthcare · Switzerland

High risk. 9 critical or high findings in GDPR outside view, Email security and 2 other checks.

Security score

47/100

Risk levelHigh

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

Hôpitaux Universitaires Genève (HUG) is a leading university hospital in Switzerland providing comprehensive medical services including surgery, outpatient consultations, patient and professional information, research, and education. The website targets patients, their families, and healthcare professionals, positioning itself as a national and international reference in healthcare. The digital infrastructure is built on Drupal 10 with modern web technologies and integrates analytics and social media platforms to enhance user engagement. The site is well-structured, mobile-optimized, and accessible, reflecting a mature digital presence. Security posture is solid with HTTPS and no visible vulnerabilities, though explicit security policies and incident response information are absent. Privacy compliance is weak due to missing privacy and cookie policies. Overall, the website is professional and trustworthy but would benefit from enhanced privacy and security transparency.

Scanned

This is an earlier scan of hug-ge.ch. View the latest report

NIS2 and GDPR posture

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

9 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 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

  2. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  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.

    • 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

  4. 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 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 hug-ge.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
0
Security headers
55
Email security
40
DNS health
75
Network security
100
GDPR outside view
10
Average
47

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

HUG operates as a public university hospital with a strong emphasis on healthcare delivery, research, and education. Its market position is robust, supported by partnerships with the University of Geneva and private foundations. The business model focuses on providing high-quality medical care and advancing medical knowledge. The website reflects this through detailed service information, professional resources, and patient engagement tools. Growth indicators include active research portals and strategic projects like hospital modernization. The partnership ecosystem includes foundations and university faculties, enhancing credibility and resource access.

Security posture

The website demonstrates a moderate to good security maturity level with enforced HTTPS, use of analytics with IP tracking, and no exposed sensitive data. However, the absence of security headers, incident response contacts, and vulnerability disclosure mechanisms indicates gaps in security transparency and readiness. There is no evidence of GDPR compliance mechanisms such as cookie consent banners or privacy policies, which could pose compliance risks. The use of third-party scripts like Facebook SDK and Piwik PRO requires ongoing monitoring to mitigate potential vulnerabilities. Overall, the security posture is adequate but requires improvements in policy publication and technical controls.

Recommendations

  1. Publish comprehensive privacy and cookie policies with clear GDPR compliance statements.
  2. Implement security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Provide explicit incident response and vulnerability disclosure information, including security contact emails.
  4. Add a data protection officer contact to enhance transparency and compliance.
  5. Regularly audit and update third-party scripts and analytics tools to minimize security risks.

Contact details published on the site

Addresses
Legal name
Hôpitaux Universitaires Genève
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Hôpitaux Universitaires Genève
Description
Services médicaux, chirurgie, consultation ambulatoire, informations pour les patients et les professionnels de santé, toute l’actualité des soins, de la formation et de la recherche aux HUG
Key services
Medical services, Surgery, Outpatient consultation, Patient and professional information, Research and training
Content quality
good
Branding
consistent

Technology

Stack
Drupal 10, Font Awesome 6, Piwik PRO analytics, Facebook SDK
Frameworks
Drupal
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced (canonical URLs use https)
  • No exposed sensitive data in HTML
  • Use of analytics with IP tracking enabled

Analytics and tracking

Services
Piwik PRO
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Piwik PRO
Marketing tools
Facebook SDK
Transparency
basic

Site quality

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

Key observations

  1. Website is a professionally maintained university hospital site
  2. Content is primarily in French with English alternate available
  3. No explicit privacy or cookie policies found on the homepage or footer
  4. Contact information is clearly provided with phone and physical addresses
  5. Use of modern CMS (Drupal 10) and standard web technologies
  6. Social media presence is extensive and official
  7. No signs of blocking or WAF challenges
  8. Analytics usage is moderate with Piwik PRO and Facebook SDK
  9. No visible security policy or incident response information
  10. No vulnerability disclosure or security.txt found
Technical notes

Notes

The website is built on Drupal 10, a modern and widely supported CMS, ensuring a solid technical foundation. It uses Font Awesome 6 for icons and integrates Piwik PRO for analytics and Facebook SDK for social media features. The site is mobile-optimized and accessible, with good SEO practices including meta tags and Open Graph data. Performance is moderate, with preloading of fonts and asynchronous loading of scripts. No critical technical debt or outdated libraries were detected. Opportunities exist to enhance security headers and privacy compliance features to align with best practices.
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

Earlier scans of this domain

  1. 69/100Medium29 findingsView report
Reviews of this site

Share your experience with hug-ge.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 hug-ge.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.