Security report for steinach-rodach-main.de
Katholisches Pfarramt Schwürbitz · Government · Germany
Medium risk. 7 critical or high findings in GDPR outside view, Email security and 2 other checks.
The website steinach-rodach-main.de serves as the official online presence of the Catholic parish Schwürbitz, located in the Lichtenfels-Obermain pastoral area in Germany. It provides parishioners and visitors with comprehensive information about church services, community events, staff, and sacraments. The site targets local community members and those interested in parish activities, operating as a non-profit religious community service platform. The content is well-organized, professionally presented, and primarily in German, reflecting its local audience focus. Technically, the website employs a modern technology stack including Bootstrap for responsive design, jQuery, Font Awesome, and specialized plugins like FancyBox and Revolution Slider for enhanced user experience. It uses FlexiWeb CMS inferred from AJAX glossary features and is hosted on servers associated with internet1.de. The site is mobile-optimized, accessible, and SEO-friendly, with moderate performance characteristics. From a security perspective, the site enforces HTTPS, uses Google reCAPTCHA for bot protection, and implements a cookie consent mechanism compliant with GDPR. Matomo analytics is used with anonymous tracking fallback to respect user privacy. However, some security headers like Content-Security-Policy and X-Frame-Options are not explicitly detected and could be improved. No vulnerabilities or exposed sensitive data were found in the analyzed content. Overall, the website demonstrates a solid security posture and good privacy compliance, with clear contact information and trust indicators such as official email addresses and imprint pages. The domain registration details align with the website content, indicating legitimacy and trustworthiness. Strategic recommendations include enhancing security headers, ensuring CSRF protection on forms, and publishing a dedicated security policy to further strengthen trust and compliance.
Scanned
NIS2 and GDPR posture
- GDPR outside view
- 28/ 100 · High
- Checks completed
- 7of 7
NIS2 Art. 21(2)
- (a) Risk analysis and security policies: Not visible from outside
- (b) Incident handling: One indicator
- (c) Business continuity, backups and crisis management: Not visible from outside
- (d) Supply chain security: Not visible from outside
- (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
- (f) Assessing the effectiveness of security measures: Not visible from outside
- (g) Cyber hygiene and security training: Not visible from outside
- (h) Cryptography and encryption: Partly checked
- (i) HR security, access control and asset management: One indicator
- (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.
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
- GDPR Art. 7
- ePrivacy Art. 5(3)
- NIST PT-4: NIST SP 800-53 Rev. 5 PT-4: Consent
- Critical
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
- Critical
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 X-Frame-Options header
Prevents clickjacking attacks
What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"
- CWE-1021
- OWASP A06:2025
- CAPEC-103
- ASVS V3.4.6
- OWASP Secure Headers: OWASP Secure Headers Project recommends X-Frame-Options: deny
- RFC 7034
- 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';…
- High
Need hands-on remediation? Email guard@offseq.com
Keep watching steinach-rodach-main.de
This scan found 29 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
- 62
- Security headers
- 30
- Email security
- 60
- DNS health
- 60
- Network security
- 100
- GDPR outside view
- 28
- Average
- 57
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
Security posture
Recommendations
- Implement and enforce security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web attacks.
- Publish a clear security policy and incident response contact information to improve transparency and readiness.
- Ensure all forms include CSRF tokens and validate inputs to prevent injection attacks.
- Regularly update third-party libraries and plugins to their latest secure versions.
- Enhance cookie consent mechanisms with detailed data retention policies and user rights information.
Contact details published on the site
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- Company
- Katholisches Pfarramt Schwürbitz
- Description
- Website of the Catholic parish Schwürbitz in the Lichtenfels-Obermain pastoral area, providing information about church services, staff, events, and community life.
- Key services
- Information on church services, Community news and events, Contact to parish office and staff, Information on sacraments and parish life
- Content quality
- good
- Branding
- consistent
Technology
- Stack
- jQuery, Bootstrap CSS, Font Awesome, FancyBox, Flexslider, Revolution Slider, Cube Portfolio, JW Player, Google reCAPTCHA, Matomo Analytics
- Frameworks
- Bootstrap
- Performance
- moderate
- Mobile
- good
- Accessibility
- good
- SEO
- good
Security
- Observed score
- 80/100
- Good practices seen
- HTTPS enforced
- Cookie consent with opt-in/out
- Use of Google reCAPTCHA for bot protection
- Matomo analytics with anonymous tracking fallback
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
- Website is a parish community site for Schwürbitz, Germany.
- Content is in German and well-structured with clear navigation.
- Cookie consent is implemented with granular options and detailed explanations.
- Uses Matomo analytics with anonymous tracking fallback.
- No signs of malicious or suspicious content.
- No visible security policy or incident response contact.
- WHOIS data is minimal but consistent with hosting provider.
- No social media links detected in the provided content.
- Contact information is clearly presented with email, phone, and physical address.
- Site uses multiple modern JS libraries and CSS frameworks for UI.
Technical notes
Notes
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.
- MITRE CWE (opens in a new tab)4.20 (2026-04-30) · CWE Terms of Use (free use with attribution, © MITRE)
- OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
- MITRE CAPEC (opens in a new tab)3.9 (2023-01-24) · CAPEC Terms of Use (free use with attribution, © MITRE)
- OWASP ASVS (opens in a new tab)5.0.0 · CC BY-SA 4.0
- OWASP Web Security Testing Guide (opens in a new tab)latest (checklist.json, master) · CC BY-SA 4.0
- OWASP Secure Headers Project (opens in a new tab)2026-10-18 · Apache-2.0
- Mozilla Server Side TLS (intermediate) (opens in a new tab)6.0 · MPL-2.0
- NIST SP 800-53 Rev. 5 (OSCAL catalog) (opens in a new tab)5.2.0 · Public domain (US Government work)
- Directive (EU) 2022/2555 (NIS2) (opens in a new tab)OJ L 333, 27.12.2022 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Commission Implementing Regulation (EU) 2024/2690 (opens in a new tab)OJ L, 18.10.2024 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Regulation (EU) 2016/679 (GDPR) (opens in a new tab)OJ L 119, 4.5.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive 2002/58/EC (ePrivacy), consolidated (opens in a new tab)19.12.2009 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- RFC Editor metadata (opens in a new tab)per-RFC (obsolete RFCs rejected) · IETF Trust Legal Provisions (metadata only)
- NIST CSRC, W3C TR, IETF Datatracker, EDPB, EUR-Lex CELLAR and gesetze-bayern.de (opens in a new tab)per document · Titles and links only
- NIST NVD CVE API 2.0 (opens in a new tab)live records · Public domain (NVD); CVE® records © MITRE, free use
- W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
- ETSI EN 301 549 (opens in a new tab)V3.2.1 (2021-03), clause headings · Clause numbers and titles only (© ETSI)
- Directive (EU) 2019/882 (European Accessibility Act) (opens in a new tab)OJ L 151, 7.6.2019 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive (EU) 2016/2102 (Web Accessibility Directive) (opens in a new tab)OJ L 327, 2.12.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Retrieved 2026-10-25
Feedback on this report
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with steinach-rodach-main.de. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review steinach-rodach-main.de.