Skip to main content

Security report for kimusearch.de

Landeskirche Hannovers · Government · Germany

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

Security score

63/100

Risk levelMedium

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

KiMuSearch is a specialized online platform operated under the Evangelische Landeskirche Hannovers, designed to connect church musicians with congregations seeking musical services for worship and events. The platform facilitates registrations for both musicians and congregations, enabling posting and responding to service requests within a regional context. The website is professionally designed with a clear focus on its niche audience, providing essential features such as secure login and event listings. Technically, the site is built on Ruby on Rails with Bootstrap and Font Awesome for UI, and uses Matomo for analytics, indicating a moderate level of digital maturity. Security measures include HTTPS enforcement and CSRF protection, though some security headers and cookie consent mechanisms are missing. Overall, the site demonstrates a solid security posture appropriate for its scope, with room for improvement in privacy compliance and incident response transparency.

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

6 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. 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 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 kimusearch.de

This scan found 26 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
72
Security headers
60
Email security
60
DNS health
60
Network security
100
GDPR outside view
28
Average
63

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 platform serves a niche market within the religious and non-profit sector, specifically targeting church musicians and congregations in the Hannover region of Germany. Its business model revolves around matchmaking and event coordination, providing value by simplifying the process of finding and booking musicians for church services. The association with the Evangelische Landeskirche Hannovers lends credibility and trust, positioning KiMuSearch as a trusted regional service. The website's content and structure support user engagement through registration and inquiry listings, though direct contact details are limited to forms and dedicated pages. The use of Matomo analytics suggests an interest in user behavior insights while maintaining some privacy considerations. The platform's growth potential is tied to the regional church community and could benefit from enhanced marketing and expanded features.

Security posture

KiMuSearch exhibits a good security baseline with HTTPS, CSRF tokens, and secure form handling. However, the absence of explicit security headers such as Content-Security-Policy and X-Frame-Options represents an area for enhancement. The lack of a published incident response or vulnerability disclosure policy limits transparency and preparedness for security events. Privacy compliance is partial; while a privacy policy exists and GDPR compliance is indicated, the missing cookie consent mechanism is a compliance gap given the use of tracking analytics. No vulnerabilities or exposed sensitive data were detected in the HTML content. Overall, the security posture is adequate for a small non-profit platform but would benefit from formalized policies and improved header configurations.

Recommendations

  1. Implement a visible cookie consent banner and detailed cookie policy to ensure full GDPR compliance.
  2. Add security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options to enhance protection against common web attacks.
  3. Publish an incident response plan and provide a dedicated security contact or abuse email to improve transparency and readiness.
  4. Consider creating a vulnerability disclosure policy or security.txt file to encourage responsible reporting of security issues.
  5. Regularly audit third-party libraries and dependencies to ensure no vulnerable components are in use.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Landeskirche Hannovers
Description
KiMuSearch is a platform that connects church musicians and congregations within the Evangelische Landeskirche Hannovers. Registered congregations can post requests for musicians, and registered musicians can offer their services within a chosen radius of their residence.
Key services
Posting musician requests by congregations, Musician registration and profile matching, Event and service scheduling
Content quality
good
Branding
consistent

Technology

Stack
Ruby on Rails, Bootstrap, Font Awesome, Matomo Analytics
Frameworks
Ruby on Rails
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • CSRF tokens in forms
  • Secure login form with password input
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Matomo
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Matomo
Marketing tools
Matomo Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is in German and targeted at church musicians and congregations in Hannover region.
  3. No direct contact emails or phone numbers found on the homepage; contact is via form and dedicated contact page.
  4. No cookie consent banner or explicit cookie policy found despite use of Matomo analytics.
  5. Security best practices like HTTPS and CSRF tokens are implemented.
  6. No explicit security or incident response policies published.
  7. WHOIS data is minimal but not privacy protected; domain legitimacy is supported by website content and branding.
Technical notes

Notes

The website is built on a Ruby on Rails framework with Bootstrap for responsive design and Font Awesome for icons, indicating a modern and maintainable tech stack. The use of Matomo analytics reflects a preference for privacy-conscious tracking. The site loads with moderate performance and is mobile-optimized, though accessibility features appear basic. SEO optimization is present but could be improved with additional meta tags and structured data. Hosting details are not explicit, but the use of generic routing name servers suggests a standard hosting environment. No critical technical debt or risks were identified, but enhancements in security headers and privacy mechanisms would strengthen the technical posture.
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 kimusearch.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 kimusearch.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.