Skip to main content

Security report for bwt.fr

BWT Holding GmbH · Manufacturing · France

High risk. 9 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

45/100

Risk levelHigh

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

BWT Holding GmbH operates a comprehensive website focused on water treatment solutions, targeting private consumers and professional sectors in France. The site offers detailed product and service information, supported by a consistent brand presence and multiple customer contact channels. Technically, the website uses modern JavaScript libraries, Google Tag Manager, and performance optimization tools, hosted behind Cloudflare. However, a critical security weakness is the invalid SSL certificate and lack of TLS protocol support, which significantly undermines the site's security posture. Privacy and cookie policies are present and appear GDPR compliant, with consent mechanisms implemented. Overall, the site is professional and content-rich but requires urgent remediation of its SSL/TLS configuration to ensure secure user interactions.

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

9 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. 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 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 bwt.fr

This scan found 18 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
35
Email security
50
DNS health
85
Network security
100
GDPR outside view
0
Average
45

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

BWT is positioned as a leading European manufacturer and retailer of water treatment products, serving a broad market including residential, commercial, and industrial clients. The business model combines product sales with service offerings such as installation and maintenance. The company leverages a network of partners and service providers, as evidenced by related domains. The website supports multiple languages and regional sites, indicating a mature international presence. Trust indicators include European production claims, certifications, and active customer support. The company appears to invest in digital marketing and analytics, using Google Analytics and Tag Manager to monitor user engagement.

Security posture

The website's security posture is weak due to the absence of a valid SSL certificate and disabled TLS protocols, exposing users to potential interception and man-in-the-middle attacks. While some security headers like X-Frame-Options and HttpOnly cookies are present, the lack of HTTPS is a critical flaw. No explicit security or incident response policies are found on the site, and no vulnerability disclosure or security.txt files are present. The site does not implement HSTS or OCSP stapling, missing opportunities to enhance security. Immediate action is required to obtain and configure a valid SSL certificate and enable modern TLS protocols to protect user data and maintain trust.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable TLS 1.2 or TLS 1.3 protocols and disable insecure protocols.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  4. Enable OCSP stapling to improve certificate revocation checking performance and security.
  5. Review and adjust cookie SameSite attributes to enhance security and compatibility.
  6. Publish a security policy and incident response contact information to improve transparency.
  7. Consider adding a security.txt file to facilitate vulnerability disclosures.
  8. Continue to maintain GDPR compliance and enhance privacy transparency where possible.
Technical notes

Notes

The website is built on a Sitecore CMS platform, using modern JavaScript libraries including Hyphenopoly for text hyphenation and SpeedKit for performance optimization. Google Tag Manager and Google Analytics are integrated for marketing and analytics purposes. Hosting is provided via Cloudflare, offering CDN and security features, although SSL is misconfigured. The site is mobile responsive with good SEO practices including meta tags and Open Graph data. Performance metrics are not provided but the use of SpeedKit suggests optimization efforts. Accessibility is basic but could be improved. Overall, the technical infrastructure is modern but requires critical security fixes to SSL/TLS configuration to ensure safe and trusted user experience.
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 bwt.fr. 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 bwt.fr.

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.