Skip to main content

Security report for rpa-kirche.de

Rechnungsprüfungsamt der evangelisch-lutherischen Landeskirche Hannovers · Government · Germany

Medium risk. 7 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

The Rechnungsprüfungsamt der evangelisch-lutherischen Landeskirche Hannovers is a specialized public institution responsible for financial auditing and control within the Evangelical Lutheran Church of Hanover. The website serves as an informational portal for church districts, congregations, and affiliated institutions, providing insights into their auditing activities, news, and career opportunities. The organization holds a stable market position within the government and non-profit sectors, focusing on transparency and accountability in church finances. Technically, the website employs modern web technologies including HTML5, CSS3, JavaScript, and Matomo analytics, hosted on a CDN for performance. Security posture is solid with HTTPS and CSRF protections, though improvements in security headers and cookie consent mechanisms are recommended. Overall, the site is professional, trustworthy, and well-structured, supporting the organization's mission effectively.

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

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. 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 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 rpa-kirche.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. See sample alerts.

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
55
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 organization operates within the government and non-profit sectors, providing essential auditing services to church entities. Its business model is non-commercial, focusing on regulatory compliance and financial oversight. The website targets church officials, auditors, and stakeholders interested in church financial governance. The presence of career pages indicates ongoing recruitment and organizational growth. Partnerships with related church and event domains suggest a collaborative ecosystem. The site’s content and structure reflect a mature digital presence with consistent branding and clear communication of services.

Security posture

The website demonstrates a good security baseline with enforced HTTPS, CSRF tokens in forms, and no visible exposure of sensitive data. However, the absence of key security headers such as Content-Security-Policy and X-Frame-Options reduces defense-in-depth. No vulnerability disclosure or incident response information is provided, which could hinder transparency in case of security events. The use of Matomo with disabled cookies shows a privacy-aware approach to analytics. Overall, the security posture is good but could be enhanced by adopting additional headers and publishing security policies.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  2. Introduce a cookie consent banner or mechanism to comply fully with GDPR and inform users about tracking practices.
  3. Publish a clear security policy and incident response contact information to improve transparency and readiness.
  4. Add a vulnerability disclosure policy or security.txt file to encourage responsible reporting of security issues.
  5. Consider adding direct contact information such as official emails and phone numbers on the website to improve user trust and accessibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Rechnungsprüfungsamt der evangelisch-lutherischen Landeskirche Hannovers
Description
Das Rechnungsprüfungsamt ist zuständig für die Prüfung der Kirchenkreise und Kirchengemeinden der Evangelisch-lutherischen Landeskirche Hannovers sowie deren Einrichtungen. Es bietet öffentliche Finanzkontrolle und Rechnungsprüfung im kirchlichen Bereich.
Key services
Finanzprüfung, Rechnungsprüfung, Beratung kirchlicher Einrichtungen
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, jQuery, Slick Slider, Matomo Analytics
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • CSRF tokens present in forms
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Matomo
Tracking level
minimal
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 focused on church financial auditing and related services.
  3. No explicit privacy or cookie consent banners found, though privacy policy page exists.
  4. No direct emails or phone numbers found in the HTML content; contact is via contact form and footer links.
  5. Use of Matomo analytics with disabled cookies indicates privacy-conscious tracking.
  6. No security.txt or vulnerability disclosure policy found.
  7. Website uses HTTPS and CSRF tokens for form security.
  8. No social media links explicitly found in the provided HTML.
  9. Website is professionally designed with consistent branding and good navigation.
Technical notes

Notes

The website uses a modern and stable technology stack with HTML5, CSS3, JavaScript, and jQuery-based components like Slick Slider. It leverages a CDN for asset delivery, improving load times and availability. Matomo analytics is integrated with cookie usage disabled, reflecting privacy-conscious design. The site is mobile-optimized with responsive design elements and basic accessibility features. SEO is supported by appropriate meta tags and structured content. However, the CMS is not explicitly identified, suggesting a custom or proprietary solution. Performance is moderate, with potential for optimization in asset loading and caching strategies.
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 rpa-kirche.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 rpa-kirche.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.