Skip to main content

Security report for lexingtonlegends.com

Lexington Legends · Retail · United States

Medium risk. 5 critical or high findings in GDPR outside view and SSL/TLS.

Security score

73/100

Risk levelMedium

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

Lexington Legends is a professional baseball team based in Central Kentucky, offering ticket sales, merchandise, and community engagement through a well-structured Shopify e-commerce website. The site targets local sports fans and community members, providing various ticketing options and branded merchandise. Technically, the website leverages modern e-commerce technologies including Shopify, Google Analytics, and hCaptcha, ensuring a performant and mobile-optimized user experience. Security posture is solid with HTTPS and form protections, though explicit security headers and policies are not clearly published. The absence of WHOIS data for the domain is a notable anomaly that impacts trustworthiness. Overall, the site is functional and professional but would benefit from enhanced transparency in privacy and security policies.

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

5 findings rated critical or high. Fix these first.

  1. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics, Facebook, Twitter, YouTube

      What to do: Document all third-party data sharing in your privacy policy

  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.

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

This scan found 19 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
75
Security headers
75
Email security
65
DNS health
85
Network security
100
GDPR outside view
35
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

The Lexington Legends operate in the retail and sports entertainment sectors, focusing on regional market penetration in Central Kentucky. Their business model combines live event ticketing with online merchandise sales, supported by community programs like Kids Club and special events. The website integrates with partners such as MLB ticketing platforms and streaming services like FloSports, indicating a connected ecosystem. The company appears small in size but maintains a consistent brand presence online. Growth opportunities include expanding digital engagement and improving compliance transparency.

Security posture

The website demonstrates a moderate to good security maturity level with HTTPS enforcement and use of CAPTCHA to protect forms. However, the lack of visible privacy, cookie, and terms of service policies, as well as no published incident response or vulnerability disclosure information, indicates gaps in compliance and transparency. No critical vulnerabilities or exposed sensitive data were detected in the HTML content. The missing WHOIS data raises questions about domain registration legitimacy, which should be addressed to improve trust. Overall, the security posture is adequate for the business type but can be enhanced by publishing clear policies and security contact information.

Recommendations

  1. Publish comprehensive privacy, cookie, and terms of service policies prominently on the website.
  2. Add explicit security headers such as Content-Security-Policy and X-Frame-Options to strengthen security.
  3. Provide clear contact information including security incident reporting channels.
  4. Implement and publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Investigate and resolve the missing WHOIS data issue to improve domain registration transparency and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Lexington Legends
Description
Central Kentucky's professional baseball team. Let’s play ball, y’all.
Key services
Ticket sales (single game, season, mini plans, groups, luxury suites), Merchandise sales via online shop, Community engagement (Kids Club, special events), Game day information and promotions
Content quality
good
Branding
consistent

Technology

Stack
Shopify, JavaScript, Google Analytics, Google Tag Manager, Font Awesome, Shopify Payments, hCaptcha
Frameworks
Shopify Liquid, Shopify storefront APIs
Platforms
Shopify e-commerce platform
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • Use of HTTPS
  • Use of hCaptcha for form protection
  • No exposed sensitive data in HTML
  • No visible vulnerable libraries

Analytics and tracking

Services
Google Analytics, Shopify Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
attn.tv
Tracking pixels
Shopify Pixel
Marketing tools
Shopify marketing apps, Tabs bestfreecdn, ElfSight widgets
Transparency
basic

Site quality

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

Key observations

  1. Website is a professionally designed e-commerce site for a regional baseball team.
  2. Uses Shopify platform with multiple third-party integrations.
  3. No visible privacy, cookie, or terms of service pages found in the provided HTML.
  4. No explicit contact emails or phone numbers found in the HTML content.
  5. No security.txt or vulnerability disclosure information found.
  6. WHOIS data is missing, which is unusual and reduces trust.
  7. No WAF or blocking detected; site content is fully accessible.
  8. Site uses multiple external scripts and tracking pixels, indicating moderate user tracking.
Technical notes

Notes

The website is built on the Shopify platform, utilizing modern JavaScript libraries and third-party integrations for analytics, marketing, and user engagement. Performance is optimized with CDN hosting and asynchronous script loading. The site is mobile responsive and accessible with semantic HTML and ARIA roles. Technical debt appears low, but reliance on multiple external scripts could pose risks if not regularly audited. SEO is supported by proper meta tags and Open Graph data. Opportunities exist to enhance security headers and formalize privacy and compliance mechanisms.
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 lexingtonlegends.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 lexingtonlegends.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.