Skip to main content

Security report for theresienschule.de

Katholische Theresienschule Berlin · Education · Germany

Medium risk. 4 critical or high findings in Security headers, SSL/TLS and 1 other check.

Security score

61/100

Risk levelMedium

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

Katholische Theresienschule Berlin is a well-established Catholic educational institution operating under the Archdiocese of Berlin. The website serves as an information hub for students, parents, and the school community, providing news, event updates, and service information. The school emphasizes community engagement and offers a variety of extracurricular activities and workshops. The domain age and content reflect a mature and credible organization with a long history dating back over a century. Technically, the website is built on Joomla CMS with modern web technologies including jQuery and Bootstrap. It features a GDPR-compliant cookie consent mechanism and is served over HTTPS with good security practices. The site is mobile-optimized and provides a good user experience with clear navigation and relevant content. However, some security headers and formal security policies are missing. From a security perspective, the site demonstrates a solid baseline with HTTPS enforcement and cookie management. There are no visible vulnerabilities or exposed sensitive data. The absence of a published security policy or incident response contact is a gap that could be addressed to improve trust and preparedness. Privacy compliance is strong with clear policies and consent mechanisms. Overall, the website is trustworthy, professional, and well-maintained, suitable for its educational purpose. Strategic recommendations include enhancing security transparency, adding incident response information, and implementing additional security headers to further harden the site against potential threats.

Scanned

NIS2 and GDPR posture

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

4 findings rated critical or high. Fix these first.

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

  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.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1
    • High

      Weak SSL Key Length

      SSL certificate uses 384-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

  3. Network security

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

    • High

      High-Risk Service Exposed: FTP

      Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer

      What to do: Consider restricting access to FTP or implementing strong authentication

      • 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

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

Keep watching theresienschule.de

This scan found 21 issues across 5 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
42
Security headers
55
Email security
80
DNS health
70
Network security
20
GDPR outside view
100
Average
61

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 school operates in the education and non-profit sectors, targeting students and their families in Berlin. Its business model is centered on providing quality Catholic education and community services. The institution benefits from its affiliation with the Archdiocese of Berlin, which supports its legitimacy and market position. The website reflects a medium-sized organization with a stable presence and active community engagement. Partnerships with the Archdiocese and related educational platforms are evident. The school leverages digital tools moderately, focusing on content delivery and community interaction rather than aggressive marketing or analytics. Growth indicators include regular event updates and active social media presence on Instagram. The school maintains a clear brand identity and consistent messaging aligned with its religious and educational mission. Revenue streams are typical for educational institutions, likely including tuition, donations, and church support. The partnership ecosystem is limited but focused on relevant educational and religious organizations.

Security posture

The website exhibits a good security posture with HTTPS enabled and a GDPR-compliant cookie consent mechanism that includes opt-in and blocking of external cookies. No critical vulnerabilities or exposed sensitive data were detected in the HTML content. However, the absence of explicit security headers such as Content-Security-Policy, X-Frame-Options, and others reduces the overall security hardening. There is no visible security policy or incident response information, which are important for transparency and readiness. The site uses third-party scripts including jQuery and GDPR plugins, which should be regularly audited for vulnerabilities. The cookie consent configuration shows attention to privacy and compliance. Overall, the security maturity is moderate to good but could be improved with formal policies and additional technical controls.

Recommendations

  1. Publish a formal security policy and incident response plan accessible on the website.
  2. Implement security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Regularly audit and update third-party libraries and plugins to mitigate vulnerabilities.
  4. Provide clear contact channels for security incidents, e.g., security@ or abuse@ email addresses.
  5. Enhance accessibility features and SEO metadata for improved user experience and discoverability.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Katholische Theresienschule Berlin
Description
Katholische Theresienschule in Trägerschaft des Erzbistums Berlin
Key services
School education, Student support services, Extracurricular activities, Events and workshops
Content quality
good
Branding
consistent

Technology

Stack
Joomla CMS, jQuery, Bootstrap (implied by classes and carousel), GDPR Cookie Consent Plugin
Frameworks
Joomla
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent with opt-in mechanism
  • Blocking of external cookies and session cookie blocking configured

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 uses Joomla CMS with GDPR-compliant cookie consent
  2. Clear and comprehensive privacy and cookie policies present
  3. Contact information is complete and prominently displayed
  4. No signs of security policy or incident response information
  5. No advertising or tracking services detected
  6. Content is focused on school news, events, and services
  7. No suspicious or malicious content detected
Technical notes

Notes

The website is built on Joomla CMS with a modern front-end stack including jQuery and Bootstrap components. It uses a GDPR cookie consent plugin with advanced configuration for blocking and consent management. The site is served over HTTPS with a valid SSL certificate. Performance is moderate with no major issues detected, though some optimization opportunities exist. Mobile responsiveness is good, and navigation is clear and user-friendly. The site lacks some advanced accessibility features and security headers, which could be improved. Hosting provider details are not explicitly available from the content. Overall, the technical infrastructure is stable and suitable for the institution's needs.
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 theresienschule.de. 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 theresienschule.de.

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.