Skip to main content

Security report for tugraz.at

Technische Universität Graz · Education · Austria

Medium risk. 5 critical or high findings in GDPR outside view and SSL/TLS.

Security score

52/100

Risk levelMedium

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

Technische Universität Graz (TU Graz) is a prominent technical university in Austria, offering a wide range of academic programs and conducting extensive research activities. The website serves as a comprehensive portal for students, researchers, international visitors, and industry partners, providing detailed information about study programs, research fields, cooperation opportunities, and career services. The site is well-branded and professionally maintained, reflecting the institution's reputation and commitment to education and innovation. Technically, the website is built on the TYPO3 CMS platform, leveraging Apache and Varnish caching for performance. However, a critical security gap exists due to the absence of a valid SSL certificate and HTTPS support, which undermines the security posture despite the presence of several security headers. Privacy compliance is addressed with a comprehensive privacy policy and cookie consent mechanism, aligning with GDPR requirements. Overall, the website is content-rich and user-friendly but requires urgent security improvements to protect user data and enhance trust.

Scanned

This is an earlier scan of tugraz.at. View the latest report

NIS2 and GDPR posture

GDPR outside view
0/ 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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • 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. 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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

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

Keep watching tugraz.at

This scan found 16 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. The full timeline opens with your unlock code.

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
0
Security headers
75
Email security
50
DNS health
85
Network security
100
GDPR outside view
0
Average
52

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

TU Graz operates as a public educational institution focused on technology and engineering disciplines. Its market position is strong within Austria and Europe, supported by partnerships such as TU Austria and the Unite! European University alliance. The business model centers on education, research, and industry collaboration, with services including degree programs, research centers, and career support. The website targets prospective and current students, academic staff, researchers, and corporate partners. The presence of multiple language options and international programs indicates a global outreach strategy. The university maintains a robust digital presence with social media integration and regularly updated news content, supporting engagement and visibility.

Security posture

The website demonstrates moderate security awareness through the implementation of multiple security headers like Content-Security-Policy, X-Content-Type-Options, and X-XSS-Protection. Cookies are set with Secure and HttpOnly flags. However, the lack of a valid SSL certificate and absence of HTTPS severely compromise the security posture, exposing users to risks such as data interception and man-in-the-middle attacks. No advanced SSL features like OCSP stapling or session resumption are enabled. There is no visible security policy or incident response contact information, which limits transparency and readiness for security incidents. The site does not provide a vulnerability disclosure policy or security.txt file, which are best practices for responsible vulnerability management.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site immediately.
  2. Configure the web server to support modern TLS protocols (TLS 1.2 and TLS 1.3) and disable insecure protocols.
  3. Enhance HSTS policy by enabling includeSubDomains and preload directives to enforce HTTPS usage.
  4. Publish a clear security policy and provide incident response contact channels (e.g., security@ or abuse@ emails).
  5. Implement a vulnerability disclosure program and consider adding a security.txt file to facilitate responsible reporting.
  6. Review and tighten Content-Security-Policy to reduce reliance on 'unsafe-inline' and 'unsafe-eval' directives.
  7. Regularly audit third-party scripts and tracking tools to ensure privacy compliance and minimize user tracking.
  8. Improve performance metrics and mobile optimization further if possible, based on detailed performance analysis.

Contact details published on the site

Addresses
Technical notes

Notes

The website is powered by TYPO3 CMS, a mature and extensible open-source content management system widely used in academia. The server runs Apache with Varnish caching to improve content delivery speed. The site uses multiple CSS and JavaScript resources hosted on the same domain, indicating centralized asset management. The presence of structured data (JSON-LD) and Open Graph tags supports SEO and social media sharing. However, performance data was not provided, so load times and resource counts are unknown. Accessibility features such as skip navigation links and language attributes are present, indicating good compliance with accessibility standards. The lack of HTTPS is a major technical deficiency that impacts security and user trust. The site integrates several analytics and marketing tools including Google Analytics, Facebook, LinkedIn, and Google Tag Manager, which require careful privacy 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. 79/100 +27Low27 findingsView report
  2. 52/100Medium24 findingsView report
Reviews of this site

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

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.