Skip to main content

Security report for catalyst-fund.com

Other · N/a

Medium risk. 9 critical or high findings in SSL/TLS, Security headers and 1 other check.

Security score

60/100

Risk levelMedium

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

The website catalyst-fund.com is currently inaccessible, returning a 403 Forbidden error page. This indicates that access to the site is blocked or restricted, likely by Cloudflare security mechanisms as evidenced by the DNS name servers. Due to the lack of accessible content, no business descriptions, contact information, or policy documents are available for analysis. The domain is registered with Network Solutions, LLC since 1999, which suggests a long-standing presence, but no registrant details are provided to verify legitimacy. The technical infrastructure shows Cloudflare DNS usage but lacks DNSSEC and security headers, indicating room for security improvements. Overall, the website's security posture is limited by the lack of accessible content and missing security best practices. The absence of privacy and cookie policies, contact details, and business information further reduces trust and compliance confidence.

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

  2. 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 catalyst-fund.com

This scan found 24 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
37
Security headers
15
Email security
85
DNS health
85
Network security
100
GDPR outside view
35
Average
60

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

Due to the 403 Forbidden error blocking access, no business intelligence data such as market positioning, services, or partnerships can be extracted. The domain age suggests an established entity, but without accessible content or registrant details, the business model and target audience remain unknown. No external business-related domains or social media links were found to infer partnerships or ecosystem. The lack of visible business information limits the ability to assess competitive advantages or growth indicators.

Security posture

The website is protected or blocked by Cloudflare, resulting in a 403 Forbidden error page. DNSSEC is not enabled, and no security headers are present in the HTML content. No forms or inputs are available to assess secure data handling. The absence of privacy, cookie, and security policies indicates compliance gaps. The domain registration is consistent and long-standing, which is a positive trust factor. However, the lack of accessible content and security best practices reduces the overall security maturity. Incident response contacts and vulnerability disclosure mechanisms are not found, limiting readiness for security events.

Recommendations

  1. Enable DNSSEC to enhance DNS security and prevent spoofing.
  2. Review Cloudflare security settings to ensure legitimate users can access the website.
  3. Implement and publish comprehensive privacy and cookie policies to improve compliance.
  4. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Provide clear contact information and business details to improve trust and credibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. The website returns a 403 Forbidden error page with Cloudflare DNS name servers, indicating access is blocked or restricted by Cloudflare security. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
Cloudflare DNS
SEO
poor

Security

Observed score
20/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is inaccessible due to 403 Forbidden error.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact information or forms available on the page.
  4. No scripts or analytics detected in the HTML content.
  5. Website appears to be protected or blocked by Cloudflare security.
  6. No business or security policy information is publicly available.
  7. WHOIS data shows a long-registered domain with no privacy protection but lacks registrant details.
  8. No external business-related links or social media profiles found.
  9. Website SEO and accessibility are poor due to lack of content.
  10. No evidence of advertising or tracking technologies.
Technical notes

Notes

The website uses Cloudflare DNS services but does not have DNSSEC enabled, which is a recommended security enhancement. The HTML content is minimal and serves only a 403 Forbidden error page with no scripts or analytics detected. No CMS or frameworks are identifiable from the content. The site lacks meta tags for SEO and accessibility features. Hosting appears to be behind Cloudflare, but performance and mobile optimization cannot be assessed due to blocked content. The absence of forms or interactive elements limits data collection and user engagement capabilities.
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 catalyst-fund.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 catalyst-fund.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.