Skip to main content

Security report for stadtwerke-badoeynhausen.de

Stadtwerke Bad Oeynhausen (AöR) · Energy · Germany

Medium risk. 5 critical or high findings in GDPR outside view, Security headers and 1 other check.

Security score

63/100

Risk levelMedium

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

Stadtwerke Bad Oeynhausen (AöR) is a municipal utility company fully owned by the city of Bad Oeynhausen, Germany. The company provides essential public services including water supply, wastewater management, waste disposal, city maintenance, and operation of public swimming pools and parking facilities. The website targets local residents and customers, offering information and access to customer services. The business model is typical for a public utility, focusing on local infrastructure and community services with a medium-sized operational scale. Technically, the website is built on a CMS platform tailored for municipal utilities (GIPS), using a combination of jQuery, jQuery UI, and custom JavaScript libraries. The hosting is managed via Ewetel, a German hosting provider. The site shows moderate performance and basic mobile optimization. SEO and accessibility features are present but could be improved. The site includes a comprehensive cookie consent mechanism and privacy policy, demonstrating good GDPR compliance. From a security perspective, the site uses HTTPS and session cookies appropriately. However, it lacks explicit security headers and uses an outdated jQuery version, which could pose risks. No critical vulnerabilities or exposed sensitive data were detected. Incident response and security policy information are not publicly available, which could be improved to enhance trust and preparedness. Overall, the website is professional, trustworthy, and well-aligned with its municipal utility purpose. Strategic improvements in security headers, technology updates, and transparency on security policies would strengthen its security posture and compliance standing.

Scanned

NIS2 and GDPR posture

GDPR outside view
43/ 100 · High
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. 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 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';…
  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 stadtwerke-badoeynhausen.de

This scan found 25 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
67
Security headers
40
Email security
70
DNS health
60
Network security
100
GDPR outside view
43
Average
63

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

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 stadtwerke-badoeynhausen.de, from OffSeq Breach.

No leaked records found

Breach holds no records for stadtwerke-badoeynhausen.de right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

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

Stadtwerke Bad Oeynhausen operates as a local municipal utility, serving the city of Bad Oeynhausen with essential infrastructure services. Its competitive advantage lies in its official status as a city-owned entity, ensuring trust and regulatory compliance. Revenue streams likely come from service fees for water, waste, and other municipal services. The target customers are local residents and businesses. The company maintains partnerships with local government and related municipal entities, as indicated by linked domains. The website content and structure support customer engagement and service delivery. Growth indicators are not explicit but the presence of digital customer services and online forms suggests ongoing modernization efforts.

Security posture

The website demonstrates a moderate security maturity level. HTTPS is enforced, and cookie consent is implemented in compliance with GDPR. However, the use of an outdated jQuery version introduces potential vulnerabilities. The absence of security headers such as Content Security Policy (CSP), HSTS, and X-Frame-Options reduces defense-in-depth. No incident response contacts or security policies are published, limiting transparency. Data protection practices appear adequate for the site's scope, with session cookies and minimal tracking. Overall, the security posture is sufficient for a public information site but could be enhanced to mitigate emerging threats and demonstrate compliance with evolving regulations like NIS2.

Recommendations

  1. Upgrade jQuery and other JavaScript libraries to current secure versions to mitigate known vulnerabilities.
  2. Implement and configure security headers including CSP, HSTS, X-Frame-Options, and X-XSS-Protection to strengthen browser security.
  3. Publish explicit security policy and incident response information to improve transparency and readiness.
  4. Enhance mobile optimization and accessibility to improve user experience and compliance with accessibility standards.
  5. Consider adding a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.

Contact details published on the site

Addresses
Legal name
Stadtwerke Bad Oeynhausen (Anstalt öffentlichen Rechts)
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Stadtwerke Bad Oeynhausen (AöR)
Description
Die Stadtwerke Bad Oeynhausen AöR ist ein 100% -iges Tochterunternehmen der Stadt Bad Oeynhausen.
Key services
Wasserversorgung, Abwasserentsorgung, Abfallentsorgung, Stadtbildpflege, Bäderbetrieb, Parkmöglichkeiten
Content quality
good
Branding
consistent

Technology

Stack
jQuery 1.9.1, jQuery UI 1.11.4, Day.js, Custom JavaScript libraries (HRSysLib), CSS with YAML framework
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced (implied by canonical and og:url https)
  • Cookie consent banner with opt-in/out
  • Session cookies used for session management

Analytics and tracking

Services
GIPS Statistik
Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
GIPS Statistik pixel
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is in German and targeted at local residents and customers.
  3. Comprehensive cookie consent mechanism is implemented.
  4. Contact information is clearly provided including phone, email, and physical address.
  5. No explicit terms of service or security policy pages found.
  6. Technical stack is somewhat dated but functional.
  7. No critical security vulnerabilities detected in the content.
  8. Social media presence on Facebook and Instagram is linked.
  9. WHOIS data supports legitimacy and consistency with business claims.
Technical notes

Notes

The website is built on the GIPS CMS platform specialized for municipal utilities, leveraging jQuery 1.9.1 and jQuery UI 1.11.4, along with Day.js for date handling and custom HRSysLib JavaScript libraries. The CSS uses the YAML framework for layout. Hosting is provided by Ewetel, a German ISP. Performance is moderate with basic mobile responsiveness. SEO is supported by meta tags and Open Graph data but could be improved. The site uses a cookie consent manager script to comply with privacy regulations. Technical debt is indicated by outdated libraries and missing modern security headers. Opportunities exist to modernize the tech stack, improve performance, and enhance security configurations.
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 stadtwerke-badoeynhausen.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 stadtwerke-badoeynhausen.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.