Skip to main content

Security report for dunningen.de

Gemeinde Dunningen · Government · Germany

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

Security score

56/100

Risk levelMedium

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

Gemeinde Dunningen operates as the official municipal government website for the town of Dunningen, Germany, serving approximately 6,330 residents across three districts. The website provides comprehensive local information including news, events, public announcements, and municipal services. It targets local citizens and visitors, offering online services and community engagement resources. The business model is focused on public service and community information dissemination, positioning itself as a trusted local government authority. Technically, the website is built on the cEasy CMS platform, leveraging JavaScript libraries such as jQuery and Swiper.js for UI components, and Matomo for privacy-conscious analytics. The site is hosted with domaincontrol.com DNS services and employs HTTPS with a good SSL configuration. The site demonstrates good mobile optimization, accessibility, and SEO practices, though there is room for improvement in security headers and explicit security policy documentation. From a security perspective, the site enforces HTTPS and includes a cookie consent mechanism compliant with GDPR. No critical vulnerabilities or exposed sensitive data were detected. However, the absence of security headers and incident response contact information suggests opportunities to enhance the security posture. The WHOIS data is consistent and legitimate, supporting the trustworthiness of the domain. Overall, the website presents a professional, secure, and privacy-conscious platform for municipal services. Strategic recommendations include implementing security headers, publishing security policies, and providing incident response contacts to further strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

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

5 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 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 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';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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

  3. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • High

      High-Risk Service Exposed: FTP

      Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer

      What to do: Consider restricting access to FTP or implementing strong authentication

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

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

Keep watching dunningen.de

This scan found 23 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
90
Security headers
15
Email security
70
DNS health
60
Network security
20
GDPR outside view
80
Average
56

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

No leaked records found

Breach holds no records for dunningen.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

The website serves as the digital presence of the local government of Dunningen, providing essential services and information to residents and visitors. Its market position is that of a small municipal authority with a focus on community engagement and transparency. The business model is non-commercial, centered on public service delivery. Key services include event calendars, public announcements, online citizen services, and local business directories. The site leverages partnerships with local service providers and uses a specialized CMS (cEasy) tailored for municipal websites. Growth indicators include active news updates and event listings. The partnership ecosystem includes the CMS provider hitcom and local community organizations. The website's operations reflect a stable, community-focused approach with moderate digital maturity.

Security posture

The website demonstrates a moderate to good security maturity level. HTTPS is enforced with a strong SSL configuration, and a cookie consent banner ensures GDPR compliance. The use of Matomo analytics reflects a privacy-conscious approach. However, the absence of key security headers such as Content Security Policy (CSP), HSTS, and X-Frame-Options reduces the overall security posture. No incident response or vulnerability disclosure information is provided, which could hinder timely handling of security issues. No exposed sensitive data or vulnerable libraries were detected. The security culture appears cautious but could benefit from formalized policies and enhanced technical controls.

Recommendations

  1. Implement HTTP security headers including CSP, HSTS, and X-Frame-Options to mitigate common web vulnerabilities.
  2. Publish a dedicated security policy and incident response contact information to improve transparency and readiness.
  3. Regularly audit and update third-party scripts and libraries to prevent vulnerabilities.
  4. Enhance cookie consent mechanism with detailed information on data retention and third-party data sharing.
  5. Consider adding a security.txt file or vulnerability disclosure page to facilitate responsible reporting.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Gemeinde Dunningen
Description
Die Gemeinde Dunningen mit rund 6.330 Einwohnern und seinen drei Ortsteilen Dunningen, Seedorf und Lackendorf liegt am östlichen Rand des mittleren Schwarzwaldes, am Übergang vom Schwarzwald zum Oberen Gäu inmitten des Landkreises Rottweil.
Key services
Public announcements, Event information, Municipal services, Online citizen services, Community information
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, jQuery, Matomo Analytics, Swiper.js, cEasy CMS
Frameworks
cEasy CMS
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner with opt-in/out
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Matomo
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Matomo
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 site for Dunningen, Germany.
  2. Content is comprehensive and well-structured with clear navigation.
  3. Cookie consent and privacy policy are implemented and accessible.
  4. No signs of security blocking or WAF interference.
  5. Use of Matomo analytics indicates privacy-conscious tracking.
  6. No visible security headers detected; opportunity for improvement.
  7. No contact form detected on the main page; contact info provided in footer.
  8. No terms of service or explicit security policy pages found.
  9. No vulnerability disclosure or security.txt file found.
Technical notes

Notes

The website is built on the cEasy CMS platform version 5.3.5, utilizing JavaScript libraries such as jQuery and Swiper.js for interactive elements. It uses Matomo for analytics, indicating a preference for privacy-friendly tracking. The site loads multiple CSS and JS bundles asynchronously, improving performance. Hosting is managed via domaincontrol.com DNS services. The site is mobile-optimized with responsive design and accessibility features like skip links and ARIA roles. SEO is supported by meta tags, canonical links, and structured JSON-LD breadcrumb data. Performance is moderate with some preloading of critical CSS. Technical risks include lack of security headers and potential reliance on third-party scripts without explicit versioning or integrity checks.
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 dunningen.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 dunningen.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.