Skip to main content

Security report for bkk-akzo.de

BKK Akzo Nobel Bayern · Healthcare · Germany

High risk. 5 critical or high findings in Network security, Security headers and 1 other check.

Security score

49/100

Risk levelHigh

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

BKK Akzo Nobel Bayern is a regional health insurance provider in Germany offering comprehensive health insurance services with a focus on personal service and digital convenience. Their website is built on TYPO3 CMS and provides a user-friendly experience with clear navigation and professional design. The company emphasizes GDPR compliance with a comprehensive privacy policy and a robust cookie consent mechanism powered by Cookiebot. Analytics are handled via Matomo with user consent enforcement, reflecting a mature approach to privacy and data protection. Security posture is good with HTTPS enforced and no critical vulnerabilities detected, though some security headers could be improved. Overall, the website reflects a trustworthy and professional organization with a solid digital presence.

Scanned

NIS2 and GDPR posture

GDPR outside view
83/ 100 · Low
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

5 findings rated critical or high. Fix these first.

  1. 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
    • Critical

      Critical Service Exposed: PostgreSQL

      Port 5432 (PostgreSQL) is publicly accessible - PostgreSQL - Database server

      What to do: Immediately restrict access to PostgreSQL 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
    • High

      High-Risk Service Exposed: FTP

      Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer

      What to do: Consider restricting access to FTP or implementing strong authentication

      • 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

  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 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. 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 bkk-akzo.de

This scan found 21 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
82
Security headers
65
Email security
80
DNS health
70
Network security
0
GDPR outside view
83
Average
63
After the cap
49

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 bkk-akzo.de, from OffSeq Breach.

Total records
21
Employees
0
Customers
21
Third parties
0
Weak passwords
10%

2 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 bkk-akzo.de.

Select it in the checkout above.

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

The company operates in the healthcare sector as a statutory health insurance fund targeting individuals in Bavaria, Germany. Their business model centers on providing health insurance memberships with additional exclusive benefits and digital health services. The website content and structure indicate a medium-sized organization with consistent branding and a focus on customer service. The use of modern CMS and consent management tools suggests a commitment to digital maturity and regulatory compliance. No direct contact emails or phone numbers were found, indicating a preference for contact via web forms. The domain registration data aligns well with the business claims, supporting legitimacy.

Security posture

The website demonstrates a good security posture with HTTPS enabled and consent-based analytics tracking. The use of Cookiebot ensures GDPR-compliant cookie management. However, explicit security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options were not detected in the HTML, representing an area for improvement. No exposed sensitive data or vulnerable libraries were found. The absence of a published security policy or incident response contact limits transparency in security governance. Overall, the site is secure but could enhance its security maturity by adopting additional headers and publishing security policies.

Recommendations

  1. Implement and enforce security headers like Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  2. Publish a clear security policy and provide incident response contact information to improve transparency and readiness.
  3. Add a security.txt file to facilitate responsible vulnerability disclosure.
  4. Regularly audit third-party scripts and libraries to ensure no vulnerabilities are introduced.
  5. Enhance contact information visibility by including verified company emails and phone numbers for customer and security inquiries.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
BKK Akzo Nobel Bayern
Description
BKK Akzo Nobel Bayern is a health insurance company offering above-average services at attractive prices, with personal service and many online services. They provide membership applications online and exclusive additional benefits.
Key services
Health insurance membership, Online membership application, Exclusive additional health services, Digital health applications, Chronic disease management, Prevention and care services
Content quality
good
Branding
consistent

Technology

Stack
TYPO3 CMS, Matomo Analytics, Cookiebot Consent Management
Frameworks
TYPO3 CMS
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Cookie consent with opt-in/out
  • No exposed sensitive data in HTML
  • Use of consent-based analytics tracking

Analytics and tracking

Services
Matomo
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Matomo
Marketing tools
Cookiebot
Transparency
good

Site quality

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

Key observations

  1. Website uses TYPO3 CMS with modern consent management via Cookiebot.
  2. Matomo analytics is integrated with user consent enforcement.
  3. No direct email or phone contact found in the provided HTML; contact is via form.
  4. Cookie consent dialog is comprehensive and GDPR compliant.
  5. No explicit terms of service page detected.
  6. No security.txt or explicit security policy found.
  7. Website content is professional, relevant, and well-structured.
  8. No signs of adult or unsafe content.
  9. No WAF or blocking mechanisms detected.
Technical notes

Notes

The website is built on TYPO3 CMS, a robust and widely used content management system, indicating a stable technical foundation. It integrates Matomo analytics with consent enforcement via Cookiebot, reflecting good privacy practices. The site is mobile optimized and accessible, with good SEO meta tags and Open Graph data for social sharing. Performance is moderate, with compressed CSS and JS assets. Hosting provider details are not explicitly found. The site uses standard favicon and manifest files for branding consistency. No major technical debt or outdated technologies were detected, but security headers could be improved to modern standards.
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 bkk-akzo.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 bkk-akzo.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.