Skip to main content

Security report for oberhausen.de

Stadt Oberhausen · Government · Germany

Medium risk. 3 critical or high findings in Security headers, SSL/TLS and 1 other check.

Security score

74/100

Risk levelMedium

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

The website www.oberhausen.de serves as the official digital portal for the city of Oberhausen, Germany, providing residents and visitors with comprehensive information on city life, public services, tourism, and cultural events. The site is well-structured with clear navigation and a focus on accessibility and user experience. It employs modern web technologies including Matomo for analytics and Cookiebot for GDPR-compliant cookie consent management, reflecting a mature digital infrastructure. Security posture is adequate with HTTPS enforced and privacy-conscious analytics, though explicit security policies and contact information for incident response are not evident in the provided content. Overall, the site demonstrates a professional and trustworthy presence consistent with a municipal government entity.

Scanned

NIS2 and GDPR posture

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

3 findings rated critical or high. Fix these first.

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

  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.

    • 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

  3. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • High

      Weak SPF Policy

      SPF record has permissive policy allowing any server to send email

      What to do: Use -all or ~all qualifier for better email security

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

Keep watching oberhausen.de

This scan found 20 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. See sample alerts.

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
50
Email security
85
DNS health
55
Network security
100
GDPR outside view
88
Average
74

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

Oberhausen's municipal website positions itself as a key information hub for local governance and community engagement. Its business model is service-oriented, focusing on providing transparent access to administrative resources, cultural information, and citizen services. The site leverages partnerships with service portals and trusted third-party providers like Cookiebot and Matomo to enhance functionality and compliance. The absence of commercial advertising and the presence of government branding reinforce its public sector identity. Growth indicators include the integration of accessibility tools such as ReadSpeaker and a comprehensive cookie consent mechanism, signaling responsiveness to regulatory and user needs.

Security posture

The website exhibits a moderate security maturity level with HTTPS enabled and the use of a reputable cookie consent management system. However, the lack of visible security headers and absence of published security policies or incident response contacts suggest areas for improvement. No vulnerabilities or exposed sensitive data were detected in the analyzed content. Compliance with GDPR is supported by Cookiebot's consent mechanism, but the missing privacy policy and terms of service documents represent compliance gaps. The site would benefit from enhanced transparency around security practices and formal incident response procedures to strengthen trust and readiness.

Recommendations

  1. Publish a comprehensive privacy policy and terms of service documents prominently on the website.
  2. Implement and disclose a formal security policy including incident response contacts.
  3. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Regularly audit and update third-party scripts to mitigate potential vulnerabilities.
  5. Enhance contact information availability including official emails and phone numbers for public inquiries and security incidents.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Stadt Oberhausen
Description
Official website of the city of Oberhausen providing information about city life, services, culture, tourism, and administration.
Key services
City information, Tourism, Public services, Citizen engagement, Event information
Content quality
good
Branding
consistent

Technology

Stack
Matomo Analytics, Cookiebot Consent Management, jQuery (implied by ajax usage), Elasticsearch (search functionality), Shadowbox.js, ReadSpeaker (text-to-speech), Modernizr
Performance
moderate
Mobile
good
Accessibility
good
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • Cookie consent with blocking mode
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Matomo
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Google
Tracking pixels
Matomo
Marketing tools
Cookiebot
Transparency
basic

Site quality

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

Key observations

  1. Website is a municipal government portal for Oberhausen, Germany.
  2. Cookie consent is managed by Cookiebot with a detailed consent dialog.
  3. Matomo analytics is used, indicating privacy-conscious tracking.
  4. No explicit privacy policy or terms of service found in the provided content.
  5. No direct contact emails or phone numbers found in the HTML snippet.
  6. Website uses HTTPS and modern JavaScript libraries.
  7. No WAF or blocking mechanisms detected.
  8. Content is in German and targeted at general public including residents and visitors.
  9. No adult or questionable content detected.
  10. Navigation is hierarchical and detailed with multiple submenus.
Technical notes

Notes

The website is built on a modern technology stack featuring Matomo analytics, Cookiebot for consent management, Elasticsearch for search functionality, and accessibility tools like ReadSpeaker. The use of esy CMS is inferred from asset paths. Performance is moderate with asynchronous script loading and responsive design elements. The site demonstrates good mobile optimization and accessibility compliance. However, SEO optimization appears basic with minimal meta descriptions and keywords. Technical debt is low but could be reduced further by consolidating scripts and improving metadata. Hosting details are not explicit but the domain uses standard name servers without privacy protection, indicating transparency.
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 oberhausen.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 oberhausen.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.