Skip to main content

Security report for uoflhealth.org

UofL Health · Healthcare · United States

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

Security score

78/100

Risk levelLow

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

UofL Health is a large, not-for-profit academic health system serving Kentucky and Indiana, operating multiple hospitals, medical centers, and physician practices. The website reflects a professional healthcare provider platform with a focus on patient services, appointments, and community engagement. The technical infrastructure is based on WordPress with modern web technologies including Bootstrap and JavaScript libraries, delivering a good user experience with mobile optimization and SEO best practices. Security posture is solid with HTTPS and security headers, though DNSSEC is not enabled and no explicit vulnerability disclosure or incident response policies are published. Privacy compliance is limited due to missing privacy and cookie policies. Overall, the website is trustworthy and well-positioned for its audience but could improve transparency and compliance documentation.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 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

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

    • 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

  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

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

Keep watching uoflhealth.org

This scan found 17 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
62
Security headers
85
Email security
85
DNS health
85
Network security
100
GDPR outside view
53
Average
78

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

UofL Health holds a strong regional market position as a comprehensive academic health system with a broad service portfolio including specialty care, emergency services, and research. The business model is non-profit, targeting patients, visitors, and healthcare professionals. The organization leverages digital channels including social media and online portals to engage stakeholders. The website supports business operations with appointment scheduling and patient portals but lacks explicit contact emails or phone numbers on the homepage. The absence of privacy and security policy disclosures suggests room for maturity in compliance and risk management. Partnerships and subsidiary relationships are not explicitly detailed on the site.

Security posture

The website demonstrates a mature security posture with HTTPS enforced and multiple security headers implemented. However, the lack of DNSSEC reduces DNS security resilience. No security.txt or vulnerability disclosure policy is present, limiting transparency for security researchers. Incident response contact information is not published, which may hinder timely reporting of security incidents. Forms are present but no explicit security measures or privacy notices accompany them. Overall, the site is secure but could enhance its security culture and compliance visibility.

Recommendations

  1. Publish comprehensive privacy and cookie policies including GDPR compliance details.
  2. Enable DNSSEC to strengthen domain name system security.
  3. Add a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  4. Provide clear incident response contact information for security issues.
  5. Enhance accessibility features to meet compliance standards and improve user experience.

Contact details published on the site

Addresses
Legal name
UofL Health
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
UofL Health
Description
UofL Health is a not-for-profit 501(c)(3) fully integrated regional academic health system with nine hospitals, four medical centers, more than 250 physician practice locations, and more than 1,200 providers.
Key services
Hospitals, Medical Centers, Physician Practice Locations, Emergency Rooms, Urgent Care, Primary Care, Transplant Services, Research
Content quality
good
Branding
consistent

Technology

Stack
WordPress, PHP, JavaScript, jQuery, Revolution Slider, Bootstrap, Google Tag Manager
Frameworks
Bootstrap
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Security headers present
  • No exposed sensitive data in HTML
  • Use of Google Tag Manager for analytics

Analytics and tracking

Services
Google Analytics (via Google Tag Manager), TVSquared
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
TVSquared
Transparency
basic

Site quality

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

Key observations

  1. Website is a professional healthcare provider site for UofL Health.
  2. Content is rich with multiple services and locations.
  3. No explicit privacy or cookie policies found on homepage or main navigation.
  4. Uses modern web technologies and WordPress CMS.
  5. Security headers and HTTPS are properly implemented.
  6. No visible contact emails or phone numbers explicitly labeled on homepage; contact forms and portal links present.
  7. Social media presence is strong with official accounts linked.
  8. No evidence of adult or questionable content.
  9. No WAF or blocking mechanisms detected.
Technical notes

Notes

The website is built on WordPress CMS with a modern tech stack including Bootstrap and jQuery. It uses third-party services such as Google Tag Manager and TVSquared for analytics and tracking. The site is mobile optimized and SEO friendly with proper meta tags and structured data (JSON-LD). Performance is moderate, with some heavy slider components. Hosting is via GoDaddy as per WHOIS data. No critical technical vulnerabilities are evident in the HTML content. The site could benefit from improved accessibility and performance optimizations.
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 uoflhealth.org. 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 uoflhealth.org.

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.