Skip to main content

Security report for lilahilfe.org

LILA HILFE e.V. · Non-profit · Germany

Medium risk. 6 critical or high findings in Email security, Security headers and 2 other checks.

Security score

65/100

Risk levelMedium

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

Lila Hilfe e.V. is a German non-profit feminist solidarity organization dedicated to supporting women affected by gender-based violence and structural discrimination. The organization operates primarily within Germany, providing financial aid, resources, and community support to its target audience. The website reflects a clear mission and offers membership and donation options to sustain its activities. Technically, the site is built on a modern React and Next.js framework, ensuring fast performance, excellent mobile optimization, and good accessibility. The content is rich, professionally presented, and highly relevant to its audience. Security-wise, the site uses HTTPS and avoids exposing sensitive data, but lacks explicit security headers and formal security policies. Privacy compliance is moderate, with a comprehensive privacy policy but no visible cookie consent mechanism. Overall, the domain appears legitimate despite the absence of WHOIS data, likely due to privacy protection common in non-profits. The site maintains a high trust level with clear branding and social media presence.

Scanned

NIS2 and GDPR posture

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

6 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  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 Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • 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 lilahilfe.org

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
72
Security headers
35
Email security
60
DNS health
70
Network security
100
GDPR outside view
53
Average
65

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

Lila Hilfe e.V. occupies a niche position in the non-profit sector focused on feminist and gender-based violence support within Germany. Its business model relies on donations, memberships, and community solidarity. The organization demonstrates strong engagement through stories of solidarity and events, indicating active community involvement. The lack of explicit contact emails or phone numbers suggests a preference for controlled communication via contact forms, enhancing privacy and security. The website's modern technical stack and minimal tracking reflect a privacy-conscious approach aligned with its mission. No partnerships or subsidiaries were identified, indicating an independent operation. The organization's market presence is modest but credible, with clear growth indicators such as membership numbers and financial support statistics.

Security posture

The website demonstrates a basic to moderate security posture. HTTPS is enforced, ensuring encrypted communications. However, the absence of visible security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options reduces defense-in-depth. No security or incident response policies are published, and no dedicated security contact channels are provided. The contact forms should be reviewed for anti-spam and input validation measures. No vulnerable libraries or exposed sensitive data were detected in the HTML content. The use of minimal third-party scripts and privacy-friendly analytics (Umami) reduces attack surface and privacy risks. Overall, the security posture is adequate for a small non-profit but could be improved with standard best practices and transparency.

Recommendations

  1. Implement and configure security headers including CSP, HSTS, and X-Frame-Options to enhance protection against common web attacks.
  2. Publish a clear security policy and incident response plan, including dedicated security contact channels such as security@ or abuse@ emails.
  3. Add a cookie consent banner and explicit cookie policy to improve privacy compliance and user transparency.
  4. Enhance contact forms with anti-spam measures and input validation to prevent abuse and injection attacks.
  5. Regularly audit third-party scripts and dependencies to ensure no vulnerable libraries are included.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
LILA HILFE e.V.
Description
We are a group of feminist women who founded Lila Hilfe, an association that we understand as a non-partisan and cross-movement solidarity organization of the (feminist) women's movement. Together, we aim to organize solidarity within the Federal Republic of Germany for all those who are subjected to misogynistic violence and are sexistly discriminated against and structurally exploited due to their gender.
Key services
Financial support for women affected by gender-based violence, Organizing solidarity and mutual support, Providing information and resources, Membership and donation opportunities
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, JavaScript, CSS
Frameworks
Next.js
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS assumed (URL is https)
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Umami
Tracking level
minimal
Privacy practices
good

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is fully accessible with rich content and no blocking detected
  2. No explicit contact emails or phone numbers publicly listed, only contact form
  3. No visible security.txt or vulnerability disclosure policy
  4. No cookie consent banner or explicit cookie policy detected
  5. Social media presence on Facebook and Instagram
  6. WHOIS data is privacy protected or unavailable
  7. Website uses modern React/Next.js stack with good performance and mobile optimization
  8. No advertising or tracking networks detected except privacy-friendly analytics (Umami)
  9. Content is safe and targeted at general audience interested in feminist solidarity
Technical notes

Notes

The website is built using React and Next.js, leveraging modern JavaScript and CSS for a responsive and performant user experience. The site is well-structured with clear navigation and semantic HTML elements. Preloading of images and fonts is used to optimize loading times. The absence of a traditional CMS suggests a custom or headless CMS backend. Analytics are handled via Umami, a privacy-focused tool, indicating a commitment to user privacy. No explicit hosting provider information was found. The site is mobile-optimized and accessible, with good SEO practices including meta descriptions and structured content. Technical risks are low, but the lack of security headers and formal policies represent areas for improvement.
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 lilahilfe.org. 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 lilahilfe.org.

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.