Skip to main content

Security report for letgrow.org

Let Grow, INC. · Non-profit · United States

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

Security score

64/100

Risk levelMedium

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

Let Grow, INC. is a US-based non-profit organization founded in 2011, dedicated to advocating for children's independence and providing educational resources to parents and communities. The organization positions itself as a trusted advocate in child development, emphasizing the importance of fostering capable and confident adults through independence. The website reflects a professional and consistent brand image, targeting parents, educators, and community stakeholders. Technically, the site is built on WordPress with modern integrations such as Gravity Forms, Google Fonts, and Cloudflare DNS, offering a good user experience with mobile optimization and SEO best practices. Security posture is moderate, with HTTPS enabled and domain protections in place, but lacking advanced security headers and DNSSEC. Privacy compliance is limited, with no explicit privacy or cookie policies detected, which is an area for improvement. Overall, the website is trustworthy and functional, supporting the organization's mission effectively.

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

6 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 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

  3. 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 SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching letgrow.org

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. See sample alerts.

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
65
Security headers
30
Email security
70
DNS health
65
Network security
100
GDPR outside view
53
Average
64

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 letgrow.org, from OffSeq Breach.

Total records
43
Employees
0
Customers
43
Third parties
0
Weak passwords
5%

1 subdomain affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for letgrow.org.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

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 in the non-profit sector focusing on child independence advocacy. Its business model revolves around education, legal advocacy, and community engagement. The domain age and WHOIS data support its legitimacy and established presence. The website integrates social media channels to extend its outreach and engagement. While no direct revenue streams or partnerships are explicitly listed, the presence of contact forms and clear communication channels indicate active community involvement. The organization's market position is that of a niche non-profit with a clear mission and consistent branding. Growth potential lies in expanding educational resources and legal support services.

Security posture

The website employs HTTPS and benefits from registrar-level domain protections such as clientDeleteProhibited status. However, it lacks DNSSEC and several important HTTP security headers, which could expose it to certain web-based attacks. No evidence of incident response policies or security certifications was found. The use of third-party scripts like Google Tag Manager introduces moderate tracking but no obvious vulnerabilities. The absence of privacy and cookie policies indicates potential compliance gaps with GDPR and other privacy regulations. Overall, the security posture is adequate for a non-profit informational site but could be enhanced with better header policies and privacy compliance.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy with consent mechanisms to improve privacy compliance.
  2. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  3. Add critical security headers such as Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy to strengthen web security.
  4. Conduct a security audit of all third-party scripts and forms to ensure no vulnerabilities or data leakage.
  5. Establish and communicate an incident response plan and security contact channels to improve security readiness and transparency.

Contact details published on the site

Addresses
Legal name
Let Grow, INC.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Let Grow, INC.
Description
At Let Grow, we believe today’s kids are smarter and stronger than our culture gives them credit for. Treating them as physically and emotionally fragile is bad for their future — and ours. Let Grow is making it easy, normal and legal to give kids the independence they need to grow into capable, confident, and happy adults.
Key services
Advocacy for child independence, Educational resources, Legal support for independence initiatives
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Gravity Forms, Cloudflare DNS, Google Fonts, Font Awesome, Yoast SEO
Frameworks
WordPress
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
65/100
Good practices seen
  • HTTPS enabled
  • Domain status includes clientDeleteProhibited and other EPP protections
  • Use of Cloudflare DNS

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Marketing tools
Yoast SEO
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. Content is professionally presented and relevant to child independence advocacy.
  3. No explicit privacy or cookie policies found on the main page or in metadata.
  4. Contact information is clearly provided including email, phone, and physical address.
  5. Use of modern web technologies and SEO best practices is evident.
  6. Security headers are minimal; DNSSEC is not enabled.
  7. WHOIS data shows privacy protection but domain age and registrar are consistent with legitimate use.
Technical notes

Notes

The website is built on WordPress CMS with integrations including Gravity Forms for form handling, Yoast SEO for search optimization, and Google Fonts and Font Awesome for typography and icons. Hosting and DNS are managed via GoDaddy and Cloudflare respectively, providing reliable infrastructure. Performance is moderate with some optimization evident through lazy loading scripts and preloading fonts. Mobile responsiveness is good, and accessibility features are basic but present. SEO is well addressed with meta tags and structured data in JSON-LD format. Technical risks include lack of DNSSEC and missing security headers, which should be addressed to reduce attack surface. Overall, the technical infrastructure supports the organization's goals effectively with room for security and privacy enhancements.
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 letgrow.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 letgrow.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.