Skip to main content

Security report for osu.eu

University of Ostrava · Education · Czech Republic

Medium risk. 5 critical or high findings in GDPR outside view and Security headers.

Security score

73/100

Risk levelMedium

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

The University of Ostrava is a reputable higher education institution based in the Czech Republic, offering a broad range of academic programs including bachelor's, master's, and doctoral degrees primarily taught in English. It holds a growing position among Central European universities, emphasizing quality education, affordability, and hospitality. The university operates multiple faculties and institutes under its domain, reflecting a comprehensive academic and research environment. The website is professionally designed with clear navigation and a strong brand presence, targeting prospective students, researchers, and academic partners internationally. Technically, the website employs a traditional web stack with jQuery and jQuery UI libraries, along with Lightbox and FontAwesome for UI elements. The site is mobile responsive and implements essential security headers and HTTPS enforcement, though some security headers could be enhanced. Cookie consent and GDPR compliance mechanisms are in place, reflecting good privacy practices. The WHOIS data is privacy protected as per EURid policies, which is typical for .eu domains and justified for an educational institution. Security posture is solid with no visible vulnerabilities or exposed sensitive data. However, the use of an outdated jQuery version and absence of a security.txt or vulnerability disclosure page are areas for improvement. The site lacks a clearly identified terms of service page, which could be addressed to improve legal transparency. Overall, the website demonstrates a mature digital presence with good security and privacy compliance, suitable for its educational mission. Strategically, the university should focus on updating its technical stack, enhancing security headers, and publishing formal policies such as terms of service and vulnerability disclosure to strengthen trust and compliance. Continued investment in accessibility and performance optimization will further improve user experience and institutional reputation.

Scanned

NIS2 and GDPR posture

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

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

    • High

      Third-party services without privacy policy

      Detected services: Twitter, YouTube

      What to do: Document all third-party data sharing in your privacy policy

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

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

Keep watching osu.eu

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. 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
85
Security headers
60
Email security
80
DNS health
90
Network security
100
GDPR outside view
25
Average
73

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 osu.eu, from OffSeq Breach.

Total records
3
Employees
0
Customers
3
Third parties
0
Weak passwords
33%

2 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 osu.eu.

Select it in the checkout above.

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

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 of Ostrava operates as a medium-sized educational entity within the Czech Republic, serving a diverse international student body and academic community. Its business model centers on delivering accredited academic programs and fostering research initiatives, supported by multiple faculties and specialized institutes. The university leverages partnerships with Microsoft 365, Moodle, and other academic platforms to enhance its service offerings. Revenue streams likely include tuition fees, research grants, and public funding. The institution maintains a strong online presence with dedicated subdomains for faculties and services, indicating a decentralized but cohesive operational structure. Growth indicators include active event calendars, summer schools, and international cooperation strategies. The university's strategic ecosystem includes social media engagement and compliance with GDPR, positioning it well within the European higher education market.

Security posture

The University of Ostrava's website demonstrates a good security maturity level with enforced HTTPS, Content Security Policy headers, and cookie consent mechanisms aligned with GDPR requirements. No sensitive information is exposed in the HTML content, and no outdated or vulnerable libraries beyond jQuery 1.12.2 were detected. The absence of a security.txt file and vulnerability disclosure policy suggests limited formal incident response transparency. There is no explicit evidence of dedicated security frameworks such as ISO 27001 or NIST. Incident response contact channels are not publicly listed, which could hinder timely reporting of security issues. Overall, the security posture is adequate for an educational institution but could be improved by adopting formal security policies, updating libraries, and publishing incident response information.

Recommendations

  1. Update JavaScript libraries, especially jQuery, to the latest secure versions to mitigate known vulnerabilities.
  2. Implement additional HTTP security headers such as Strict-Transport-Security, X-Frame-Options, and X-Content-Type-Options.
  3. Publish a clear terms of service page to enhance legal transparency and user trust.
  4. Create and publish a security.txt file and vulnerability disclosure policy to facilitate responsible security reporting.
  5. Enhance accessibility features to improve compliance with accessibility standards and user experience for all visitors.

Contact details published on the site

Addresses
Legal name
University of Ostrava
VAT number
CZ61988987
Registration number
61988987
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
University of Ostrava
Description
University of Ostrava is a young and rising university in Central Europe offering quality, affordability, and hospitality in English taught Bachelors, Masters, and Doctoral degrees.
Key services
Academic degree programs, Research initiatives, International cooperation, Student services and life, Counseling and career center
Content quality
good
Branding
consistent

Technology

Stack
jQuery 1.12.2, jQuery UI 1.11.4, Lightbox, FontAwesome
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Content Security Policy to upgrade insecure requests
  • No sensitive data exposed in HTML
  • Cookie consent mechanism implemented

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is professionally designed and well-structured.
  2. Content is comprehensive and relevant to higher education and research.
  3. Strong presence of official university branding and multiple subdomains for faculties.
  4. Cookie consent and GDPR compliance are implemented.
  5. No visible security vulnerabilities or exposed sensitive data.
  6. WHOIS data is privacy protected as per EURid policy, no registrant details publicly available.
  7. No evidence of advertising or tracking beyond essential cookies.
  8. Social media presence includes Facebook, Instagram, Twitter (X), and YouTube.
  9. No terms of service page explicitly found.
  10. No security.txt or vulnerability disclosure page detected.
Technical notes

Notes

The website uses a traditional web technology stack with jQuery 1.12.2, jQuery UI 1.11.4, Lightbox, and FontAwesome for UI components. The site is structured with responsive CSS stylesheets targeting different screen sizes, indicating mobile optimization efforts. Meta tags for SEO and Open Graph are well implemented, supporting social media sharing and search engine indexing. The site enforces HTTPS and uses Content Security Policy to upgrade insecure requests, enhancing security. However, the use of older JavaScript libraries suggests some technical debt. Performance is moderate, with no explicit CDN or advanced caching mechanisms detected. Hosting provider details are not disclosed. Overall, the technical infrastructure supports the university's needs but could benefit from modernization and performance tuning.
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 osu.eu. 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 osu.eu.

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.