Skip to main content

Security report for uni-stuttgart.de

Universität Stuttgart · Education · Germany

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

Security score

66/100

Risk levelMedium

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

The Universität Stuttgart is a leading technical university in Germany with a strong international reputation. The website reflects its mission to integrate engineering, natural sciences, humanities, and social sciences through top-tier research and education. The site targets prospective students, current students, researchers, entrepreneurs, employees, alumni, and media professionals, offering comprehensive information on study programs, research initiatives, and technology transfer. The university operates a large-scale digital presence with consistent branding and professional content quality. Technically, the website employs modern JavaScript libraries such as Bootstrap, jQuery UI, Fancybox, and Tippy.js, alongside Matomo analytics configured to disable cookies, indicating a privacy-conscious approach. The site is mobile-optimized, accessible, and SEO-friendly, with a custom CMS backend. Performance is moderate, with asynchronous script loading enhancing user experience. Security posture is solid with HTTPS enforced and standard security headers likely in place, though explicit Content-Security-Policy headers and incident response contacts are absent. Privacy compliance is good, with a comprehensive privacy policy and GDPR adherence, but lacks a visible cookie consent mechanism. No vulnerabilities or exposed sensitive data were detected. Overall, the website is trustworthy, professional, and well-maintained, supporting the university's stature. Strategic improvements include implementing a cookie consent banner, publishing a security policy and incident response contacts, and enhancing security headers to further strengthen the security posture.

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

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"

  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 SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching uni-stuttgart.de

This scan found 22 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
80
Security headers
45
Email security
85
DNS health
60
Network security
100
GDPR outside view
28
Average
66

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

Total records
10,097
Employees
742
Customers
8,388
Third parties
967
Weak passwords
6%

Latest record dated 2026-06-14 · 229 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-stuttgart.de.

Select it in the checkout above.

Masked preview

  • –idp.uni-stuttgart.de2026-06-14
  • –mail.uni-stuttgart.de2026-06-12
  • –campus.uni-stuttgart.de2026-06-12
  • –idp.uni-stuttgart.de2026-06-12
  • –siam.uni-stuttgart.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 Stuttgart holds a prominent position in the higher education sector, focusing on technical and interdisciplinary research and education. Its business model revolves around public funding, research grants, and knowledge transfer activities. The university targets a diverse audience including students at various levels, researchers, startups, and industry partners. The website's extensive navigation and content reflect a mature digital strategy supporting recruitment, research dissemination, and community engagement. Partnerships and social media presence indicate active outreach and collaboration. The institution's long history since 1829 and large size underscore its established market presence. Revenue streams likely include tuition fees, research funding, and technology licensing. The university's ecosystem supports entrepreneurship and innovation, positioning it as a key player in regional and international academic and technological landscapes.

Security posture

The website demonstrates a mature security posture with enforced HTTPS and use of security best practices such as disabling cookies in analytics. The absence of exposed sensitive data and use of asynchronous script loading reduce attack surface. However, the lack of explicit Content-Security-Policy headers and absence of published security policies or incident response contacts represent gaps in transparency and preparedness. No vulnerability disclosures or security.txt files were found, limiting external reporting channels. Overall, the security measures are adequate for an educational institution but could be enhanced by adopting additional headers, formalizing incident response communication, and implementing cookie consent mechanisms to align fully with GDPR and modern security standards.

Recommendations

  1. Implement a visible cookie consent mechanism to comply fully with GDPR requirements.
  2. Publish a dedicated security policy and provide clear incident response contact information.
  3. Add Content-Security-Policy and Referrer-Policy headers to strengthen browser security.
  4. Regularly audit third-party scripts and dependencies to mitigate potential vulnerabilities.
  5. Enhance transparency by providing a security.txt file and vulnerability disclosure guidelines.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Universität Stuttgart
Description
Die Universität Stuttgart ist eine führende technisch orientierte Universität mit weltweiter Ausstrahlung. Ihr Weg ist die interdisziplinäre Integration von Ingenieur-, Natur-, Geistes- und Gesellschaftswissenschaften auf der Grundlage disziplinärer Spitzenforschung.
Key services
Education (Bachelor, Master, Lehramt, Promotion), Research and Innovation, Technology and Knowledge Transfer, Career and Continuing Education Services
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, jQuery UI, Bootstrap, Fancybox, Tippy.js, Popper.js, Piwik/Matomo Analytics
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of async and defer for scripts
  • Disable cookies in analytics (_paq.push(['disableCookies']))

Analytics and tracking

Services
Piwik/Matomo
Tracking level
minimal
Privacy practices
good

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 fully accessible with no blocking or WAF challenges.
  2. Content is comprehensive, professionally presented, and well-structured.
  3. Strong focus on education, research, and technology transfer.
  4. Multiple social media channels linked, indicating active engagement.
  5. No explicit contact emails or phone numbers found in the HTML content.
  6. No visible cookie consent mechanism despite GDPR compliance indications.
  7. Use of Matomo analytics with cookies disabled for privacy.
  8. No security.txt or explicit incident response contact information found.
  9. No vulnerability disclosure or security policy pages detected.
  10. Good use of modern JavaScript libraries and frameworks.
Technical notes

Notes

The website uses a custom CMS with a modern front-end stack including Bootstrap for responsive design, jQuery UI for UI components, Fancybox for media display, and Tippy.js for tooltips. Analytics are handled by Matomo with cookies disabled, reflecting privacy awareness. Scripts are loaded asynchronously or deferred to improve performance. The site is mobile-optimized and accessible, with semantic HTML and ARIA attributes. Navigation is clear and hierarchical, supporting user experience. Performance is moderate, with potential for optimization in image loading and script bundling. No major technical debt or obsolete technologies detected, indicating ongoing maintenance and modernization efforts.
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 uni-stuttgart.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-stuttgart.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.