Skip to main content

Security report for boernsen-erleben.de

Gemeinde Börnsen · Government · Germany

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

Security score

60/100

Risk levelMedium

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

The website boernsen-erleben.de serves as an official community and municipal information portal for the small German municipality of Börnsen. It provides residents and visitors with local news, events, business listings, and community resources, positioning itself as a key digital touchpoint for local engagement. The site is built on the ProcessWire CMS platform, leveraging jQuery and Matomo analytics for user tracking and interaction. However, the technical infrastructure lacks modern security measures, notably the absence of HTTPS, which critically undermines user trust and data protection. The site’s content is well-organized and relevant, with clear navigation and consistent branding, but mobile optimization and accessibility are only basic. Privacy compliance is limited, with no cookie consent mechanism despite active tracking, and no visible security or incident response policies. Overall, the site functions adequately as a local government information resource but requires urgent security and privacy improvements to meet modern standards.

Scanned

This is an earlier scan of boernsen-erleben.de. View the latest report

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

7 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 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 boernsen-erleben.de

This scan found 22 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
85
Security headers
30
Email security
65
DNS health
85
Network security
75
GDPR outside view
18
Average
60

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

Boernsen-erleben.de operates as a government sector digital platform focused on community engagement and information dissemination. Its business model centers on providing free access to local news, events, and business information to residents and visitors, supporting municipal transparency and participation. The site’s market position is localized with no evident commercial revenue streams. The partnership ecosystem is minimal, with no identified subsidiaries or parent companies. The platform’s growth potential lies in enhancing digital services and expanding mobile accessibility. The use of Matomo analytics indicates an interest in user behavior insights, though privacy practices need strengthening. The site’s competitive advantage is its official status and comprehensive local content, but technical and security modernization is necessary to maintain credibility and user trust.

Security posture

The security posture of boernsen-erleben.de is currently weak. The absence of any SSL/TLS certificate and HTTPS support is a critical vulnerability, exposing users to data interception and undermining trust. Security headers are minimal, with only X-XSS-Protection present, and no advanced headers like Content-Security-Policy or HSTS enabled. The site lacks cookie consent mechanisms despite using Matomo analytics, raising GDPR compliance concerns. No incident response or security policy information is publicly available, indicating limited preparedness for security incidents. While no active vulnerabilities such as Heartbleed or POODLE were detected, the overall security configuration is insufficient for protecting user data and ensuring compliance with modern standards. Immediate remediation is required to implement HTTPS, enhance header security, and establish privacy and incident response policies.

Recommendations

  1. Implement a valid SSL/TLS certificate and enforce HTTPS site-wide to secure data transmission.
  2. Deploy comprehensive security headers including HSTS, Content-Security-Policy, X-Content-Type-Options, and Referrer-Policy.
  3. Introduce a cookie consent mechanism compliant with GDPR to manage user tracking and privacy.
  4. Publish clear security policies and incident response procedures to improve transparency and readiness.
  5. Enhance mobile optimization and accessibility to improve user experience across devices.

Contact details published on the site

Addresses
Technical notes

Notes

The website is hosted on an nginx server with DNS and mail services provided by rzone.de and Strato, indicating a standard hosting environment for small to medium German websites. The CMS used is ProcessWire, a flexible PHP-based content management system, complemented by jQuery for client-side scripting and Matomo for analytics. Despite a modern CMS choice, the lack of HTTPS and modern TLS protocols severely limits security. Performance metrics are missing, suggesting potential monitoring gaps. The site includes structured navigation and meta tags supporting SEO, but accessibility and mobile responsiveness are only basic. The absence of advanced caching or session management features indicates room for technical optimization. Overall, the infrastructure is functional but requires modernization to meet current web standards and security best practices.
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/100Medium28 findingsView report
Reviews of this site

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