Skip to main content

Security report for lebenshilfe.at

Lebenshilfe Österreich · Non-profit · Austria

Critical risk. 10 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

25/100

Risk levelCritical

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

Lebenshilfe Österreich is a well-established non-profit organization dedicated to advocating for the rights and support of people with intellectual and multiple disabilities across Austria. Serving as the umbrella organization for regional Lebenshilfe groups, it offers services including support, advocacy, public relations, and organizes events such as the Austrian Inclusion Prize. The website reflects a mature digital presence with comprehensive content, clear navigation, and strong branding consistency targeting individuals and stakeholders interested in disability rights and inclusion. Technically, the site is built on WordPress with modern plugins like Yoast SEO and Cookiebot for consent management. It uses Apache hosting with DNS managed by easyname.eu. Accessibility features and structured data are implemented, enhancing user experience and SEO. However, performance metrics are not provided. From a security perspective, the site lacks a valid SSL/TLS certificate, exposing it to significant risks and undermining user trust. No advanced security headers or protocols are configured, and no incident response or security policies are publicly disclosed. Cookie consent is properly implemented, and privacy policies are present and GDPR compliant. Overall, while the website excels in content quality, user experience, and privacy compliance, the absence of HTTPS is a critical vulnerability that must be addressed immediately to protect users and maintain credibility. Strategic improvements in security posture and transparency around security policies are recommended to enhance trust and resilience.

Scanned

NIS2 and GDPR posture

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

10 findings rated critical or high. Fix these first.

  1. GDPR outside view

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

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  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.

    • 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

  4. 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

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

Keep watching lebenshilfe.at

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. The full timeline opens with your unlock code.

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
0
Security headers
15
Email security
50
DNS health
85
Network security
0
GDPR outside view
0
Average
25

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

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 lebenshilfe.at, from OffSeq Breach.

Total records
156
Employees
4
Customers
19
Third parties
133
Weak passwords
30%

Latest record dated 2026-03-27 · 13 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for lebenshilfe.at.

Select it in the checkout above.

Masked preview

  • –connect.noe.lebenshilfe.at2026-03-27
  • –noe.lebenshilfe.at2026-01-12
  • –connect.noe.lebenshilfe.at2025-09-04
  • –webmail.noe.lebenshilfe.at2025-06-23

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)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

Lebenshilfe Österreich holds a strong market position as the national umbrella organization for disability support and advocacy in Austria. Its business model focuses on non-profit advocacy, support services, and public engagement through events and educational initiatives. The organization targets people with disabilities, their families, and the broader community interested in inclusion. The website indicates a large operational scale with thousands of supported individuals and employees nationwide. Partnerships with regional Lebenshilfe groups and active social media presence support its outreach and influence. The organization appears stable with consistent branding and professional content, though no financial or founding year data is disclosed. The digital ecosystem includes modern CMS and marketing tools, reflecting a commitment to digital maturity.

Security posture

The current security posture is weak due to the lack of HTTPS, which is a fundamental security requirement. The absence of TLS protocols and secure cipher suites means data transmitted to and from the site is unencrypted, risking interception and tampering. Security headers are minimal, with only a referrer-policy header present. No evidence of incident response contacts, vulnerability disclosure, or security certifications is found, indicating limited transparency and preparedness. Cookie consent is implemented, supporting privacy compliance. The site should prioritize obtaining and configuring a valid SSL certificate, enabling modern TLS versions, and adding security headers such as Content-Security-Policy and X-Frame-Options. Establishing incident response contacts and publishing security policies would further improve security maturity and trust.

Recommendations

  1. Immediately install and configure a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload options to enforce secure connections.
  3. Configure modern TLS protocols (TLS 1.2 or 1.3) and strong cipher suites to protect data in transit.
  4. Implement additional security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web attacks.
  5. Publish a clear security policy and incident response contact information to enhance transparency and preparedness.
  6. Regularly audit and update all software components, including WordPress core, themes, and plugins, to reduce vulnerability exposure.
  7. Maintain and monitor cookie consent mechanisms to ensure ongoing compliance with privacy regulations.
  8. Consider performance monitoring and optimization to improve loading times and user experience.

Contact details published on the site

Addresses
Technical notes

Notes

The website is built on WordPress 6.8.1 running on an Apache server with DNS hosted by easyname.eu. It uses popular plugins such as Yoast SEO for search engine optimization and Cookiebot for cookie consent management. The front-end includes modern JavaScript libraries like GSAP for animations and Swiper for sliders, enhancing interactivity and visual appeal. jQuery 3.7.1 is also loaded. The site is mobile responsive and includes accessibility features such as skip links and screen reader text. Structured data in JSON-LD format is implemented for SEO benefits. However, the absence of HTTPS and modern TLS protocols is a significant technical risk. Performance data is missing, but the use of caching (W3 Total Cache) is indicated in the footer comments, suggesting some optimization efforts. Overall, the technical infrastructure is modern but requires urgent security upgrades.
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 lebenshilfe.at. 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 lebenshilfe.at.

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.