Skip to main content

Security report for zsluka.net

Základní škola a Mateřská škola Luka nad Jihlavou, příspěvková organizace · Education · Czech Republic

High risk. 9 critical or high findings in Network security, Security headers and 3 other checks.

Security score

46/100

Risk levelHigh

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

Základní škola a Mateřská škola Luka nad Jihlavou is a small public educational institution serving primary and nursery education needs for Luka nad Jihlavou and surrounding villages in the Czech Republic. The website provides comprehensive information about the school, its classes, extracurricular activities, and administrative contacts, targeting students, parents, and the local community. The institution positions itself as a key local educational provider with modern facilities and a supportive environment. Technically, the website is built on a custom CMS platform (IPO Redakční systém) using jQuery and jQuery UI libraries, with integration of Google reCAPTCHA and Matomo analytics for user tracking. The site is mobile responsive and implements cookie consent mechanisms, reflecting a moderate level of digital maturity. Performance is moderate, with good SEO and basic accessibility features. From a security perspective, the site enforces HTTPS and uses reCAPTCHA to protect forms, but lacks explicit security headers and published security policies or incident response contacts. The absence of WHOIS registration data is a notable anomaly, potentially indicating domain registration issues or privacy protection, which slightly reduces trustworthiness. Overall, the security posture is adequate but could be improved with better header configurations and transparency. The overall risk assessment is moderate with no critical vulnerabilities detected. Strategic recommendations include enhancing security headers, publishing security and incident response policies, improving accessibility compliance, and clarifying domain registration status to strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
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

9 findings rated critical or high. Fix these first.

  1. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
  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"

    • 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';…
  3. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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

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

Keep watching zsluka.net

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
72
Security headers
30
Email security
45
DNS health
80
Network security
0
GDPR outside view
50
Average
46

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 · found on this site
  • 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 school operates as a public educational entity focused on delivering primary and nursery education services to a defined local community. Its business model is non-commercial, funded likely by government or local authorities. The website supports communication with parents and students, providing updates, schedules, and administrative documents. The institution's competitive advantage lies in its established local presence and comprehensive educational offerings. There is no indication of revenue streams beyond public funding. The partnership ecosystem includes local government and service providers like Antee s.r.o. for web development. Growth indicators are limited due to the nature of the institution, but the website reflects active engagement with its audience through news and updates.

Security posture

The website demonstrates a basic to moderate security maturity level. HTTPS is enforced, and Google reCAPTCHA is used to mitigate automated abuse. Matomo analytics is configured with cookie disabling by default, indicating privacy awareness. However, the absence of security headers such as Content Security Policy, HSTS, and X-Frame-Options reduces defense-in-depth. No published security policies or incident response contacts limit transparency and preparedness perception. No vulnerabilities or exposed sensitive data were detected in the analysis. Compliance with GDPR is suggested by cookie consent and privacy statements but lacks explicit data protection officer contact or detailed policies. Overall, the security posture is sufficient for a public educational website but could benefit from enhancements to align with best practices.

Recommendations

  1. Implement and enforce security headers including CSP, HSTS, and X-Frame-Options to improve protection against common web attacks.
  2. Publish a clear security policy and incident response contact information to enhance transparency and preparedness.
  3. Clarify domain registration status and ensure WHOIS data is accurate and publicly available to improve trustworthiness.
  4. Enhance accessibility features to meet higher standards and improve user experience for all visitors.
  5. Regularly update third-party libraries and CMS components to mitigate potential vulnerabilities.

Contact details published on the site

Addresses
Legal name
Základní škola a Mateřská škola Luka nad Jihlavou, příspěvková organizace
Registration number
75023024
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Základní škola a Mateřská škola Luka nad Jihlavou, příspěvková organizace
Description
Základní škola Luka nad Jihlavou je úplná škola s 9 postupnými ročníky, spádovou školou pro okolní vesnice. Poskytuje vzdělání pro 1. i 2. stupeň základní školy a mateřskou školu s moderním vybavením a zázemím.
Key services
primary education, nursery education, school canteen services, after-school care, extracurricular activities
Content quality
good
Branding
consistent

Technology

Stack
jQuery 3.0.0, jQuery UI 1.8.20, Google reCAPTCHA, Matomo Analytics, PHP backend (implied by .php URLs), custom CMS (IPO Redakční systém)
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Cookie consent implemented
  • Google reCAPTCHA for forms

Analytics and tracking

Services
Matomo
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Matomo
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is focused on education for local community in Czech Republic.
  3. No privacy policy page explicitly found but accessibility statement present.
  4. Cookie consent banner is implemented and functional.
  5. No explicit security or incident response policies published.
  6. WHOIS data is missing or domain not found in WHOIS database, which is unusual.
  7. Website uses Matomo analytics with cookie disabling by default.
  8. No social media links detected.
  9. Contact information is clearly presented in footer.
  10. Website uses HTTPS with no visible security warnings.
Technical notes

Notes

The website uses a custom CMS platform with jQuery 3.0.0 and jQuery UI 1.8.20, which are somewhat outdated but functional. Google reCAPTCHA integration helps protect forms from abuse. Matomo analytics is used for privacy-respecting user tracking. The site is mobile responsive and includes SEO-friendly meta tags and structured navigation. Performance is moderate, with some opportunities for optimization. The hosting provider is not explicitly identified. The site uses HTTPS with valid SSL configuration. There is no evidence of modern JavaScript frameworks or advanced backend technologies. Overall, the technical infrastructure is stable but could benefit from modernization and improved security configurations.
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 zsluka.net. 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 zsluka.net.

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.