Skip to main content

Security report for medunigraz.at

Medizinische Universität Graz · Healthcare · Austria

High risk. 7 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

47/100

Risk levelHigh

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

Medizinische Universität Graz operates as a leading medical university in Austria, focusing on education, research, and patient care. The website reflects a comprehensive digital presence with detailed information on academic programs, research initiatives, campus life, and services for students and staff. The institution targets students, researchers, healthcare professionals, and patients, positioning itself as a center of innovative medical education and research in southern Austria. Technically, the site is built on TYPO3 CMS with modern frontend libraries like jQuery and Bootstrap, and it employs Matomo for analytics with privacy-conscious settings such as Do Not Track enabled. However, a critical security gap exists due to the absence of a valid SSL certificate and HTTPS support, which undermines user trust and data security. The site includes a privacy policy consistent with GDPR but lacks a cookie consent mechanism and visible security or incident response policies. Overall, the website is professional and content-rich but requires urgent security improvements to meet modern standards.

Scanned

This is an earlier scan of medunigraz.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

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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  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

  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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

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

This scan found 17 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
40
Email security
50
DNS health
90
Network security
100
GDPR outside view
0
Average
47

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

The university maintains a strong market position as a public healthcare and education provider with a large user base of over 5,000 students and 2,500 staff. Its business model centers on academic programs in human medicine, dentistry, nursing science, and doctoral studies, supplemented by extensive research projects and patient services. The site links to numerous partner organizations and research centers, indicating a broad collaborative ecosystem. The presence of multiple quicklinks and detailed navigation supports user engagement and operational transparency. The university's digital footprint includes social media channels and specialized portals for research and learning, enhancing its outreach and service delivery. No commercial or e-commerce activities are evident, consistent with its public institution status.

Security posture

Security posture is currently weak due to the lack of HTTPS and valid SSL certificates, exposing users to potential data interception risks. While some security headers like Strict-Transport-Security and X-Content-Type-Options are present, they are ineffective without proper TLS configuration. The absence of OCSP stapling, session resumption, and vulnerability disclosures further limits security maturity. No incident response or security policy information is publicly available, which may hinder timely handling of security events. The site does not appear to use any WAF or advanced security mechanisms. Immediate remediation of SSL/TLS issues and implementation of comprehensive security policies are recommended to enhance trust and compliance.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable and configure modern TLS protocols (TLS 1.2 or TLS 1.3) and disable insecure protocols.
  3. Implement a cookie consent mechanism to comply with GDPR and enhance user privacy transparency.
  4. Publish clear security policies and incident response contact information to improve security posture and user trust.
  5. Regularly audit and update security headers, enable OCSP stapling, and session resumption to improve performance and security.

Contact details published on the site

Addresses
Technical notes

Notes

The website uses a mature CMS platform (TYPO3) with a stable Apache server environment. Frontend technologies include jQuery and Bootstrap, supporting responsive and accessible design. SEO is well addressed with meta tags, Open Graph, Twitter cards, and JSON-LD structured data. The site is multilingual (German and English) and includes accessibility features such as font size adjustment and contrast modes. Performance data is unavailable, but the site structure and assets suggest moderate loading times. DNS configuration is standard with multiple authoritative name servers and MX records. However, the SSL configuration is critically lacking, with no TLS protocols enabled and no valid certificate, which is a major technical risk. The CAA DNS records appear malformed or undefined, which should be corrected to improve certificate issuance security.
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/100Medium35 findingsView report
Reviews of this site

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