Skip to main content

Security report for stalbert.org

St. Albert the Great Catholic Community · Non-profit · United States

High risk. 8 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

49/100

Risk levelHigh

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

St. Albert the Great Catholic Community is a well-established non-profit religious organization based in Louisville, Kentucky, founded in 1959. The website serves as a digital hub for parishioners and the local community, offering information on worship services, sacramental preparation, lifelong education, pastoral care, and social concerns. The site also facilitates online giving and promotes parish events, reflecting a community-focused business model. Technically, the website is built on the Wix platform, leveraging modern JavaScript frameworks such as React and integrating various Wix apps for video, events, and music. While the site is functional and professionally designed, mobile optimization and accessibility are basic and could be enhanced. Security posture is adequate with HTTPS and some security hardening scripts, but lacks explicit security headers and incident response information. Privacy compliance is weak due to the absence of privacy and cookie policies. Overall, the site is trustworthy and serves its community well but would benefit from improved privacy and security transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
10/ 100 · Critical
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

8 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

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

  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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

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

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

Keep watching stalbert.org

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. 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
0
Security headers
35
Email security
75
DNS health
75
Network security
100
GDPR outside view
10
Average
49

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 as a small-sized non-profit religious entity with a clear focus on serving the Catholic community in Louisville. Its market position is local and community-centric, with key services including religious worship, education, pastoral care, and social outreach. The business model relies on donations and community engagement, supported by online giving and event promotion. The website's integration with social media and external services like Google Calendar and payment processors indicates a moderate digital maturity. The presence of a dedicated store domain suggests additional revenue streams through merchandise. The organization maintains consistent branding and provides clear contact information, enhancing credibility and trust within its target audience.

Security posture

The website employs HTTPS, ensuring encrypted communications, and includes scripts that harden fetch and XMLHttpRequest operations, indicating attention to security best practices. However, the absence of explicit security headers such as Content-Security-Policy and X-Frame-Options reduces the overall security posture. No vulnerabilities or exposed sensitive data were detected in the analyzed content. The lack of a published security policy or incident response contact channels limits transparency and preparedness for security incidents. The site uses third-party scripts from Wix and integrates with external services, which should be regularly audited to mitigate supply chain risks. Overall, the security posture is moderate but could be significantly improved with additional policies and headers.

Recommendations

  1. Publish comprehensive privacy and cookie policies with clear GDPR compliance statements and implement a cookie consent mechanism.
  2. Add security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  3. Provide explicit security policy and incident response contact information to improve transparency and readiness.
  4. Enhance mobile optimization and accessibility to improve user experience across devices and for users with disabilities.
  5. Regularly audit and update third-party scripts and dependencies to mitigate potential vulnerabilities and supply chain risks.

Contact details published on the site

Addresses
Legal name
St. Albert the Great Catholic Community
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
St. Albert the Great Catholic Community
Description
Founded in 1959, St. Albert the Great is a Christ-centered community of Disciples dedicated to inspiring people to love, serve and know God and one another. Our parish works to offer a dynamic, Christ-centered community that thrives on our shared Roman Catholic faith.
Key services
Religious services and worship, Sacramental preparation, Lifelong education and formation, Pastoral care, Social concerns and community welfare, Online giving and donations, Parish events and communications
Content quality
good
Branding
consistent

Technology

Stack
Wix.com Website Builder, JavaScript, React (18.3.1), Lodash, Wix Video Widget, Wix Events & Tickets, Wix Music, Google Event Calendar integration
Frameworks
Wix Thunderbolt, Wix Editor Elements
Platforms
Wix Hosting
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Use of security override globals to harden fetch and XHR
  • Cookie handling with restricted access to sensitive cookies

Analytics and tracking

Services
Wix BI, Sentry error monitoring
Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is built on Wix platform with standard Wix technologies
  2. No explicit privacy, cookie, or terms of service policies found on main pages
  3. Contact information is clearly presented including phone, email, physical address, and contact form
  4. Social media presence is active and linked
  5. Security best practices partially implemented but could be improved with headers and policies
  6. No signs of blocking or WAF interference
  7. Content is relevant and professionally presented for a religious community
  8. Mobile optimization is basic but functional
  9. No advertising or tracking beyond Wix BI and Sentry error monitoring
Technical notes

Notes

The website is built on the Wix platform using modern web technologies including React 18 and Lodash. It integrates multiple Wix apps such as Wix Video, Wix Events & Tickets, and Wix Music, along with external services like Google Calendar and Podbean. The site uses AVIF image encoding for optimized media delivery. Performance is moderate with some optimizations in place, but mobile responsiveness is basic. Accessibility features are minimal but present. The site lacks advanced SEO optimizations but includes basic meta tags and structured data for local business. Technical debt appears low due to the managed Wix environment, but reliance on multiple third-party widgets requires ongoing maintenance to ensure stability and security.
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 stalbert.org. 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 stalbert.org.

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.