Skip to main content

Security report for uke.de

Universitätsklinikum Hamburg-Eppendorf · Healthcare · Germany

Medium risk. 5 critical or high findings in GDPR outside view and Security headers.

Security score

56/100

Risk levelMedium

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

The Universitätsklinikum Hamburg-Eppendorf (UKE) is a leading European university hospital specializing in healthcare, research, and education. The website reflects a comprehensive digital presence with extensive information about clinics, institutes, research programs, patient services, and educational offerings. The site targets patients, medical professionals, researchers, and students, positioning UKE as a major healthcare and research institution in Germany. Technically, the site uses established libraries like jQuery and Modernizr, and employs Matomo for privacy-conscious analytics. However, the absence of a valid SSL certificate and modern TLS protocols significantly impacts the security posture. Privacy compliance is well addressed with a clear privacy policy and cookie consent mechanism. The site demonstrates high professionalism and trustworthiness but requires urgent improvements in security infrastructure to protect user data and enhance 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

5 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

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

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

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

Keep watching uke.de

This scan found 17 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
50
Security headers
30
Email security
50
DNS health
90
Network security
100
GDPR outside view
18
Average
56

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

UKE operates as an essential entity in the healthcare sector, providing advanced medical treatment, research, and education. It maintains a large organizational structure with numerous clinics, institutes, and subsidiaries, indicating a large enterprise scale. The business model integrates patient care with cutting-edge research and academic programs, supported by a strong partnership and subsidiary ecosystem. The presence of certifications and trust seals, along with active social media channels, supports its market position and credibility. The website content is rich and well-structured, facilitating user navigation and engagement across diverse target groups.

Security posture

The current security posture of the UKE website is basic and requires significant enhancements. The lack of a valid SSL certificate and absence of HTTPS exposes users to potential data interception risks. No modern TLS protocols or security headers are implemented, and critical features like HSTS and OCSP stapling are missing. While no immediate vulnerabilities or subdomain takeover risks were detected, the overall configuration does not meet modern security standards. There is no explicit security or incident response policy visible, which may impact compliance with regulations such as GDPR and NIS2. Immediate remediation is recommended to secure communications and protect sensitive patient and organizational data.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable and enforce modern TLS protocols (TLS 1.2 or 1.3) and disable deprecated versions.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  4. Enable OCSP stapling to improve certificate revocation checks and reduce latency.
  5. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  6. Publish a security policy and incident response contact information to enhance transparency and compliance.
  7. Regularly audit and update third-party libraries and scripts to avoid vulnerabilities.
  8. Enhance privacy compliance by clearly documenting data retention policies and user rights.

Contact details published on the site

Addresses
Technical notes

Notes

The website is built using traditional web technologies including jQuery 2.1.3 and Modernizr, with a responsive design that adapts well to mobile devices. Matomo is used for analytics with a cookie-less configuration, reflecting a privacy-conscious approach. The site has a large number of resources (335) and a relatively slow load time (~24 seconds), indicating potential optimization opportunities. No modern CMS or advanced frameworks were detected. Hosting appears to be managed by the University of Hamburg infrastructure. The absence of HTTPS and modern security protocols is a critical technical risk. Overall, the technical implementation is functional but requires modernization and security hardening to meet current 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

Reviews of this site

Share your experience with uke.de. 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 uke.de.

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.