Skip to main content

Security report for gesundsozial.digital

Other · N/a

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

Security score

63/100

Risk levelMedium

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

The website gesundsozial.digital appears to be a German language platform related to digital health and social services. The content is basic and targeted at German-speaking users interested in these sectors. The site uses modern frontend technologies such as Vue.js, Nuxt.js, TailwindCSS, and Leaflet.js for mapping features, indicating a moderate level of technical maturity. However, the lack of visible contact information, privacy policy, and terms of service pages limits the business credibility and user trust. Security posture is minimal with no detected security headers or explicit security policies, and no WHOIS registrant data is publicly available, suggesting privacy protection but reducing transparency. Overall, the site is functional and professionally designed but requires improvements in compliance and security transparency.

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. 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. 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 gesundsozial.digital

This scan found 27 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
62
Security headers
15
Email security
70
DNS health
80
Network security
100
GDPR outside view
53
Average
63

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 business behind gesundsozial.digital is not explicitly identified in the content or WHOIS data. The site targets the health and social digital services sector in Germany, likely serving a niche or specialized audience. The absence of detailed business information, contact details, or certifications limits insights into market positioning or revenue models. The use of modern web frameworks suggests a focus on user experience and digital presence. No partnerships or related domains were identified. The business appears to be small scale or early stage based on available data.

Security posture

Security maturity is low to moderate. The site uses HTTPS (inferred from URL), but no security headers were detected in the provided data. There is no visible privacy policy or incident response contact information, which are critical for GDPR compliance and user trust. No vulnerable libraries or exposed sensitive data were identified, but the absence of security best practices and policies is a concern. The WHOIS data is privacy protected, which is common but reduces transparency. Overall, the site should enhance its security posture by implementing security headers, publishing privacy and security policies, and providing clear contact channels for security incidents.

Recommendations

  1. Implement and publish a comprehensive privacy policy and terms of service to improve compliance and user trust.
  2. Add explicit contact information including business emails and phone numbers to enhance credibility.
  3. Configure and enforce security headers such as Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, and X-Content-Type-Options.
  4. Establish an incident response contact channel (e.g., security@ or abuse@ email) and publish it on the site.
  5. Regularly audit and update all dependencies and frameworks to mitigate vulnerabilities and improve performance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Website appears to be related to digital health and social services in German language, but no explicit business description found in the provided content.
Content quality
basic
Branding
moderate

Technology

Stack
TailwindCSS, Leaflet.js, Vue.js (inferred from .vue files in CSS comments), Nuxt.js (inferred from _nuxt paths)
Frameworks
Nuxt.js, Vue.js
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
40/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
good
User experience
good
Content relevance
basic
Navigation
basic
Professionalism
basic
Trustworthiness
moderate

Key observations

  1. WHOIS data unavailable publicly, indicating privacy protection
  2. No explicit contact emails or phone numbers found in content
  3. Cookie consent mechanism present and functional
  4. No privacy policy or terms of service pages detected in provided content
  5. Website uses modern frontend technologies (Vue/Nuxt, TailwindCSS, Leaflet)
  6. No external analytics or advertising scripts detected in provided content
  7. Content is in German language focused on health and social digital topics
  8. No security headers or explicit security policies found
  9. No forms detected in provided HTML snippet
  10. No social media links or business contact info found
Technical notes

Notes

The website is built using modern frontend technologies including Vue.js and Nuxt.js frameworks, styled with TailwindCSS, and incorporates Leaflet.js for interactive maps. The site appears mobile optimized with responsive design. Performance is moderate with no explicit indicators of slow loading. Accessibility features are basic but present. SEO optimization is minimal with basic meta tags but no structured data or Open Graph tags detected in the provided content. Hosting provider and CMS are not identifiable from the data. The technical stack is modern but could benefit from enhanced SEO and accessibility improvements.
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 gesundsozial.digital. 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 gesundsozial.digital.

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.