Skip to main content

Security report for blcchurch.org.uk

Brook Lane Community Church · Non-profit · United Kingdom

High risk. 7 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

47/100

Risk levelHigh

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

Brook Lane Community Church is a small non-profit religious organization based in the United Kingdom, with a history dating back to 1928. The church focuses on community outreach, spiritual growth, and providing worship services both in-person and via live streaming. Their website serves as a portal for engagement, learning, sharing testimonies, and connecting with the church community. The organization is registered as a company limited by guarantee and a registered charity, indicating formal legal and charitable status. Technically, the website uses legacy JavaScript libraries such as jQuery 1.11.1 and jQuery UI 1.10.4, along with plugins like Cycle2 for slideshows. Some external resources are loaded over HTTP, which is a security concern. The site appears moderately optimized for mobile and accessibility but lacks advanced SEO and modern frameworks. The contact form collects user data securely via POST but lacks advanced anti-spam protections. From a security perspective, the site lacks visible security headers and uses outdated libraries with known vulnerabilities. The WHOIS data for the domain is unavailable due to a domain naming rules error, which raises concerns about domain registration legitimacy. No cookie consent or comprehensive privacy compliance mechanisms are present, though a basic privacy policy is linked. Social media presence is active across major platforms, enhancing community engagement. Overall, the website is functional and serves its community purpose but requires technical and security improvements. The domain registration issues and outdated technology stack reduce trustworthiness and security posture. Strategic improvements in security headers, HTTPS enforcement, updated libraries, and privacy compliance would enhance the site's reliability and user trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
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. 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 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';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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

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

Keep watching blcchurch.org.uk

This scan found 28 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
47
Security headers
15
Email security
85
DNS health
60
Network security
20
GDPR outside view
53
Average
47

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

Brook Lane Community Church operates as a local non-profit religious entity serving the Christian community in the UK. Its market position is that of a longstanding community church with a focus on outreach and spiritual support. The business model centers on community engagement, worship services, and pastoral care, supported by donations and charitable status. The target audience includes church members, local residents, and online viewers of live-streamed services. The organization maintains an active social media presence to extend its reach. Growth indicators include digital live streaming and online group meetings. Partnerships appear limited to social media platforms and public health/government advisory links. The church's operations are typical for a small non-profit with a focus on community and faith-based services.

Security posture

The website demonstrates a basic security posture with several areas for improvement. The use of outdated JavaScript libraries such as jQuery 1.11.1 introduces known vulnerabilities that could be exploited. External scripts loaded over unsecured HTTP connections increase the risk of man-in-the-middle attacks. No security headers like Content-Security-Policy or X-Frame-Options are detected, which are important for mitigating common web attacks. The contact form uses POST and requires key fields, but lacks visible anti-spam or CAPTCHA protections. The absence of cookie consent and detailed privacy compliance mechanisms indicates potential GDPR compliance gaps. The WHOIS data unavailability due to domain naming errors raises concerns about domain legitimacy and registration transparency. Overall, the security maturity is low to moderate, suitable for a small non-profit but requiring urgent upgrades to protect user data and trust.

Recommendations

  1. Upgrade all JavaScript libraries to their latest secure versions to mitigate known vulnerabilities.
  2. Serve all external resources over HTTPS to prevent interception and ensure data integrity.
  3. Implement essential security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Add a cookie consent mechanism and enhance privacy policy to improve GDPR compliance.
  5. Investigate and resolve domain WHOIS registration issues to improve domain legitimacy and trust.

Contact details published on the site

Legal name
Brook Lane Community Church
Registration number
06486246
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Brook Lane Community Church
Description
Brook Lane Community Church is a non-profit religious organization focused on sharing Christ and doing good through reaching, serving, sharing, and equipping. They offer Sunday services, live streaming, community support, and pastoral care.
Key services
Sunday worship services, Live streaming of services, Community outreach, Pastoral support, Kingdom Groups
Content quality
good
Branding
consistent

Technology

Stack
jQuery 1.11.1, jQuery UI 1.10.4, jQuery Cycle2 plugin, Adobe Edge Web Fonts
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
45/100
Good practices seen
  • Use of HTTPS assumed but not confirmed
  • Contact form uses POST method
  • Form fields have required attributes

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

Design
basic
User experience
basic
Content relevance
good
Navigation
good
Professionalism
basic
Trustworthiness
moderate

Key observations

  1. Website is accessible with full content and no blocking detected
  2. No HTTPS status explicitly confirmed in provided data
  3. Use of outdated JavaScript libraries and HTTP external resources
  4. Contact form collects personal data with required fields
  5. No cookie or tracking consent mechanisms found
  6. Privacy policy present but basic
  7. No terms of service or security policy pages found
  8. Social media presence on Facebook, Twitter, YouTube, Instagram
  9. Physical location embedded via Google Maps
  10. Company registration and charity numbers displayed in footer
Technical notes

Notes

The website is built using legacy front-end technologies including jQuery 1.11.1 and jQuery UI 1.10.4, supplemented by the Cycle2 plugin for slideshow functionality. It uses Adobe Edge Web Fonts loaded over HTTP, which is outdated and insecure. The HTML structure is basic but functional, with responsive meta tags included. No modern frameworks or CMS platforms are detected. Performance is moderate with no explicit optimization techniques observed. Mobile optimization is basic, with viewport meta tags but no advanced responsive design frameworks. Accessibility features are minimal. SEO optimization is basic, with a simple title tag and meta viewport but no Open Graph or structured data markup. Hosting provider and SSL configuration details are not available from the provided data.
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 blcchurch.org.uk. 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 blcchurch.org.uk.

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.