Skip to main content

Security report for uni-leipzig.de

Universität Leipzig · Education · Germany

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

Security score

62/100

Risk levelMedium

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

Universität Leipzig is a historic and large public university in Germany, founded in 1409, offering a broad range of academic disciplines from humanities to natural sciences and medicine. The website serves as a comprehensive portal for faculties, institutes, and university services, targeting students, researchers, and the general public interested in academic information. The university holds a strong market position as a leading research and medical institution in Germany. Technically, the website is built on the TYPO3 CMS platform, employing modern web technologies including responsive design and accessibility features. The site integrates Matomo analytics for user tracking and maintains a consistent branding and professional design. Hosting appears to be managed within academic networks, ensuring reliability. From a security perspective, the site uses HTTPS and avoids exposing sensitive data. However, it lacks visible security headers, published security policies, and incident response contacts, which are areas for improvement. Privacy compliance is limited due to the absence of explicit privacy and cookie policies. Overall, the security posture is moderate but could be enhanced with additional best practices. The website content is safe for general audiences, with no adult or questionable content detected. Social media presence is robust, linking to official university channels. The WHOIS data aligns with the academic nature of the domain, showing consistency and legitimacy. The overall AI score reflects a good quality website with minor gaps in privacy and security disclosures.

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

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

  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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching uni-leipzig.de

This scan found 26 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
42
Security headers
75
Email security
60
DNS health
65
Network security
100
GDPR outside view
28
Average
62

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 uni-leipzig.de, from OffSeq Breach.

Total records
5,972
Employees
569
Customers
4,695
Third parties
708
Weak passwords
13%

Latest record dated 2026-06-14 · 199 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 uni-leipzig.de.

Select it in the checkout above.

Masked preview

  • –almaweb.uni-leipzig.de2026-06-14
  • –webvpn.uni-leipzig.de2026-06-13
  • –services.ub.uni-leipzig.de2026-06-12
  • –aai.rz.uni-leipzig.de2026-06-12
  • –almaweb.uni-leipzig.de2026-06-12

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

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

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

Business context

Business profile

Universität Leipzig operates as a public educational institution with a broad academic portfolio, including faculties in education, chemistry, history, life sciences, mathematics, physics, social sciences, law, philology, sports science, theology, medicine, veterinary medicine, and economics. The university's business model centers on providing higher education and conducting research, supported by its medical faculty and university hospital. Its target customers include students, academic staff, researchers, and healthcare patients. The university benefits from a strong brand legacy and a comprehensive network of faculties and institutes, which supports its competitive advantage in research and education. The website reflects a well-structured ecosystem with extensive information on departments and contact points, facilitating engagement and transparency. Growth indicators include active social media channels and digital presence. Partnerships appear to be primarily academic and institutional, with no commercial subsidiaries or payment processors identified. The university's operations emphasize knowledge dissemination and public service rather than commercial revenue streams.

Security posture

The security maturity of the Universität Leipzig website is moderate. The site enforces HTTPS, which is mandatory for secure communications. However, the absence of security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options reduces protection against common web attacks. No incident response or security contact information is published, limiting transparency and readiness for security incidents. No vulnerabilities or exposed sensitive data were detected in the analyzed content. The use of Matomo analytics indicates a preference for privacy-conscious tracking over third-party services. The lack of a vulnerability disclosure policy or security.txt file suggests room for improvement in vulnerability management and responsible disclosure. Recommendations include implementing security headers, publishing security policies, and establishing clear incident response channels to enhance trust and resilience.

Recommendations

  1. Publish a comprehensive privacy policy and cookie consent mechanism to improve GDPR compliance.
  2. Implement and configure security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Create and publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  4. Add incident response contact information, including dedicated security or abuse email addresses.
  5. Regularly audit and update third-party scripts and dependencies to mitigate potential vulnerabilities.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Universität Leipzig
Description
Unsere Universität wurde 1409 gegründet und gehört zu den forschungsstarken und medizinführenden Universitäten Deutschlands. Sie bietet eine einmalige Fächervielfalt von den Geistes- und Sozialwissenschaften bis zu den Natur- und Lebenswissenschaften.
Key services
Higher education, Research, Medical services via Universitätsklinikum Leipzig
Content quality
good
Branding
consistent

Technology

Stack
TYPO3 CMS, JavaScript, CSS, SVG, HTML5
Frameworks
TYPO3
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
75/100
Good practices seen
  • Use of HTTPS (implied by URL)
  • No visible exposed sensitive data in HTML
  • No vulnerable libraries detected in scripts

Analytics and tracking

Services
Matomo
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
piwik.js (Matomo analytics)
Marketing tools
Matomo (piwik.js)
Transparency
basic

Site quality

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

Key observations

  1. Website is a comprehensive portal for Universität Leipzig with detailed faculty and institute information.
  2. Content is primarily in German with English alternate links.
  3. Uses TYPO3 CMS and includes accessibility features.
  4. No visible privacy or cookie policies found in provided content.
  5. No contact forms detected in the provided HTML snippet.
  6. Social media presence is strong with official accounts linked.
  7. No security.txt or vulnerability disclosure found.
  8. No explicit security headers detected in provided data.
  9. Uses Matomo analytics for user tracking.
  10. No advertising or affiliate marketing detected.
Technical notes

Notes

The website is powered by TYPO3 CMS, a mature and widely used content management system suitable for large institutional websites. The use of compressed CSS assets and deferred JavaScript loading indicates attention to performance optimization. The site is mobile responsive and includes accessibility features such as skip links and ARIA attributes. Hosting appears to be managed within German academic networks, providing stable and reliable infrastructure. The site uses SVG logos and modern HTML5 semantics, supporting good SEO and user experience. However, the lack of visible security headers and privacy disclosures indicates technical debt in security and compliance areas. Performance is moderate, with potential for further optimization through enhanced caching and resource management.
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. 63/100Medium33 findingsView report
Reviews of this site

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