Skip to main content

Security report for buechen.de

Gemeinde Büchen · Government · Germany

High risk. 8 critical or high findings in GDPR outside view, Email security and 2 other checks.

Security score

46/100

Risk levelHigh

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

Gemeinde Büchen operates as a local government entity serving approximately 6,700 residents in the Herzogtum Lauenburg district of Germany. The website provides comprehensive information about municipal services, including family and social services, education, culture, economy, and local infrastructure. It targets residents, families, businesses, and visitors, positioning itself as a community hub with a focus on quality of life and connectivity. Technically, the site is built on TYPO3 CMS with Bootstrap and jQuery, but suffers from slow load times and lacks modern security configurations such as HTTPS. The security posture is weak due to the absence of SSL/TLS encryption, security headers, and DNS security features. Privacy compliance is partially addressed with a cookie consent mechanism and a privacy policy, but no terms of service or incident response policies are evident. Overall, the site is functional and informative but requires urgent security improvements to protect user data and enhance trust.

Scanned

NIS2 and GDPR posture

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

      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

  2. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

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

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

Keep watching buechen.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
90
Security headers
15
Email security
60
DNS health
75
Network security
20
GDPR outside view
18
Average
46

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 website reflects a government-operated municipal portal focused on providing essential information and services to its community. Its market position is local and essential, with a business model centered on public service rather than commercial revenue. The site supports community engagement through news, events, and cultural activities. The partnership ecosystem includes related municipal domains such as amt-buechen.eu. Growth indicators are not explicit, but the presence of digital services like online search and event calendars suggests ongoing digital maturity. Competitive advantages include comprehensive local content and integration of mobility and economic development information.

Security posture

The current security maturity level is low, primarily due to the lack of HTTPS and absence of security headers. This exposes users to risks such as data interception and man-in-the-middle attacks. The absence of DMARC, DNSSEC, and CAA records further weakens domain security. No incident response or vulnerability disclosure mechanisms are in place, indicating limited readiness for security incidents. The cookie consent implementation is a positive aspect for GDPR compliance, but overall data protection practices need enhancement. The security culture appears minimal, with no visible certifications or security policies.

Recommendations

  1. Implement a valid SSL/TLS certificate to enable HTTPS across the entire site immediately.
  2. Configure and deploy essential security headers including Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.
  3. Set up DNS security features such as DMARC, DNSSEC, and CAA records to protect domain integrity.
  4. Develop and publish a clear security policy and incident response plan accessible to users.
  5. Enhance cookie consent mechanisms to fully comply with GDPR and provide transparent data usage information.

Contact details published on the site

Addresses
Technical notes

Notes

The website uses a mature CMS platform (TYPO3) with a standard set of front-end libraries including Bootstrap and jQuery. While the design is responsive and content-rich, the site suffers from slow load times (over 8 seconds) and a large page size (~530 KB). The hosting provider is identified as DomainControl, with DNS managed via GoDaddy nameservers. No modern TLS protocols are supported, and no SSL certificate is installed, which is a critical technical deficiency. The site includes multiple JavaScript libraries and custom scripts for UI enhancements and cookie management. SEO is supported with meta tags and canonical links, but accessibility features are basic. There is room for modernization and performance optimization.
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. 53/100Medium33 findingsView report
Reviews of this site

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