Skip to main content

Security report for bethelhouseinc.org

Bethel House of Whitewater · Non-profit · United States

Medium risk. 9 critical or high findings in Email security, SSL/TLS and 2 other checks.

Security score

57/100

Risk levelMedium

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

Bethel House of Whitewater is a small nonprofit organization dedicated to preventing homelessness among local children and families. Founded in 1994, it offers a range of support programs including transitional housing, emergency financial assistance, case management, and a client toiletry pantry. The organization relies heavily on community donations and volunteers to fulfill its mission, positioning itself as a grassroots community pillar with a strong local presence. The website reflects this mission with clear calls to action for support and volunteering, and maintains active social media channels to engage the community. Technically, the website is built on the Duda platform, utilizing modern web technologies such as jQuery, service workers, and CDN hosting via Cloudfront. The site is mobile optimized and performs moderately well, though accessibility and SEO could be improved. Analytics are implemented via Snowplow, indicating some level of user behavior tracking, but privacy compliance is lacking as no privacy or cookie policies are present. From a security perspective, the site enforces HTTPS and uses service workers, but lacks important security headers and formal security policies or incident response contacts. No vulnerabilities or exposed sensitive data were detected in the content. The WHOIS data is unavailable or privacy protected, which is typical for nonprofits and does not raise immediate concerns. Overall, the site is trustworthy and professional but would benefit from enhanced privacy and security compliance. Strategically, Bethel House should prioritize implementing comprehensive privacy and cookie policies, improve security headers, and consider publishing a vulnerability disclosure or security.txt file to enhance trust and compliance. These steps will strengthen their security posture and align with best practices for nonprofit organizations handling sensitive client information.

Scanned

NIS2 and GDPR posture

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

9 findings rated critical or high. Fix these first.

  1. 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

  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

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

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

Keep watching bethelhouseinc.org

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
69
Security headers
15
Email security
60
DNS health
60
Network security
100
GDPR outside view
35
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

Bethel House operates in the nonprofit sector focused on housing stability and homelessness prevention. Its competitive advantage lies in its long-standing local presence and community-driven support model. Revenue streams are primarily donations and volunteer contributions. The target customers are local families at risk of homelessness and community volunteers. Growth indicators include a 30-year history and active social media engagement. The organization appears to maintain a lean operational model without subsidiaries or parent companies. Partnerships are implied through community and church support but no explicit partner domains are listed. The website content and structure suggest a focus on transparency and community engagement, which supports donor confidence and volunteer recruitment.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and no visible sensitive data exposure. However, the absence of key security headers such as Content-Security-Policy and X-Frame-Options reduces protection against common web attacks. The lack of privacy and cookie policies indicates compliance gaps with GDPR and other data protection regulations. No incident response or security contact information is provided, limiting readiness for security events. The use of third-party scripts like Snowplow and embedded forms from dvforms.net introduces potential risk vectors that require regular auditing. Overall, the security posture is adequate for a small nonprofit but requires improvements to meet higher compliance and security standards.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie consent mechanism to ensure GDPR and privacy compliance.
  2. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance web security.
  3. Establish a vulnerability disclosure policy or security.txt file to provide clear channels for reporting security issues.
  4. Improve accessibility features to make the website usable for a wider audience including those with disabilities.
  5. Regularly audit third-party scripts and embedded forms for security vulnerabilities and update them as needed.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Bethel House of Whitewater
Description
Bethel House is an ecumenical nonprofit organization founded in 1994 with the goal to provide compassionate support to local families to keep them safely housed. They offer programs such as Transitional Housing, Emergency Assistance, Case Management Services, and a Toiletry Pantry to prevent homelessness for children and families in the Whitewater area.
Key services
Transitional Housing Program, Emergency Assistance Program, Case Management Services, Toiletry Pantry, Volunteer opportunities
Content quality
good
Branding
consistent

Technology

Stack
jQuery 3.7.0, skrollr, Snowplow analytics, Cloudfront CDN, Service Worker, dvforms.net embedded forms
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Service Worker registered
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Snowplow
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Snowplow
Marketing tools
Snowplow 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 challenge
  2. Content is focused on nonprofit housing support services
  3. Clear navigation with multiple program pages
  4. Contact info includes emails, phone, physical address, and embedded contact form
  5. No privacy or cookie policies found, indicating compliance gap
  6. Modern technologies used but no advanced security headers detected
  7. Social media presence on Facebook, Twitter, YouTube, Instagram
  8. No explicit or adult content detected
  9. WHOIS data unavailable, likely privacy protected
Technical notes

Notes

The website is built on the Duda platform, leveraging modern JavaScript libraries including jQuery 3.7.0 and skrollr for animations. It uses Cloudfront CDN for content delivery and registers a service worker for offline capabilities. Fonts are loaded from Google Fonts with multiple font families for branding consistency. Analytics are implemented via Snowplow, indicating a custom tracking setup. The site is mobile responsive with good navigation clarity. Performance is moderate, with room for optimization in CSS loading and script management. No major technical debt or legacy technologies were detected, but accessibility and SEO optimizations are basic and could be enhanced for better user experience and search engine ranking.
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 bethelhouseinc.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 bethelhouseinc.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.