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

63/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. It offers a broad range of academic disciplines from humanities to natural sciences and medicine, positioning itself as a leading research and medical university in the country. The website serves as a comprehensive portal for faculties, institutes, and academic services, targeting students, researchers, and the academic community. Technically, the website is built on the TYPO3 CMS platform, leveraging modern web technologies including HTML5, CSS, and JavaScript. It demonstrates good mobile optimization and accessibility features, with structured data enhancing SEO and content clarity. The hosting infrastructure appears to be university-managed or affiliated with German research networks, ensuring reliability. From a security perspective, the site uses HTTPS with strong SSL configuration and employs best practices such as deferred script loading. However, it lacks explicit security headers and does not publicly provide a security policy or vulnerability disclosure mechanism. Privacy compliance is limited, with no visible privacy or cookie policies, which could be improved to align with GDPR requirements. Overall, the website is professional, trustworthy, and content-rich, but could enhance its privacy and security posture to better protect users and comply with regulations.

Scanned

This is an earlier scan of uni-leipzig.de. View the latest report

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 25 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
47
Security headers
75
Email security
60
DNS health
65
Network security
100
GDPR outside view
28
Average
63

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 strong research focus, serving a large and diverse academic audience. Its competitive advantage lies in its long history, comprehensive academic offerings, and integration with medical and veterinary faculties. Revenue streams are primarily from public funding and tuition, with strategic partnerships evident through multiple affiliated institutes and research centers. The university maintains a robust digital presence with active social media channels and a well-structured website, supporting its mission and outreach. Growth indicators include the breadth of faculties and institutes, ongoing research activities, and digital maturity. The partnership ecosystem includes various academic and research institutions, enhancing its market position in higher education within Germany and internationally.

Security posture

The university's website demonstrates a moderate to good security maturity level. HTTPS is enforced with excellent SSL configuration, and no sensitive data is exposed in the HTML content. The use of asynchronous and deferred JavaScript loading reduces performance and security risks. However, the absence of security headers such as Content-Security-Policy and X-Frame-Options represents a gap that could be exploited in certain attack scenarios. There is no publicly available incident response or security contact information, limiting transparency and readiness for security incidents. Compliance gaps include missing explicit privacy and cookie policies, which are critical under GDPR and related regulations. The lack of a vulnerability disclosure policy or security.txt file reduces the ability for external security researchers to report issues responsibly. Overall, while no critical vulnerabilities are evident, improvements in policy transparency and header implementation are recommended.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie consent mechanism to ensure GDPR compliance.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  3. Establish and publicize an incident response contact and vulnerability disclosure policy, including a security.txt file.
  4. Regularly audit and update third-party scripts and libraries to avoid vulnerabilities.
  5. Enhance user trust by linking certifications, accreditations, or trust seals where applicable.

Contact details published on the site

Addresses
Legal name
Universität Leipzig
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 education and clinical services
Content quality
excellent
Branding
consistent

Technology

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

Security

Observed score
85/100
Good practices seen
  • HTTPS enabled
  • Use of deferred and async script loading
  • No visible exposed sensitive data in HTML

Analytics and tracking

Services
Piwik (Matomo)
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Piwik (Matomo)
Transparency
basic

Site quality

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

Key observations

  1. Website is a comprehensive portal for Universität Leipzig with detailed faculty and institute information.
  2. Uses TYPO3 CMS, a reputable open-source CMS.
  3. No visible privacy or cookie policies found in the provided content.
  4. No forms detected in the truncated HTML content; likely forms exist on subpages.
  5. Social media presence is strong with official accounts linked.
  6. No security.txt or vulnerability disclosure information found.
  7. Good accessibility features such as skip links and aria attributes.
  8. No suspicious or malicious content detected.
Technical notes

Notes

The website is powered by TYPO3 CMS, a mature and widely used open-source content management system, indicating a stable and scalable infrastructure. The site uses modern web standards including HTML5, CSS, and JavaScript with deferred and asynchronous loading to optimize performance. Structured data in JSON-LD format is implemented for organization and social media profiles, improving SEO and discoverability. Hosting appears to be managed by university or research network infrastructure, providing reliability and security. The site is mobile optimized and accessible, with ARIA attributes and skip links enhancing usability for assistive technologies. Performance is moderate, with potential for improvement through further optimization of assets and caching strategies. No critical technical debt or deprecated technologies were detected in the provided content.
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. 62/100Medium34 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.