Skip to main content

Security report for bowas.com

Bowas-Induplan Chemie Ges.m.b.h. · Manufacturing · Austria

High risk. 8 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

48/100

Risk levelHigh

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

Bowas-Induplan Chemie Ges.m.b.h. is a mature, internationally active plant engineering company specializing in chemical plants for the energetic materials industry. With over 200 projects completed globally and a subsidiary in India, the company demonstrates a solid market presence and expertise in environmentally responsible industrial solutions. The website is professionally designed using Contao CMS and includes modern features such as cookie consent management via Cookiebot. However, the absence of HTTPS and a valid SSL certificate significantly undermines the site's security posture, exposing visitors to potential risks. Additionally, the domain is at high expiry risk with no domain protection locks, which could threaten business continuity if not addressed promptly. Privacy compliance is basic, with a privacy policy linked but no explicit GDPR compliance statements or data protection officer contact. Overall, the site presents a credible business but requires urgent security improvements.

Scanned

NIS2 and GDPR posture

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

8 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

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

  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 bowas.com

This scan found 16 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
65
Email security
50
DNS health
55
Network security
100
GDPR outside view
15
Average
48

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 company operates in the manufacturing sector, focusing on chemical plant engineering for industrial and military applications. Its business model centers on engineering, installation, and commissioning of specialized plants, including dismantlement and environmental remediation. The firm targets industrial clients worldwide, leveraging a strong project portfolio and a subsidiary in India to expand market reach. The website content is consistent with the company's stated expertise and geographic footprint. The lack of visible direct contact details may limit immediate customer engagement but is mitigated by a contact form. The company appears well-positioned but should enhance digital trust signals and security to maintain competitive advantage.

Security posture

The website's security posture is weak due to the lack of HTTPS, no TLS support, and missing advanced security headers like HSTS. DNSSEC is not enabled, and domain protection is absent, increasing risk of domain hijacking or expiry-related outages. While some security headers are present, the overall configuration is insufficient for modern security standards. No incident response or vulnerability disclosure policies are found, indicating limited readiness for security incidents. The use of Cookiebot shows awareness of privacy regulations but is not complemented by comprehensive GDPR compliance measures. Immediate remediation of SSL/TLS and domain security is critical to reduce risk.

Recommendations

  1. Implement a valid SSL/TLS certificate and enable HTTPS site-wide immediately.
  2. Enable HSTS with includeSubDomains and preload to enforce secure connections.
  3. Activate DNSSEC and domain protection locks to safeguard domain integrity.
  4. Renew domain registration well before expiry to avoid service disruption.
  5. Publish clear security and incident response policies including vulnerability disclosure.
  6. Enhance privacy compliance with explicit GDPR statements and appoint a data protection officer.
  7. Add visible company contact emails and phone numbers to improve trust and customer engagement.

Contact details published on the site

Addresses
Legal name
Bowas-Induplan Chemie Ges.m.b.h.
Technical notes

Notes

The website runs on Apache 2.4.62 with Contao CMS and uses jQuery and Cookiebot scripts. The site is moderately optimized for mobile and SEO with proper meta tags and structured navigation. However, performance metrics are missing or zero, indicating possible measurement gaps or slow loading. The absence of HTTPS and modern TLS protocols is a major technical deficiency. The hosting provider is not explicitly identified but the IP address suggests a European hosting environment. The site uses Typekit fonts and multiple JavaScript libraries for UI enhancements. Overall, the technical infrastructure is functional but outdated in security and performance aspects, requiring modernization to meet current 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 bowas.com. 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 bowas.com.

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.