Skip to main content

Security report for volleyballfoundation.com

Volleyball Foundation · Non-profit · N/a

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

Security score

67/100

Risk levelMedium

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

The Volleyball Foundation is a non-profit initiative established in 2024 by the FIVB to leverage volleyball's global reach for community upliftment through impactful projects. The foundation operates globally, targeting communities, donors, and the social impact sector with services including project support, fundraising, advocacy, and partnerships. The website is professionally built on WordPress using Elementor and GiveWP for donations, with integrated Google Analytics and Stripe payment processing. While the technical infrastructure is modern and secure with HTTPS and Cloudflare DNS, there are gaps in privacy compliance such as missing privacy and cookie policies and no GDPR consent mechanism. Security posture is good but could be enhanced by enabling DNSSEC and adding security headers. Overall, the site presents a credible and trustworthy image but should improve transparency and compliance documentation.

Scanned

NIS2 and GDPR posture

GDPR outside view
80/ 100 · Low
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 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

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

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

Keep watching volleyballfoundation.com

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
52
Security headers
30
Email security
70
DNS health
70
Network security
100
GDPR outside view
80
Average
67

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 volleyballfoundation.com, from OffSeq Breach.

No leaked records found

Breach holds no records for volleyballfoundation.com right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The foundation positions itself as a global non-profit leveraging volleyball for social good, with a clear business model focused on community projects and fundraising. Its competitive advantage lies in its affiliation with FIVB and use of volleyball professionals for advocacy. Revenue streams are primarily donations facilitated through Stripe. The target audience includes global communities, volleyball enthusiasts, donors, and social impact organizations. The website indicates growth potential with project submissions and partner engagement. The partnership ecosystem includes payment processors like Stripe and analytics providers like Google. Strategic observations suggest the foundation is in early stages with room to enhance compliance and contact transparency.

Security posture

The website demonstrates a moderate to good security maturity level with HTTPS enforced, clientTransferProhibited domain status, and Cloudflare DNS/registrar usage. However, DNSSEC is not enabled, and no explicit Content-Security-Policy or security.txt files are present. There is no visible incident response or vulnerability disclosure information. Forms are integrated via GiveWP and Stripe, but explicit anti-CSRF or input validation details are not visible. Privacy compliance is limited, lacking cookie consent and privacy policy documentation. The security culture appears nascent, with opportunities to improve transparency and technical controls to reduce risk.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Publish a comprehensive privacy policy and cookie policy with GDPR compliance details.
  3. Implement a cookie consent mechanism to comply with privacy regulations.
  4. Add a security.txt file and vulnerability disclosure policy to improve incident response readiness.
  5. Configure Content-Security-Policy and other security headers to mitigate XSS and related attacks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Volleyball Foundation
Description
The Volleyball Foundation, an initiative by the FIVB, was established in May 2024. The Foundation uses the global reach and power of volleyball to support community projects worldwide that have a positive impact.
Key services
Community projects support, Fundraising, Resource provision, Project implementation, Impact assessment, Advocacy and ambassadorship
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Elementor, Yoast SEO, GiveWP (donation plugin), Google Analytics, Google Tag Manager, Stripe payment integration, Jetpack
Frameworks
Elementor
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited domain status
  • Use of Cloudflare DNS and registrar for protection

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
Google Ads
Marketing tools
MonsterInsights (Google Analytics plugin), Google Site Kit
Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is a professionally designed WordPress site using Elementor and GiveWP for donations.
  2. No explicit privacy, cookie, or terms of service policies found on the homepage or main navigation.
  3. No contact emails or phone numbers explicitly listed on the homepage or header/footer areas.
  4. Social media presence limited to Instagram link only.
  5. Strong use of structured data (JSON-LD) for SEO and organization information.
  6. Multiple Google Analytics and Google Tag Manager scripts present indicating moderate user tracking.
  7. Stripe payment integration for donations is live and configured with a publishable key.
  8. No visible security.txt or vulnerability disclosure page.
  9. No GDPR cookie consent banner or mechanism detected.
  10. Site uses HTTPS with Cloudflare DNS and registrar but DNSSEC is not enabled.
Technical notes

Notes

The website is built on a modern WordPress platform with Elementor page builder and GiveWP for donations, integrating Stripe for payment processing. Google Analytics and Tag Manager are used for user tracking. The site is hosted behind Cloudflare DNS and registrar services, providing performance and security benefits. Performance is moderate with good mobile optimization. SEO is enhanced by Yoast SEO plugin and structured data (JSON-LD). Accessibility is basic but could be improved. Technical risks include missing DNSSEC and security headers, and lack of documented privacy and security policies. Overall, the infrastructure is solid but requires enhancements for compliance and security best practices.
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 volleyballfoundation.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 volleyballfoundation.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.