Skip to main content

Security report for protectedtomorrows.com

Protected Tomorrows Inc. · Non-profit · United States

Medium risk. 5 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

70/100

Risk levelMedium

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

Protected Tomorrows Inc. is a specialized non-profit organization dedicated to providing compassionate guidance and resources for families and caregivers of individuals with special needs. Their market position is focused on niche services including advocacy, financial advisory, educational programs, and membership-based community support. The website offers a comprehensive range of services and resources, including free tools, expert Q&A, and a shop with educational materials, positioning them as a trusted ally in future planning for special needs families. Technically, the website is built on WordPress with WooCommerce and integrates multiple plugins for events, forms, payments, and analytics. The hosting is managed via WP Engine with Cloudflare CDN, ensuring good performance and availability. Security-wise, the site has a valid SSL certificate but lacks modern TLS protocol support and some advanced security headers. Cookie consent and privacy policies are implemented with GDPR compliance in mind, and accessibility is addressed via an ADA widget. Overall, the site demonstrates a good balance of business focus, technical maturity, and security awareness, though there is room for improvement in security hardening and transparency.

Scanned

NIS2 and GDPR posture

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

5 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 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 protectedtomorrows.com

This scan found 18 issues across 5 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
60
Security headers
15
Email security
100
DNS health
85
Network security
100
GDPR outside view
58
Average
70

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

Protected Tomorrows operates in the non-profit sector, targeting families and caregivers of individuals with special needs. Their business model combines free resources with paid memberships and an e-commerce shop, creating diversified revenue streams. The organization leverages partnerships, such as with Fortress, to enhance service delivery. Their competitive advantage lies in specialized knowledge, community building, and comprehensive support services. The website content and structure indicate a focus on education, advocacy, and financial planning, appealing to a dedicated and engaged audience. Growth indicators include active event scheduling, educational offerings, and a membership hub. The partnership ecosystem is limited but includes key service providers for payments and hosting.

Security posture

The current security posture of Protected Tomorrows is moderate. The site benefits from a valid SSL certificate and Cloudflare protection, reducing exposure to common web threats. Cookie consent mechanisms and privacy policies indicate compliance with GDPR requirements. However, the absence of modern TLS protocols (TLS 1.2/1.3) and missing security headers such as HSTS, CSP, and X-Frame-Options represent gaps that could be exploited. No public security policy or incident response information is available, which may impact transparency and readiness. The use of reCAPTCHA on forms mitigates automated abuse risks. Overall, while no critical vulnerabilities are detected, the site would benefit from enhanced security controls and public disclosure of security practices.

Recommendations

  1. Enable TLS 1.2 or TLS 1.3 protocols on the server to improve encryption standards.
  2. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  3. Add security headers such as Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.
  4. Publish a public security policy and incident response plan to increase transparency and trust.
  5. Regularly update and audit WordPress core, themes, and plugins to mitigate vulnerabilities.

Contact details published on the site

Addresses
Legal name
Protected Tomorrows Inc.
Technical notes

Notes

The website is built on a mature and widely supported platform (WordPress) with WooCommerce for e-commerce capabilities. It uses a variety of plugins to extend functionality, including event management, payment processing via Authorize.Net, cookie consent management, and analytics integration with Google services. Hosting is provided by WP Engine with Cloudflare CDN, contributing to fast load times and caching efficiency. The site is mobile-optimized and includes accessibility features. However, the lack of modern TLS support and some missing security headers indicate technical debt in security configuration. The presence of multiple JavaScript libraries and plugins suggests a moderately complex front-end architecture that requires ongoing maintenance to ensure performance 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 protectedtomorrows.com. 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 protectedtomorrows.com.

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.