Skip to main content

Security report for elte.hu

Eötvös Loránd Tudományegyetem · Education · Hungary

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

Security score

50/100

Risk levelMedium

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

Eötvös Loránd Tudományegyetem (ELTE) is a leading Hungarian university with a long-established presence since 1992. The website serves as a comprehensive portal for students, researchers, staff, and the public, offering information on education, research, innovation, and university life. The institution holds a strong market position in the education sector in Hungary, supported by a mature domain and consistent branding. Technically, the website uses a custom CMS with Loginet technologies, integrates Google Fonts, Analytics, and reCAPTCHA, and provides a mobile-optimized experience. However, the absence of a valid SSL certificate and HTTPS support is a critical security weakness. Privacy compliance is addressed with visible cookie consent and a comprehensive privacy policy. Overall, the site demonstrates good content quality and business credibility but requires urgent security improvements.

Scanned

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

8 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

  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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • 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 elte.hu

This scan found 19 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
50
Security headers
15
Email security
50
DNS health
85
Network security
100
GDPR outside view
0
Average
50

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

ELTE operates as a public higher education institution focusing on academic programs, research, and innovation. Its business model relies on government funding and research grants. The website targets students, academic staff, alumni, and the general public interested in higher education. The university maintains partnerships and subsidiary domains related to alumni and research projects. The site’s content and structure reflect a professional academic institution with a broad service offering including education, research, innovation, and community engagement. The presence of social media channels and event listings indicates active outreach and engagement strategies.

Security posture

The website currently lacks a valid SSL certificate and does not support HTTPS or modern TLS protocols, exposing users to potential data interception risks. Security headers are minimal, and advanced protections like HSTS, OCSP stapling, and session resumption are not enabled. No vulnerability disclosure or incident response contacts are found. While session cookies are used, their security attributes are unclear. The site does not expose sensitive data or known vulnerable libraries but falls short of best practices. Immediate remediation of SSL/TLS configuration and enhancement of security headers is recommended to improve the security posture and user trust.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  3. Implement OCSP stapling to improve certificate revocation checking performance and security.
  4. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  5. Review and secure session cookies with Secure and HttpOnly flags.
  6. Publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  7. Provide clear incident response contact information for security issues.
  8. Improve accessibility features to meet higher standards.
  9. Enhance SEO by adding missing meta descriptions and keywords where appropriate.

Contact details published on the site

Addresses
Technical notes

Notes

The website runs on an Apache 2.4.29 server on Ubuntu, serving UTF-8 encoded HTML content. It uses jQuery 2.1.4, Google Fonts, FontAwesome icons, and integrates Google Analytics and reCAPTCHA for analytics and bot protection. The CMS appears custom-built with Loginet components for routing and carousel functionality. The site is mobile responsive with separate navigation for mobile and desktop. Performance metrics are not provided but the site loads a moderate number of resources. The lack of HTTPS and modern TLS protocols is a significant technical deficiency. DNS records show a single IPv4 address and Microsoft Outlook-based email protection with SPF configured. No DNSSEC or CAA records are present. Overall, the technical infrastructure is functional but requires modernization and security enhancements.
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. 64/100Medium32 findingsView report
Reviews of this site

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

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.