Skip to main content

Security report for pax-bkc.de

Pax-Bank für Kirche und Caritas eG · Finance · Germany

Medium risk. 3 critical or high findings in GDPR outside view and SSL/TLS.

Security score

71/100

Risk levelMedium

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

Pax-Bank für Kirche und Caritas eG is a specialized financial institution serving church and charitable organizations in Germany. The website reflects a professional banking service tailored to the non-profit sector, emphasizing trust and sector-specific financial solutions. The market position is niche, focusing on clients within the church and social sectors. Technically, the website employs modern frameworks such as Angular and integrates analytics tools like eTracker and Dynatrace Ruxit for performance monitoring and user tracking. The site is mobile-optimized with good SEO and accessibility basics, though some improvements are possible. Security posture is solid with HTTPS enforced and no visible vulnerabilities, but lacks explicit security policies and headers. Privacy compliance is partial, with cookie consent mechanisms present but no clear privacy or terms of service pages. Overall, the domain registration and hosting align well with the business identity, supporting legitimacy and trustworthiness.

Scanned

NIS2 and GDPR posture

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

3 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. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching pax-bkc.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. 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
77
Security headers
85
Email security
55
DNS health
65
Network security
100
GDPR outside view
43
Average
71

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 bank operates in the finance sector with a focus on church and charitable organizations, positioning itself as a trusted partner for non-profit financial services. Its business model revolves around providing tailored banking products to a specialized clientele, likely generating revenue through traditional banking fees and services. The website's content and structure suggest a medium-sized enterprise with consistent branding and a clear target audience. The use of multiple nameservers under a known hosting provider indicates a stable infrastructure. No direct partnerships or subsidiaries were identified from the data. The company maintains a professional online presence but could enhance transparency by publishing more detailed policies and contact information.

Security posture

The website demonstrates a good security baseline with HTTPS enabled and no exposed sensitive data in the HTML. The use of monitoring scripts like Dynatrace Ruxit indicates active performance and security monitoring. However, the absence of security headers such as Content-Security-Policy and lack of published security policies or incident response contacts are gaps that reduce the overall security maturity. No vulnerabilities or outdated libraries were detected in the provided content. The site lacks a vulnerability disclosure policy or security.txt file, which are recommended best practices. Incident response readiness and communication channels are not publicly available, which could hinder timely reporting and resolution of security incidents.

Recommendations

  1. Publish a comprehensive privacy policy and terms of service to improve compliance and user trust.
  2. Implement and configure security headers like Content-Security-Policy, X-Frame-Options, and X-XSS-Protection.
  3. Add a security policy page and provide incident response contact information (e.g., security@ or abuse@ email).
  4. Introduce a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  5. Enhance accessibility features to meet higher standards and improve user experience for all visitors.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Pax-Bank für Kirche und Caritas eG
Description
Pax-Bank für Kirche und Caritas eG is a bank serving church and charitable organizations, offering financial services tailored to these sectors.
Key services
banking services, financial products for church and charity organizations
Content quality
good
Branding
consistent

Technology

Stack
Angular (indicated by cdk and mat- prefixes), eTracker analytics, Ruxit agent (Dynatrace), Material Design Components, CSS3, JavaScript
Frameworks
Angular
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of security-focused scripts (ruxitagentjs)

Analytics and tracking

Services
eTracker, Dynatrace Ruxit
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
eTracker
Marketing tools
eTracker, Dynatrace Ruxit agent
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 professional and targeted to church and charitable banking clients.
  3. No explicit privacy or terms of service pages found in the provided HTML.
  4. Cookie consent mechanism appears present but no explicit cookie policy page detected.
  5. Use of modern web technologies and analytics tools.
  6. No contact emails or phone numbers explicitly found in the provided HTML snippet.
  7. No security.txt or vulnerability disclosure information found.
  8. WHOIS data supports legitimacy and consistent domain registration.
Technical notes

Notes

The website is built using Angular framework with Material Design components, indicating a modern and maintainable front-end architecture. It uses proprietary or custom CMS components for content rendering. Performance is moderate, with preloading of CSS assets and module preloading for scripts. Analytics integration includes eTracker and Dynatrace Ruxit, providing user behavior insights and performance monitoring. Hosting is managed via atruvia.de nameservers, suggesting a professional hosting environment. The site is mobile-optimized and SEO-friendly with proper meta tags and Open Graph data. Technical risks are minimal but could be reduced further by implementing security headers and improving privacy disclosures.
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 pax-bkc.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 pax-bkc.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.