Skip to main content

Security report for pfarrei-burgkunstadt.de

Pfarrei St. Heinrich und Kunigunde Burgkunstadt · Non-profit · 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

Pfarrei St. Heinrich und Kunigunde Burgkunstadt is a local parish church serving the community in Burgkunstadt, Germany. The website provides comprehensive information about religious services, sacraments, community news, and events, targeting local parishioners and visitors. It is part of the Erzbistum Bamberg diocese network and collaborates with nearby parishes. The site is well-structured, accessible, and includes GDPR-compliant privacy and cookie policies. Contact information is clearly presented, supporting community engagement. Technically, the website is built on the Alkacon Mercury CMS platform, using modern web technologies including JavaScript, Bootstrap, and Matomo analytics for privacy-conscious tracking. The site is mobile-optimized and includes accessibility features such as the eyeAble plugin. Hosting is provided by internet1.de, with DNS configured accordingly. Performance is moderate, with good SEO and accessibility practices. From a security perspective, the site uses HTTPS (assumed from canonical URLs and external scripts), employs cookie consent mechanisms, and avoids exposing sensitive data. However, explicit security headers are not visible in the provided data, and no incident response or security policy pages are found. The site does not show signs of vulnerabilities or malicious content. The WHOIS data indicates a consistent and legitimate domain registration appropriate for a local parish. Overall, the website demonstrates a solid digital presence for a small non-profit religious organization, balancing user experience, privacy, and accessibility. Strategic improvements could include enhancing security headers, publishing a security policy, and formalizing incident response contacts to strengthen trust and compliance.

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

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

  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';…
  4. 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 pfarrei-burgkunstadt.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. 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
52
Security headers
60
Email security
60
DNS health
60
Network security
100
GDPR outside view
43
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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention pfarrei-burgkunstadt.de, from OffSeq Breach.

No leaked records found

Breach holds no records for pfarrei-burgkunstadt.de right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The parish operates as a non-profit religious entity focused on community engagement through sacraments, events, and pastoral care. Its market position is local within the Erzbistum Bamberg diocese, collaborating with neighboring parishes. The business model centers on serving parishioners and the local community rather than commercial revenue. The website supports this by providing detailed information on services, contact points, and community news. The partnership ecosystem includes related parish websites and diocesan resources, indicating a collaborative network. Growth indicators are limited due to the nature of the organization, but the recent website update and accessibility focus suggest ongoing digital maturity efforts.

Security posture

The website exhibits a moderate security posture with HTTPS usage and cookie consent mechanisms in place. The absence of visible security headers and incident response information suggests room for improvement. No vulnerabilities or exposed sensitive data were detected in the HTML content. The use of Matomo analytics aligns with privacy-conscious practices. The site lacks explicit security policies or contact channels for security incidents, which could impact incident response readiness. Overall, the security culture appears basic but adequate for a small non-profit, with recommendations to enhance header configurations and formalize security documentation.

Recommendations

  1. Implement comprehensive HTTP security headers including Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, and X-Content-Type-Options.
  2. Publish a dedicated security policy page and provide clear incident response contact information.
  3. Regularly audit and update third-party scripts and libraries to mitigate vulnerabilities.
  4. Enhance SSL/TLS configuration to ensure strong encryption and forward secrecy.
  5. Maintain and improve accessibility and privacy compliance to reinforce trust with users.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Pfarrei St. Heinrich und Kunigunde Burgkunstadt
Description
Kirchliche Gemeinde Pfarrei St. Heinrich und Kunigunde Burgkunstadt offering religious services, sacraments, community news, and events.
Key services
Community news and events, Pastoral care and contact, Information about churches and groups
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, Matomo Analytics, OpenStreetMap, Alkacon Mercury CMS modules, Bootstrap (collapse, responsive classes), FontAwesome icons
Frameworks
Alkacon Mercury CMS
Performance
moderate
Mobile
good
Accessibility
excellent
SEO
good

Security

Observed score
70/100
Good practices seen
  • Cookie consent banner with opt-in for external content
  • No exposed sensitive data in HTML
  • No visible vulnerable libraries

Analytics and tracking

Services
Matomo
Tracking level
minimal
Privacy practices
good

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. Strong focus on accessibility with eyeAble plugin integration.
  3. Comprehensive cookie consent mechanism with granular options.
  4. No explicit terms of service found.
  5. Contact information is clearly presented and structured.
  6. Use of Matomo analytics indicates privacy-conscious tracking.
  7. External links mostly to related church and diocese sites.
  8. No signs of suspicious or malicious content.
  9. Content is in German and targeted at local parish community.
  10. No security headers data available; recommend audit.
Technical notes

Notes

The website is built on the Alkacon Mercury CMS platform, leveraging JavaScript, Bootstrap, and FontAwesome for UI and interactivity. It integrates Matomo for analytics, emphasizing privacy. The site is mobile-responsive and includes advanced accessibility features via the eyeAble plugin. Hosting is managed by internet1.de, with DNS configured accordingly. Performance is moderate, with room for optimization. The site uses external resources from the Erzbistum Bamberg CDN and integrates OpenStreetMap via MapTiler for location services. The technical stack is modern and appropriate for the organization's needs, though security header implementation and performance tuning could be enhanced.
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 pfarrei-burgkunstadt.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 pfarrei-burgkunstadt.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.