Skip to main content

Security report for oekumenisches-stundengebet.de

Ökumenisches Stundengebet e. V. · Other · Germany

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

Security score

55/100

Risk levelMedium

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

Ökumenisches Stundengebet e. V. operates as a small non-profit network focused on promoting ecumenical liturgical spirituality in Germany. The organization leverages shared traditions across Christian confessions to foster community through the celebration of the daily hours (Tagzeitenliturgie). Their website serves as an informational and resource hub, offering materials, consultation, and networking opportunities for religious communities and individuals interested in this spiritual practice. The site is professionally designed with clear navigation and good mobile optimization, reflecting a solid digital presence for a niche religious organization. Technically, the website is built on WordPress 6.8.3, utilizing common plugins such as Contact Form 7 and GDPR Cookie Compliance. Hosting is provided via rzone.de, with HTTPS enforced and cookie consent mechanisms in place, indicating a good baseline for security and privacy compliance. The absence of advanced security headers and incident response information suggests room for improvement in security maturity. No analytics or advertising tools were detected, aligning with the organization's non-commercial nature. From a security perspective, the site demonstrates good practices including HTTPS usage and GDPR compliance, with no visible vulnerabilities or exposed sensitive data. However, the lack of a published security policy, incident response contacts, and vulnerability disclosure mechanisms indicates limited transparency and preparedness for security incidents. The WHOIS data is minimal but consistent with a small non-profit entity, with no suspicious patterns detected. Overall, the website is safe, trustworthy, and well-suited for its target audience. Strategic recommendations include enhancing security transparency, adding incident response information, and implementing additional security headers to strengthen the security posture. These steps will improve trust and resilience while maintaining compliance with privacy regulations.

Scanned

NIS2 and GDPR posture

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

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

  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

  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 oekumenisches-stundengebet.de

This scan found 25 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
62
Security headers
15
Email security
65
DNS health
70
Network security
20
GDPR outside view
95
Average
55

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 organization occupies a specialized niche within the religious and spiritual sector, focusing on ecumenical liturgical practices. Its business model is non-profit, centered on community building, resource sharing, and spiritual networking rather than commercial revenue generation. The target audience includes religious communities, clergy, and laypersons interested in ecumenical worship practices. The website's content and structure support these goals effectively, with sections dedicated to news, ideas, consultation, materials, and networking. Partnerships and events are highlighted, though no external partner domains were identified. The organization's market position is that of a trusted, small-scale network with a clear mission and consistent branding. Growth potential may be limited by the niche focus but supported by strong community engagement.

Security posture

The website exhibits a moderate to good security maturity level. HTTPS is properly implemented, and GDPR compliance is actively managed through a cookie consent plugin and privacy policy. No security headers were detected in the HTML content, which could be improved to mitigate common web vulnerabilities. The absence of incident response contacts and vulnerability disclosure policies suggests limited readiness for security incidents. No exposed sensitive data or vulnerable libraries were found, and forms appear to be standard with no obvious security flaws. Overall, the security posture is adequate for a small non-profit but would benefit from enhanced transparency and technical controls.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and commitments.
  2. Add clear incident response contact information such as security@ or abuse@ email addresses.
  3. Implement security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Regularly audit and update WordPress core and plugins to mitigate vulnerabilities.
  5. Consider adding a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Ökumenisches Stundengebet e. V.
Description
Netzwerk für liturgische Spiritualität, das die gemeinsame Tradition der Konfessionen nutzt und neue Sprach- und Singformen öffnet. Fokus auf Tagzeitenliturgie als Antwort auf Herausforderungen in Gemeinden, Förderung des allgemeinen Priestertums aller Gläubigen und ökumenische Feier des Stundengebets.
Key services
Networking for liturgical spirituality, Providing materials and downloads, Consultation and advice, Organizing events and partnerships
Content quality
good
Branding
consistent

Technology

Stack
WordPress 6.8.3, jQuery 3.7.1, Contact Form 7 plugin, GDPR Cookie Compliance plugin
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner implemented
  • No exposed sensitive data in HTML
  • Use of GDPR compliance plugin

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 fully accessible with no blocking or WAF challenges.
  2. Content is focused on ecumenical liturgical spirituality and community networking.
  3. Uses WordPress CMS with standard plugins for contact forms and GDPR compliance.
  4. No exposed sensitive data or obvious security vulnerabilities detected in HTML.
  5. No explicit or adult content present; safe for general audiences.
  6. Limited business and security policy information publicly available.
  7. No visible analytics or advertising/tracking services detected.
Technical notes

Notes

The website is built on a modern WordPress platform (version 6.8.3) with standard plugins for contact forms and GDPR compliance. It uses jQuery 3.7.1 and loads fonts from Google Fonts. Hosting is provided by rzone.de, as indicated by the nameservers. The site is mobile optimized and accessible, with good SEO practices including meta tags and structured navigation. Performance is moderate, with no major issues detected in the HTML content. There is no evidence of advanced frameworks or custom backend technologies. The technical setup is appropriate for a small non-profit organization but could be enhanced with additional security and performance optimizations.
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 oekumenisches-stundengebet.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 oekumenisches-stundengebet.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.