Skip to main content

Security report for uclahealth.org

UCLA Health · Healthcare · United States

Low risk. 2 critical or high findings in SSL/TLS.

Security score

81/100

Risk levelLow

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

UCLA Health is a leading healthcare provider and academic medical center based in Southern California, affiliated with the University of California. The website serves patients, healthcare professionals, and the community by providing information about its hospitals, clinics, cancer center, and academic departments. It holds a strong market position as a top-ranked hospital system with a comprehensive range of healthcare services. Technically, the site is built on Drupal 11, leveraging modern web technologies including Font Awesome, Google Tag Manager, and Vimeo API, with good mobile optimization and accessibility features. Security posture is strong with HTTPS, multiple security headers, and no visible vulnerabilities, though explicit security policies and vulnerability disclosures are absent. Overall, the site demonstrates high professionalism, trustworthiness, and compliance with privacy regulations, making it a reliable digital presence for UCLA Health.

Scanned

NIS2 and GDPR posture

GDPR outside view
83/ 100 · Low
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

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

    • 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
    • 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 uclahealth.org

This scan found 15 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
57
Security headers
75
Email security
87
DNS health
85
Network security
100
GDPR outside view
83
Average
81

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention uclahealth.org, from OffSeq Breach.

Total records
1,786
Employees
0
Customers
1,741
Third parties
45
Weak passwords
8%

17 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for uclahealth.org.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

UCLA Health operates as an essential healthcare entity within the education and medical sectors, targeting patients and medical professionals. Its business model focuses on providing high-quality healthcare services combined with academic medical education. The website reflects a mature digital ecosystem with partnerships such as the UCLA School of Medicine. Revenue streams likely include patient care, research funding, and educational programs. The presence of comprehensive privacy and cookie policies indicates regulatory compliance. The organization maintains a consistent brand and strong trust signals, positioning it as a market leader in healthcare within the United States.

Security posture

The website exhibits a mature security posture with enforced HTTPS, comprehensive security headers, and secure form implementations. No exposed sensitive data or vulnerable libraries were detected. However, the absence of a published security policy, incident response contacts, or vulnerability disclosure mechanisms suggests room for improvement in transparency and incident readiness. The use of third-party scripts is controlled but should be regularly audited to mitigate supply chain risks. Overall, the security maturity is high, suitable for a healthcare institution handling sensitive information.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and compliance.
  2. Implement and publicize a vulnerability disclosure program or security.txt file.
  3. Provide clear incident response contact information for security issues.
  4. Regularly audit and update third-party scripts and libraries to prevent vulnerabilities.
  5. Enhance transparency around data retention policies and user privacy controls.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
UCLA Health
Description
Ranked as one of America's top hospitals, UCLA Health provides the best care at its 4 hospitals and more than 250 locations throughout Southern California.
Key services
Hospital care, Clinics, Cancer Center, Academic medical education
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 11, Font Awesome 6, Google Tag Manager, Vimeo Player API, Google Translate
Frameworks
Drupal CMS
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Security headers present
  • No exposed sensitive data in HTML
  • Secure forms with modal dialogs

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Tealium (utag.js)
Marketing tools
Google Translate, LoyalHealth forms
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is rich, professional, and targeted to healthcare consumers and professionals.
  3. Strong privacy and cookie policies with consent mechanisms are implemented.
  4. No security.txt or explicit vulnerability disclosure found.
  5. WHOIS data is unavailable or privacy protected, common for large institutions.
  6. Multiple external trusted domains linked, including official university and medical school sites.
  7. Use of modern technologies and frameworks with good security headers and HTTPS.
  8. Contact phone number clearly displayed with tel: link.
  9. Google Translate integration for multilingual support.
  10. No adult or questionable content detected.
Technical notes

Notes

The website is built on Drupal 11 CMS, utilizing modern front-end libraries such as Font Awesome 6 and integrating third-party services like Google Tag Manager and Vimeo Player API. The site is mobile optimized with responsive design and accessibility features. Performance is moderate, with potential for optimization in loading speed. The presence of Google Translate indicates a focus on multilingual accessibility. No major technical debt or outdated technologies were detected. Hosting provider details are not explicit but the infrastructure supports secure and scalable operations. Opportunities exist to improve technical SEO and implement advanced 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 uclahealth.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 uclahealth.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.