Skip to main content

Security report for gemeinsam-gegen-sexismus.de

Bündnis "Gemeinsam gegen Sexismus" · Government · Germany

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

50/100

Risk levelMedium

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

The website 'Bündnis Gemeinsam gegen Sexismus' represents a German government-supported non-profit alliance focused on combating sexism and sexual harassment across various sectors. It provides educational resources, advocacy, and a platform for organizations to join the cause. The site is professionally designed, mobile-optimized, and uses modern web technologies including WordPress and Yoast SEO. It integrates privacy-compliant cookie consent mechanisms and minimal user tracking via Plausible Analytics. Security posture is strong with HTTPS and security headers in place, though explicit security policies and incident response contacts are not published. Overall, the domain registration and website content align well, indicating a legitimate and trustworthy initiative.

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

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

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

Keep watching gemeinsam-gegen-sexismus.de

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
65
DNS health
70
Network security
20
GDPR outside view
68
Average
50

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 alliance targets organizations and the public in Germany, leveraging governmental funding and partnerships to establish a credible position in social advocacy. Its business model is non-profit, focusing on awareness, education, and prevention of sexism. The website features testimonials from influential figures, enhancing trust and outreach. The initiative's growth potential is supported by its governmental backing and comprehensive resource offerings. No direct revenue streams are evident, consistent with its non-profit nature.

Security posture

The website demonstrates a mature security posture with enforced HTTPS, use of security headers, and no visible vulnerabilities or exposed sensitive data. Cookie consent is implemented via Borlabs Cookie, supporting GDPR compliance. However, the absence of a published security policy or incident response information limits transparency in security governance. No vulnerability disclosure or security.txt file is present, which could be improved to enhance security culture and responsiveness.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and commitments.
  2. Provide clear incident response contact channels to improve transparency and trust.
  3. Implement and publish a vulnerability disclosure policy or security.txt file.
  4. Consider listing a data protection officer contact to strengthen GDPR compliance.
  5. Regularly review and update third-party scripts and plugins to mitigate potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Bündnis "Gemeinsam gegen Sexismus"
Description
Branchenübergreifendes Bündnis zur Erkennung, Sichtbarmachung und Bekämpfung von Sexismus und sexueller Belästigung, gefördert vom Bundesministerium für Bildung, Familie, Senioren, Frauen und Jugend (BMBFSFJ) und durchgeführt von EAF Berlin.
Key services
Aufklärung und Wissensvermittlung, Bereitstellung von Materialien und Handreichungen, Vernetzung von Bündnispartnern, Förderung wirksamer Maßnahmen gegen Sexismus
Content quality
excellent
Branding
consistent

Technology

Stack
WordPress 6.8.3, Yoast SEO plugin, Borlabs Cookie plugin, Plausible Analytics, SVG graphics, JavaScript for UI enhancements
Platforms
WordPress
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism implemented
  • No exposed sensitive data in HTML
  • Use of security headers

Analytics and tracking

Services
Plausible Analytics
Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
Plausible Analytics
Marketing tools
Yoast SEO
Transparency
good

Site quality

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

Key observations

  1. Website is a professionally maintained non-profit initiative.
  2. Content is comprehensive and well-structured in German language.
  3. Strong governmental support and partnerships.
  4. Good privacy and cookie compliance with consent mechanisms.
  5. No signs of malicious or suspicious activity.
  6. Use of modern web technologies and SEO best practices.
  7. No direct contact emails or phone numbers publicly listed; contact via form.
  8. No explicit security or incident response policies published.
Technical notes

Notes

The website is built on WordPress 6.8.3 with Yoast SEO and Borlabs Cookie plugins, hosted on 1&1 IONOS infrastructure. It uses SVG graphics and JavaScript for UI enhancements including contrast mode toggling and parallax effects. Performance is moderate with good mobile optimization and accessibility features. SEO is well addressed with meta tags, Open Graph, and JSON-LD structured data. The technical stack is modern and well maintained, though continuous monitoring for plugin updates and security patches is recommended to avoid technical debt.
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

Earlier scans of this domain

  1. 52/100Medium35 findingsView report
Reviews of this site

Share your experience with gemeinsam-gegen-sexismus.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 gemeinsam-gegen-sexismus.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.