Skip to main content

Security report for kirchengemeinde-ingersheim.de

Evangelische Kirchengemeinde Ingersheim · Non-profit · Germany

Medium risk. 7 critical or high findings in Email security, Security headers and 2 other checks.

Security score

60/100

Risk levelMedium

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

Evangelische Kirchengemeinde Ingersheim operates as a small non-profit Protestant church community in Germany, affiliated with the Evangelische Landeskirche in Württemberg. The website serves as an informational and community engagement platform, offering details on church services, events, youth and adult education, and pastoral care. It targets local community members and churchgoers, providing a trusted source for religious and community activities. Technically, the site is built on TYPO3 CMS, employs Matomo analytics configured for privacy, and includes accessibility features enhancing user experience. The site is mobile-optimized and well-structured, reflecting good digital maturity for a small non-profit entity. Security posture is solid with HTTPS enforced and privacy compliance evident through consent management, though improvements are recommended in security headers and incident response transparency. Overall, the website is professional, trustworthy, and compliant with GDPR, supporting the church's mission effectively.

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

7 findings rated critical or high. Fix these first.

  1. 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

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

  3. 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

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

Keep watching kirchengemeinde-ingersheim.de

This scan found 27 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
42
Security headers
20
Email security
60
DNS health
60
Network security
100
GDPR outside view
80
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

The church community maintains a clear market position as a local religious institution within the Evangelische Landeskirche network. Its business model focuses on non-profit community service, spiritual guidance, and educational programs. The website supports engagement through event registration and news dissemination, leveraging partnerships with the regional church authority (elk-wue.de) and event management via AmosWEB. The absence of commercial advertising or affiliate programs aligns with its non-profit status. Growth indicators include active event listings and community news feeds. The partnership ecosystem is primarily ecclesiastical and regional, emphasizing trust and community service over commercial expansion.

Security posture

The website demonstrates a moderate to good security maturity level. HTTPS is properly implemented, and privacy is respected through a comprehensive consent management system. The use of Matomo analytics with disabled cookies reflects a privacy-conscious approach. However, the absence of explicit security headers such as Content-Security-Policy and X-Frame-Options represents a potential area for improvement. No vulnerabilities or exposed sensitive data were detected in the HTML content. Incident response and security policy information are not publicly available, which could hinder rapid response to security incidents. Overall, the site maintains a secure environment appropriate for its non-commercial nature but would benefit from enhanced security transparency and technical hardening.

Recommendations

  1. Implement standard security headers (Content-Security-Policy, X-Frame-Options, X-Content-Type-Options) to improve protection against common web attacks.
  2. Publish a clear security policy and incident response contact information to enhance transparency and preparedness.
  3. Add explicit email contact information for general and security-related inquiries to improve communication channels.
  4. Regularly audit third-party integrations such as AmosWEB iframe to ensure they do not introduce vulnerabilities.
  5. Continue to monitor and update privacy and cookie consent mechanisms to maintain GDPR compliance.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Evangelische Kirchengemeinde Ingersheim
Description
Evangelische Kirchengemeinde Ingersheim is a Protestant church community belonging to the Evangelische Landeskirche in Württemberg. The website provides information about church services, community life, events, youth work, adult education, pastoral care, and related church activities.
Key services
Church services (Gottesdienste), Community information and news, Event calendar and registration, Youth and children programs, Pastoral care and counseling, Adult education
Content quality
good
Branding
consistent

Technology

Stack
TYPO3 CMS, Matomo Analytics, JavaScript, CSS, HTML5
Frameworks
TYPO3 CMS
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Consent management for cookies
  • No exposed sensitive data in HTML
  • Use of Matomo with disabled cookies

Analytics and tracking

Services
Matomo
Tracking level
minimal
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 well-structured church community site using TYPO3 CMS.
  2. Comprehensive privacy and cookie consent mechanisms are implemented.
  3. No terms of service or explicit security policy pages found.
  4. Contact information is limited to phone and postal address; no email explicitly provided.
  5. Use of Matomo analytics with privacy-conscious configuration (disabled cookies).
  6. Good accessibility features including keyboard shortcuts and color adjustment options.
  7. No signs of security headers in HTML content; recommend adding for enhanced security.
  8. No visible forms collecting personal data except embedded event iframe from AmosWEB.
  9. No social media links detected in the provided content.
  10. No advertising or affiliate marketing detected.
Technical notes

Notes

The website is built on TYPO3 CMS, a mature and widely used content management system, indicating a stable and maintainable infrastructure. The use of Matomo analytics configured to disable cookies shows attention to privacy. The site loads multiple CSS and JavaScript assets, including accessibility scripts and UI enhancements, contributing to a good user experience. Mobile optimization and accessibility features such as keyboard shortcuts and color adjustments are well implemented. Performance appears moderate, with no explicit indicators of slow loading but room for optimization. The site lacks visible security headers, which is a technical debt that should be addressed. Hosting provider details are not explicitly available from the content. Overall, the technical stack is appropriate for a small non-profit organization, balancing functionality and privacy.
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 kirchengemeinde-ingersheim.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 kirchengemeinde-ingersheim.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.