Skip to main content

Security report for downtownlex.com

Downtown Lexington Partnership · Non-profit · United States

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

Security score

38/100

Risk levelHigh

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

Downtown Lexington Partnership is a non-profit organization dedicated to promoting and enhancing the Downtown Lexington area as a vibrant community hub for living, working, and playing. The website serves as a comprehensive resource for residents, visitors, and businesses, offering event information, real estate listings, business directories, and community engagement opportunities. The organization positions itself as a key local leader in economic development and cultural promotion within Lexington, Kentucky. Technically, the website is built on WordPress with a modern tech stack including jQuery, Google Analytics, Google Tag Manager, and several plugins for events and forms. The site demonstrates good mobile optimization, clear navigation, and professional design, though some accessibility features could be improved. Performance is moderate, with use of CDNs and asynchronous loading of scripts. From a security perspective, the site enforces HTTPS and integrates Google reCAPTCHA for form protection, but lacks several important security headers such as Content-Security-Policy and X-Frame-Options. No critical vulnerabilities or exposed sensitive data were detected. Privacy compliance is limited, with no explicit privacy or cookie policies found, which represents a compliance gap. The WHOIS data is missing or unavailable, which raises concerns about domain registration legitimacy despite the professional website presence. Overall, the website is a well-constructed community resource with strong business credibility and user experience. However, it should address privacy compliance and security header implementation, and verify domain registration status to enhance trustworthiness and reduce risk.

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.

    • 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

  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';…

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

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

Keep watching downtownlex.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
0
Security headers
15
Email security
70
DNS health
85
Network security
20
GDPR outside view
35
Average
38

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 Downtown Lexington Partnership operates as a non-profit entity focused on community and economic development in Lexington, Kentucky. Its market positioning leverages local partnerships with banks, legal firms, and community organizations, as evidenced by stakeholder logos and event sponsorships. The business model centers on membership, event promotion, and community engagement rather than direct commercial sales. Revenue streams likely include membership fees, sponsorships, and event-related income. The target customer segments include local residents, businesses, visitors, and potential real estate clients. Growth indicators include active event promotion, social media engagement, and a regularly updated blog. The partnership ecosystem is robust with multiple local financial institutions and service providers. Strategic observations suggest a focus on maintaining strong local ties and enhancing downtown vitality through cultural and business activities.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and use of Google reCAPTCHA to protect forms from automated abuse. However, the absence of key security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options reduces the overall security posture. No visible vulnerabilities or exposed sensitive data were found in the HTML content. The lack of explicit security or incident response policies on the site indicates a potential gap in security culture and readiness. Compliance with GDPR and other privacy regulations is minimal due to missing privacy and cookie policies. Incident response readiness and data protection officer contact information are not provided, which could be improved to meet best practices. Overall, the site is secure enough for its informational purpose but should enhance security controls and compliance documentation.

Recommendations

  1. Implement comprehensive privacy and cookie policies to ensure GDPR and other privacy regulation compliance.
  2. Add and configure security headers including Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy.
  3. Verify and update WHOIS domain registration information to ensure domain legitimacy and trust.
  4. Conduct regular security audits and update WordPress core and plugins promptly to mitigate vulnerabilities.
  5. Enhance accessibility features to improve compliance with WCAG standards and user inclusivity.

Contact details published on the site

Addresses
Legal name
Downtown Lexington Partnership
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Downtown Lexington Partnership
Description
Downtown Lexington Partnership promotes Downtown Lexington as a vibrant destination for living, working, and playing. It highlights local businesses, events, real estate, and community engagement.
Key services
Event promotion, Business directory and support, Real estate listings, Community engagement and membership
Content quality
good
Branding
consistent

Technology

Stack
WordPress, jQuery, Google Analytics, Google Tag Manager, Slick Carousel, Events Manager plugin, WP FullCalendar, Formidable Forms, Constant Contact
Frameworks
WordPress
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Use of Google reCAPTCHA v2 invisible on forms
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics, MonsterInsights
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
Dstillery
Marketing tools
Constant Contact, MonsterInsights
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content and navigation
  2. No privacy or cookie policy pages detected
  3. Multiple newsletter signup forms with reCAPTCHA integration
  4. Strong social media presence on Twitter, Facebook, Instagram
  5. Use of multiple Google services for analytics and tag management
  6. Sponsors and stakeholder logos prominently displayed
  7. No explicit security or incident response policies found
  8. WHOIS data missing, raising domain registration concerns
Technical notes

Notes

The website is built on WordPress CMS with a variety of plugins including Events Manager, WP FullCalendar, Formidable Forms, and Google Analytics integration via MonsterInsights. It uses jQuery and Slick Carousel for UI components and asynchronous loading for performance optimization. The site loads external resources from reputable CDNs such as Cloudflare, jsDelivr, and Google Fonts. The presence of Google Tag Manager and reCAPTCHA indicates a mature approach to analytics and bot protection. Performance is moderate with room for improvement in caching and minimizing external requests. The site is mobile optimized with responsive design and uses modern CSS variables and gradients. Technical debt appears low, but security header implementation and privacy compliance require attention to reduce risk and improve trust.
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 downtownlex.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 downtownlex.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.