Skip to main content

Security report for bitmi.de

Bundesverband IT-Mittelstand e.V. · Technology · Germany

Medium risk. 6 critical or high findings in GDPR outside view and Security headers.

Security score

61/100

Risk levelMedium

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

The Bundesverband IT-Mittelstand e.V. (BITMi) is a prominent German industry association representing over 2,500 medium-sized IT companies, positioning itself as the largest specialized association for the IT Mittelstand in Germany. The organization focuses on promoting digital sovereignty, quality standards such as 'Software Made in Germany', and political advocacy for its members. The website reflects a mature digital presence with comprehensive content including news, events, projects, and membership information, supported by a professional WordPress infrastructure and modern web technologies. Security posture is solid with HTTPS enabled, valid SPF and DMARC records, and no critical vulnerabilities detected, although there is room for improvement in security headers and SSL configuration. Privacy compliance is well addressed with a detailed privacy policy, cookie consent mechanism, and use of privacy-respecting analytics (Matomo). Overall, the site demonstrates a high level of professionalism, trustworthiness, and business credibility, serving its target audience effectively.

Scanned

This is an earlier scan of bitmi.de. View the latest report

NIS2 and GDPR posture

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

6 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

    • 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

  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 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';…

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

Keep watching bitmi.de

This scan found 26 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
77
Security headers
15
Email security
75
DNS health
80
Network security
100
GDPR outside view
18
Average
61

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

BITMi operates as a key player in the German IT sector, focusing on the medium-sized business segment. Its business model revolves around advocacy, certification, networking, and knowledge dissemination. The association leverages partnerships with quality seal initiatives and digital sovereignty projects to enhance its market position. The presence of multiple certifications and a strong event calendar indicates active engagement with its community. The organization’s digital strategy includes social media outreach across major platforms and privacy-conscious analytics, reflecting a balance between marketing and compliance. The lack of direct phone contacts on the website suggests a preference for digital communication channels. The association’s growth and influence are supported by its comprehensive service offerings and strategic partnerships.

Security posture

The website employs HTTPS with modern TLS protocols (TLS 1.3 and 1.2) and maintains valid SPF and DMARC DNS records, enhancing email security and domain reputation. No known SSL vulnerabilities such as Heartbleed or FREAK are present. However, the absence of HSTS and OCSP stapling reduces the robustness of the SSL configuration. Security headers beyond basic HTTP headers are not detected, indicating potential for enhancement. The site uses secure forms and cookie consent mechanisms, aligning with GDPR requirements. No exposed sensitive data or vulnerable libraries were identified in the analysis. Overall, the security posture is good but could benefit from implementing additional HTTP security headers and improving SSL practices to reach an excellent level.

Recommendations

  1. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload to enforce HTTPS usage and prevent protocol downgrade attacks.
  2. Implement OCSP stapling to improve SSL certificate revocation checking performance and reliability.
  3. Configure and deploy additional security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web vulnerabilities.
  4. Publish a security.txt file to provide a clear vulnerability disclosure policy and contact information for security researchers.
  5. Review and explicitly configure TLS cipher suites to ensure only strong ciphers are supported, enhancing cryptographic security.
Technical notes

Notes

The website is built on WordPress 6.7.2 with PHP 8.3.22 running on an nginx server, indicating a modern and supported technology stack. It uses popular plugins such as Yoast SEO for search engine optimization, WPBakery Page Builder for content layout, Events Manager for event handling, and Borlabs Cookie for GDPR-compliant cookie management. The site integrates Matomo analytics for privacy-respecting visitor tracking. Performance metrics indicate moderate loading speed with room for optimization. The site is mobile optimized with responsive design elements. Accessibility features are basic but present. The technical infrastructure is solid, leveraging standard web technologies and plugins, but could improve in performance optimization and advanced accessibility compliance.
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. 75/100Medium22 findings · partial scanView report
Reviews of this site

Share your experience with bitmi.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 bitmi.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.