Skip to main content

Security report for robert-enke-stiftung.de

Robert-Enke-Stiftung · Non-profit · Germany

Medium risk. 5 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

64/100

Risk levelMedium

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

The Robert-Enke-Stiftung is a German non-profit foundation dedicated to promoting open dialogue about depression and other mental illnesses, as well as supporting suicide prevention projects. The website reflects a strong commitment to mental health awareness through educational initiatives, social engagement opportunities, and partnerships with prominent sports organizations. The foundation targets a broad audience including individuals affected by mental health issues, students, and the sports community. The business model is centered on non-profit activities, fundraising, and community outreach. Technically, the website is built on the Webflow platform, leveraging modern web technologies such as jQuery, Lottie animations, and SVG graphics. It is hosted on a CDN ensuring fast performance and excellent mobile optimization. The site includes a cookie consent mechanism compliant with GDPR, enhancing privacy compliance. Navigation is clear and content is professionally presented, contributing to a positive user experience. From a security perspective, the site enforces HTTPS and uses a cookie consent banner, but lacks explicit security policy pages or incident response contacts. No critical vulnerabilities or exposed sensitive data were detected. The WHOIS data shows consistent domain registration with no suspicious patterns, supporting the legitimacy of the organization. Overall, the website demonstrates a high level of professionalism, security, and compliance suitable for a non-profit organization focused on sensitive health topics. Strategic improvements could include publishing a dedicated security policy, vulnerability disclosure information, and enhancing security headers to further strengthen the security posture.

Scanned

NIS2 and GDPR posture

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

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 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. GDPR outside view

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

    • 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

  3. 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 256-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

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

Keep watching robert-enke-stiftung.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
57
Security headers
30
Email security
70
DNS health
60
Network security
100
GDPR outside view
68
Average
64

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 robert-enke-stiftung.de, from OffSeq Breach.

No leaked records found

Breach holds no records for robert-enke-stiftung.de right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The Robert-Enke-Stiftung occupies a recognized position within the German mental health non-profit sector, leveraging partnerships with major football organizations such as Deutscher Fussball-Bund (DFB), DFL e.V., and Hannover 96. Its competitive advantage lies in combining mental health advocacy with sports community engagement and innovative educational tools like Virtual Reality experiences. Revenue streams primarily come from donations and grants, supported by clear calls to action on the website. The foundation targets individuals affected by mental health issues, students interested in social engagement, and the sports community. Growth indicators include active campaigns, awards, and social media presence. The partnership ecosystem enhances credibility and outreach effectiveness.

Security posture

The current security maturity level is moderate to good. The website uses HTTPS and a cookie consent mechanism, indicating awareness of privacy and security best practices. However, the absence of a published security policy, incident response contacts, and vulnerability disclosure mechanisms represents gaps in compliance and readiness. No security headers were detected in the provided data, which could improve protection against common web attacks. No vulnerabilities or exposed sensitive data were found in the HTML content. The site would benefit from enhanced security documentation and technical controls to align with GDPR and NIS2 requirements, improving incident response readiness and security culture.

Recommendations

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

Automated reading of the public site. Ratings are indicative.

Business

Company
Robert-Enke-Stiftung
Description
Die Robert-Enke-Stiftung setzt sich für einen offenen Umgang mit Depression und anderen psychischen Erkrankungen ein und unterstützt Projekte zur Prävention von Suiziden.
Key services
Mental health awareness campaigns, Support for depression and suicide prevention projects, Educational initiatives including Virtual Reality experiences, Scholarships and awards (e.g., Mental Health Awareness Award), Opportunities for social engagement (FSJ, dual studies)
Content quality
excellent
Branding
consistent

Technology

Stack
Webflow, jQuery 3.5.1, CookieScript, Lottie animations, SVG graphics
Frameworks
Webflow CMS
Platforms
Webflow hosting
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner implemented
  • No exposed sensitive data in HTML

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
CookieScript
Marketing tools
CookieScript
Transparency
basic

Site quality

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

Key observations

  1. Website is professionally designed and well-structured.
  2. Strong focus on mental health awareness and suicide prevention.
  3. Clear calls to action for donations, volunteering, and participation.
  4. Cookie consent implemented with detailed user options.
  5. No visible security policy or incident response information.
  6. No terms of service page found.
  7. Social media presence on Facebook, Twitter, Instagram, YouTube.
  8. No exposed sensitive data or obvious vulnerabilities in HTML content.
  9. Use of modern web technologies and CDN hosting.
Technical notes

Notes

The website is built on a modern and scalable infrastructure using Webflow CMS and CDN hosting, ensuring fast load times and excellent mobile responsiveness. The use of jQuery and Lottie animations adds interactive and visual appeal without compromising performance. SEO is supported by proper meta tags and Open Graph data. Accessibility features are present but could be further enhanced. The technical stack is well-suited for the foundation's needs, with low technical debt and opportunities for modernization primarily in security enhancements. The absence of server-side security headers and incident response mechanisms represents a technical risk that should be addressed to safeguard business operations.
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 robert-enke-stiftung.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 robert-enke-stiftung.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.