Skip to main content

Security report for jeffersonrams.com

Thomas Jefferson University · Education · United States

Medium risk. 5 critical or high findings in Email security, Security headers and 2 other checks.

Security score

73/100

Risk levelMedium

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

Thomas Jefferson University operates an official athletics website serving as the primary digital platform for its NCAA Division II sports programs. The site provides comprehensive sports-related content including schedules, rosters, news, and community engagement resources targeted at students, athletes, and fans. The university positions itself as a competitive participant within the Central Atlantic Collegiate Conference (CACC), leveraging digital tools to enhance fan and community interaction. Technically, the website is built on the Sidearm Sports platform, utilizing a mix of modern and legacy web technologies such as Google Analytics, Google Tag Manager, jQuery, and Knockout.js. Hosting and content delivery are managed via Cloudfront CDN and Rackspace DNS services, ensuring moderate performance and good mobile optimization. Accessibility features and SEO practices are adequately implemented, contributing to a positive user experience. From a security perspective, the site benefits from HTTPS encryption and domain transfer protections but lacks advanced DNS security measures like DNSSEC and important HTTP security headers. Privacy compliance is partial, with a privacy policy present but no visible cookie consent mechanism or GDPR-specific disclosures. No incident response or vulnerability disclosure information is publicly available, indicating room for maturity in security governance. Overall, the website is trustworthy and professionally maintained, with a solid foundation for athletics content delivery. Strategic improvements in security headers, privacy compliance, and incident response transparency would enhance the site's security posture and regulatory adherence.

Scanned

NIS2 and GDPR posture

GDPR outside view
70/ 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. 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. 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 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';…

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

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

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

Keep watching jeffersonrams.com

This scan found 20 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
72
Security headers
65
Email security
60
DNS health
70
Network security
100
GDPR outside view
70
Average
73

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

Thomas Jefferson University Athletics operates within the education sector, focusing on collegiate sports engagement. The business model centers on providing athletics information and fostering community involvement rather than direct revenue generation. The university leverages partnerships such as recruitment services and advertising networks to support operations. The athletics site serves a medium-sized audience primarily composed of students, alumni, and sports enthusiasts. Growth indicators include active social media presence and integration with university recruitment platforms. Competitive advantages lie in official NCAA affiliation and comprehensive sports coverage. The partnership ecosystem includes advertising and analytics providers, with potential for expansion into enhanced digital marketing and fan engagement tools.

Security posture

The current security maturity level is moderate. HTTPS is enforced, and domain transfer protections are in place, reducing risks of domain hijacking. However, the absence of DNSSEC and critical HTTP security headers such as Content-Security-Policy and Strict-Transport-Security exposes the site to potential DNS spoofing and clickjacking attacks. No explicit incident response or vulnerability disclosure policies are published, which may delay response to security incidents. Privacy compliance gaps, particularly the lack of cookie consent mechanisms, could lead to regulatory scrutiny under GDPR or similar frameworks. The use of older JavaScript libraries like jQuery 1.9.1 may introduce vulnerabilities if not regularly updated. Overall, the security culture appears functional but would benefit from formalized policies and technical hardening.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement comprehensive HTTP security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Add a cookie consent banner and update privacy disclosures to align with GDPR and other privacy regulations.
  4. Publish an incident response plan and vulnerability disclosure policy to improve transparency and readiness.
  5. Regularly update third-party libraries and dependencies to mitigate known vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Thomas Jefferson University
Description
Official athletics website for Thomas Jefferson University, providing sports news, schedules, rosters, and related athletics content.
Key services
Sports schedules, Team rosters, News and archives, Athletics communications, Community engagement
Content quality
good
Branding
consistent

Technology

Stack
Google Analytics, Google Tag Manager, jQuery 1.9.1, RequireJS 2.2.0, Knockout.js, Underscore.js, LazySizes, Slick Carousel, Sidearm Sports platform
Frameworks
Sidearm Sports CMS
Platforms
Cloudfront CDN, Rackspace DNS
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • ClientTransferProhibited domain status

Analytics and tracking

Services
Google Analytics, comScore
Tracking level
extensive
Privacy practices
basic

Advertising

Ad networks
Google DFP, Sidearm Ads
Tracking pixels
comScore, Scorecard Research
Marketing tools
ID5
Transparency
basic

Site quality

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

Key observations

  1. Website is an official university athletics site with comprehensive sports coverage.
  2. Uses multiple analytics and advertising services indicating active marketing and user engagement.
  3. No explicit privacy or cookie consent mechanisms detected, which may be a compliance gap.
  4. Technical stack is modern but includes some older libraries (jQuery 1.9.1).
  5. No visible security headers in HTML content; opportunity for security improvements.
  6. WHOIS data is consistent and domain is not privacy protected, supporting legitimacy.
Technical notes

Notes

The website infrastructure is based on the Sidearm Sports CMS platform, supported by AWS Cloudfront CDN and Rackspace DNS services. The technology stack includes a mix of modern analytics and tag management tools alongside legacy JavaScript libraries, which may pose maintenance challenges. Performance is moderate with good mobile responsiveness and accessibility features. SEO is well addressed through meta tags and structured data, although some JSON-LD data appears incomplete or placeholder. The site lacks some modern security headers and DNS security features, indicating technical debt in security hardening. Opportunities exist to modernize the tech stack, improve performance, and enhance security configurations to reduce operational risks.
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 jeffersonrams.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 jeffersonrams.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.