Skip to main content

Security report for uniklinikum-leipzig.de

Universitätsklinikum Leipzig AöR · Healthcare · Germany

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

Security score

58/100

Risk levelMedium

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

Universitätsklinikum Leipzig is a large, reputable university hospital in Germany providing comprehensive healthcare services, medical education, and research. The website serves multiple audiences including patients, students, and medical professionals, offering detailed information on clinical services, education programs, and research initiatives. The institution holds recognized certifications such as the lung cancer center certification, reinforcing its medical excellence. Technically, the website is built on Microsoft SharePoint with Bootstrap and jQuery, ensuring responsive design and moderate performance. Analytics are handled via Matomo with privacy-conscious settings disabling cookies. Security posture is strong with HTTPS enforced and secure form handling, though some security headers and explicit incident response policies are absent. Overall, the site is professional, trustworthy, and well-aligned with its institutional mission.

Scanned

NIS2 and GDPR posture

GDPR outside view
28/ 100 · High
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. 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. 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. 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 uniklinikum-leipzig.de

This scan found 28 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
62
Security headers
55
Email security
40
DNS health
60
Network security
100
GDPR outside view
28
Average
58

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention uniklinikum-leipzig.de, from OffSeq Breach.

Total records
68
Employees
0
Customers
68
Third parties
0
Weak passwords
10%

5 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for uniklinikum-leipzig.de.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The hospital holds a strong market position as the largest medical education institution in Saxony, Germany, with a public university hospital business model. It targets patients, medical students, and researchers, offering services from patient care to clinical studies and academic training. The website links to partner domains including the University of Leipzig and dedicated job portals, indicating a robust partnership ecosystem. The content quality and branding are consistent, supporting a credible and authoritative online presence. Growth indicators include active recruitment campaigns and new institute formations. The business model is supported by public funding and academic affiliations.

Security posture

The website demonstrates a mature security posture with enforced HTTPS, secure form submissions with anti-forgery tokens, and no visible exposure of sensitive data. However, the absence of common security headers (CSP, HSTS, X-Frame-Options) and lack of published incident response or vulnerability disclosure policies represent gaps. GDPR compliance is indicated by a comprehensive privacy policy, but no cookie consent mechanism was detected. The use of Matomo analytics with disabled cookies shows privacy-conscious tracking. Overall, the security maturity is good but could be improved by adding explicit security headers and incident response information.

Recommendations

  1. Implement and publish a cookie consent banner to comply fully with GDPR cookie requirements.
  2. Add standard security headers such as Content-Security-Policy, Strict-Transport-Security, and X-Frame-Options.
  3. Publish a vulnerability disclosure policy or security.txt file to enhance transparency and incident response readiness.
  4. Include explicit security and incident response policies accessible from the website.
  5. Regularly audit third-party scripts and libraries to ensure no vulnerabilities are introduced.

Contact details published on the site

Addresses
Legal name
Universitätsklinikum Leipzig AöR
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Universitätsklinikum Leipzig AöR
Description
Universitätsklinikum Leipzig is a large university hospital providing medical care, education, and research services. It offers patient care, medical training, and scientific research with a focus on healthcare excellence.
Key services
Patient care, Medical education, Research, Emergency services, Clinical studies
Content quality
good
Branding
consistent

Technology

Stack
Microsoft SharePoint, jQuery 2.1.4, Bootstrap, Matomo Analytics
Frameworks
SharePoint 2013/2016, Bootstrap
Platforms
Web, Desktop, Mobile (responsive design)
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of secure forms with anti-forgery tokens

Analytics and tracking

Services
Matomo
Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
Matomo
Transparency
basic

Site quality

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

Key observations

  1. Website is a professional university hospital site with comprehensive healthcare and education content.
  2. Uses Microsoft SharePoint CMS with custom theming and Bootstrap for responsive design.
  3. Includes emergency contact information prominently.
  4. No explicit cookie consent mechanism detected despite GDPR compliance indications.
  5. Social media presence on Instagram, LinkedIn, Twitter, and YouTube.
  6. No visible security.txt or vulnerability disclosure page.
  7. SSL is properly configured with HTTPS enforced.
  8. No suspicious or malicious content detected.
Technical notes

Notes

The website uses Microsoft SharePoint as its CMS platform, leveraging Bootstrap and jQuery for frontend responsiveness and interactivity. The site is mobile-optimized with a responsive design and moderate performance. SEO is basic with canonical links and meta viewport tags but lacks advanced structured data like JSON-LD or Open Graph tags. Analytics are implemented via Matomo with privacy settings to disable cookies. The hosting appears to be managed internally by the university or medical center, with no external cloud hosting detected. The technical stack is stable but could benefit from modernization and enhanced SEO and accessibility features.
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. 58/100Medium35 findingsView report
Reviews of this site

Share your experience with uniklinikum-leipzig.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 uniklinikum-leipzig.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.