Skip to main content

Security report for hanau.de

Stadt Hanau · Government · Germany

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

Security score

65/100

Risk levelMedium

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

The website www.hanau.de is the official digital presence of the city of Hanau, Germany, serving as a comprehensive municipal portal. It provides residents, visitors, and businesses with access to a wide range of city services, political information, cultural events, environmental initiatives, and citizen engagement programs. The site targets a broad audience including local citizens, tourists, and stakeholders interested in the city's offerings. The business model is that of a government entity providing public information and services, positioning itself as the authoritative source for Hanau-related municipal content. Technically, the website is built on the IMPERIA CMS platform, leveraging modern web technologies such as Bootstrap and FontAwesome for UI/UX. It employs Matomo analytics with pseudonymized IP tracking, demonstrating a commitment to privacy. The site is mobile-optimized and includes accessibility features, with a cookie consent mechanism compliant with GDPR requirements. Hosting appears professional with multiple authoritative nameservers. From a security perspective, the site uses HTTPS and implements cookie consent controls. However, explicit security policies, incident response contacts, and vulnerability disclosure mechanisms are not evident. No critical vulnerabilities or exposed sensitive data were detected in the analyzed content. The WHOIS data aligns with the website's governmental nature, showing consistent registration and no privacy protection, which is appropriate for a public entity. Overall, the website presents a trustworthy, well-maintained, and privacy-conscious digital platform for the city of Hanau. Strategic improvements could include publishing a dedicated security policy, incident response information, and a vulnerability disclosure page to enhance transparency and security posture.

Scanned

NIS2 and GDPR posture

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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  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 hanau.de

This scan found 24 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
65
Email security
70
DNS health
60
Network security
100
GDPR outside view
28
Average
65

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

Total records
86
Employees
0
Customers
75
Third parties
11
Weak passwords
26%

9 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 hanau.de.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Hanau.de operates as the official municipal website for the city of Hanau, providing extensive information and services across multiple sectors including government administration, culture, environment, education, and citizen engagement. The site supports digital transformation initiatives such as online applications and digital citizen services. Its market position is that of a trusted government portal with a medium-sized audience primarily composed of local residents and regional visitors. The business model is non-commercial, focused on public service delivery. Partnerships with local organizations and external service providers are evident through linked domains. The site demonstrates growth in digital maturity with integrated analytics and accessibility features, supporting strategic goals of transparency and citizen participation.

Security posture

The security posture of hanau.de is solid with HTTPS enforced and a cookie consent mechanism that respects user privacy and GDPR compliance. The use of Matomo analytics with pseudonymized IP addresses further supports privacy protection. No security headers were explicitly detected in the provided content, and no direct incident response or security contact information is published, which represents an area for improvement. There is no evidence of exposed sensitive data or vulnerable libraries in the HTML content. The absence of a security.txt or vulnerability disclosure page limits transparency for security researchers. Overall, the site maintains good baseline security practices appropriate for a government website but could enhance its security maturity by formalizing policies and contact channels.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and commitments.
  2. Provide clear incident response contact information, such as a security@ or abuse@ email address.
  3. Implement and advertise a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  4. Add standard security headers like Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Enhance visibility and accessibility of contact information including phone numbers and physical addresses for official communication.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Stadt Hanau
Description
Official website of the city of Hanau, Germany, providing information about city services, politics, culture, events, environment, and citizen engagement.
Key services
Online applications and services, City news and announcements, Event calendars, Information on city politics and administration, Tourism and cultural information, Environmental programs and initiatives
Content quality
good
Branding
consistent

Technology

Stack
IMPERIA CMS 10.5.1, FontAwesome 6 Pro, Matomo (self-hosted analytics), Bootstrap (implied by classes and modal usage), jQuery (implied by modal and event handlers), Green Audio Player (podcast player)
Frameworks
Bootstrap
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 pseudonymized analytics

Analytics and tracking

Services
Matomo
Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
Matomo
Marketing tools
Matomo
Transparency
good

Site quality

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

Key observations

  1. Website is a comprehensive municipal portal for the city of Hanau, Germany.
  2. Content is in German and well-structured with extensive navigation menus.
  3. Cookie consent and privacy policy are implemented with GDPR compliance.
  4. No visible security policy or incident response contact information.
  5. No exposed sensitive data or obvious vulnerabilities detected in HTML content.
  6. Use of Matomo analytics with pseudonymized IPs indicates privacy-conscious tracking.
  7. Social media presence includes LinkedIn, Instagram, YouTube, Facebook, and Twitter.
  8. No terms of service page explicitly found.
  9. No security.txt or vulnerability disclosure page detected.
  10. No direct contact emails or phone numbers found in the provided HTML snippet.
Technical notes

Notes

The website is powered by IMPERIA CMS version 10.5.1, a specialized content management system for government and public sector websites. Frontend technologies include Bootstrap for responsive design and FontAwesome 6 Pro for iconography. The site uses a custom podcast player (Green Audio Player) and includes accessibility features such as adjustable contrast and font size controls. Analytics are handled via a self-hosted Matomo instance, configured for privacy compliance. The site is mobile-optimized and demonstrates good SEO practices with appropriate meta tags. Hosting is managed through multiple aspiria.de nameservers, indicating professional infrastructure. Performance is moderate, with no critical technical debt observed. Opportunities exist to improve security headers and formalize security-related documentation.
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

Earlier scans of this domain

  1. 65/100Medium33 findingsView report
Reviews of this site

Share your experience with hanau.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 hanau.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.