Skip to main content

Security report for spartanfund.net

Spartan Fund · Education · United States

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

Security score

48/100

Risk levelHigh

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

Spartan Fund is a philanthropic organization dedicated to supporting Michigan State University Athletics by raising funds to empower student-athletes through scholarships, facilities, endowments, and premium seating. The website reflects a well-established non-profit with a clear mission to engage donors and enhance the Spartan athletic experience. The organization targets alumni, sports fans, and donors interested in collegiate athletics philanthropy. Technically, the site uses modern web technologies including Bootstrap and asynchronous JavaScript modules, hosted on AWS infrastructure, and integrates Google Tag Manager for analytics. The site is mobile-optimized with excellent design and navigation, providing a professional user experience. Security posture is good with HTTPS and domain transfer protections, but lacks DNSSEC and security headers. Privacy and cookie policies are absent, indicating compliance gaps. Overall, the site is trustworthy and credible but would benefit from enhanced privacy and security disclosures.

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.

    • Critical

      Unable to retrieve SSL certificate

      Could not establish secure connection to retrieve certificate information

      What to do: Check if the server is accessible and SSL/TLS is properly configured

  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 spartanfund.net

This scan found 22 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
0
Security headers
15
Email security
60
DNS health
75
Network security
100
GDPR outside view
35
Average
48

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

The Spartan Fund operates in the education and non-profit sectors, focusing on fundraising for collegiate athletics at Michigan State University. Its business model revolves around donor engagement and philanthropic contributions to support athletic scholarships, capital projects, and programmatic endowments. The organization leverages partnerships with official MSU platforms for ticketing and donations, enhancing operational efficiency. The website's content and testimonials reinforce its market position as a trusted fundraising entity with a strong community presence. Growth opportunities include expanding digital engagement and improving transparency around privacy and security policies to build donor confidence.

Security posture

The website demonstrates a moderate to good security maturity level with HTTPS enforced and domain transfer protections in place. However, the absence of DNSSEC and security headers such as Content-Security-Policy and Strict-Transport-Security represents areas for improvement. No vulnerabilities or exposed sensitive data were detected in the HTML content. The lack of published incident response or vulnerability disclosure policies suggests limited readiness for security incidents. Compliance with GDPR and other privacy regulations is weak due to missing privacy and cookie policies. Enhancing these areas would strengthen the overall security posture and regulatory compliance.

Recommendations

  1. Enable DNSSEC on the domain to protect against DNS spoofing and improve DNS security.
  2. Implement standard security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish comprehensive privacy and cookie policies with clear GDPR compliance statements.
  4. Add a vulnerability disclosure or security.txt file to facilitate responsible reporting of security issues.
  5. Provide clear contact information for security incidents and data protection inquiries to improve incident response readiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Spartan Fund
Description
Spartan Fund is a philanthropic organization supporting Michigan State University Athletics. It empowers nearly 700 student-athletes through donations that fund scholarships, facilities, endowments, and premium seating. The fund aims to elevate the experience for Spartan supporters and student-athletes alike.
Key services
Fundraising for athletic scholarships, Capital projects and facilities support, Endowments for coaching and programs, Premium seating and parking management, Donor engagement and benefits
Content quality
excellent
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript ES6 Modules, Bootstrap 5, YouTube iframe API, Google Tag Manager
Frameworks
Bootstrap
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced (implied by URL)
  • ClientTransferProhibited domain status
  • No exposed sensitive data in HTML
  • Use of secure external donation platforms

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Google Analytics (via Google Tag Manager)
Transparency
basic

Site quality

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

Key observations

  1. Website is professionally designed with clear navigation and rich content.
  2. No explicit privacy, cookie, or terms of service policies found on the main page.
  3. No contact emails or phone numbers explicitly listed on the homepage or navigation.
  4. External donation and login links point to official MSU ticketing and donation platforms.
  5. Social media presence is strong with official MSU Spartan Fund accounts on Facebook, Instagram, Twitter (X), and YouTube.
  6. No forms detected on the homepage; donation and login handled externally.
  7. Use of modern web technologies and asynchronous loading for performance.
  8. No security.txt or vulnerability disclosure found.
  9. No explicit security or incident response policies published.
Technical notes

Notes

The website is built using modern web standards with HTML5, CSS3, and JavaScript ES6 modules. It uses Bootstrap 5 for responsive design and layout, ensuring excellent mobile optimization and accessibility. Hosting is via AWS, indicated by the use of AWS DNS servers, providing reliable infrastructure. Google Tag Manager is used for analytics and tracking, enabling data-driven insights. Performance is fast with asynchronous script loading and optimized media assets. No CMS was detected, suggesting a custom or static site architecture. Technical risks include missing DNSSEC and security headers, which could be addressed to reduce attack surface and improve security compliance.
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 spartanfund.net. 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 spartanfund.net.

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.