Skip to main content

Security report for stanfordhealthcarenow.org

Stanford Health Care · Healthcare · United States

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

Security score

73/100

Risk levelMedium

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

Stanford Health Care is a leading academic medical center and healthcare provider delivering advanced medical services including cancer treatment, heart disease care, brain disorder treatment, and primary care. The organization leverages cutting-edge technology and research to provide compassionate, patient-centered care. Their digital presence is supported by a robust technical infrastructure including Adobe Experience Manager CMS, AWS hosting, and modern analytics tools such as Google Analytics and Adobe Launch. The website is professionally designed, mobile-optimized, and provides clear navigation and comprehensive content relevant to patients, healthcare professionals, and visitors. Security posture is strong with HTTPS enforcement and domain security best practices, though DNSSEC is not enabled. Privacy and cookie policies are present with consent mechanisms, indicating good compliance with GDPR and related regulations. Overall, the website reflects a mature, trustworthy healthcare institution with a high level of digital maturity and security awareness.

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

5 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 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 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 stanfordhealthcarenow.org

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
67
Security headers
40
Email security
95
DNS health
85
Network security
100
GDPR outside view
53
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

Stanford Health Care operates in the healthcare sector as an essential entity with an enterprise scale. It maintains a strong market position as a top academic medical center with a comprehensive range of services and a focus on innovation and patient care. The business model centers on providing specialized medical treatments, clinical trials, and patient engagement through digital tools like MyHealth. The organization has a well-established partnership ecosystem including quality assurance and donation platforms. The website content and structure support growth and patient outreach, with clear branding and trust signals. The domain age and registration details align with the organization's history and reputation.

Security posture

The website demonstrates a good security maturity level with HTTPS enabled, domain status protections, and no visible vulnerabilities or exposed sensitive data. Security headers are partially implemented but could be improved by adding Content-Security-Policy and X-Content-Type-Options headers. The use of third-party scripts is standard for analytics and marketing but should be regularly audited. No incident response or security policy pages were found, which could be an area for enhancement. Overall, the security posture supports business continuity and data protection but has room for incremental improvements.

Recommendations

  1. Enable DNSSEC to enhance DNS security and prevent spoofing.
  2. Implement a comprehensive Content-Security-Policy header to mitigate XSS risks.
  3. Add explicit security headers such as X-Content-Type-Options and Referrer-Policy.
  4. Publish a dedicated security policy and incident response contact information to improve transparency.
  5. Regularly review and update third-party scripts and analytics tools to minimize vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Stanford Health Care
Description
Stanford Health Care brings together leading-edge technology, innovative research, and world-renowned experts to meet unique healthcare needs, delivering high levels of care and compassion for conditions including cancer, heart disease, brain disorders, and primary care.
Key services
Cancer treatment, Heart disease care, Brain disorder treatment, Primary care, Clinical trials, Video visits, Patient portal (MyHealth)
Content quality
excellent
Branding
consistent

Technology

Stack
Adobe Experience Manager (AEM), jQuery, Google Tag Manager, Adobe Launch (Adobe DTM), YouTube Player API, Qualtrics Site Intercept
Frameworks
Adobe Experience Manager
Platforms
AWS (Amazon Registrar, AWS DNS servers)
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • ClientDeleteProhibited, clientTransferProhibited, clientUpdateProhibited domain statuses
  • No exposed sensitive data in HTML
  • Use of secure cookies in analytics scripts

Analytics and tracking

Services
Google Analytics, Adobe Analytics (via Adobe Launch), Qualtrics
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Google Ad Services
Tracking pixels
Adobe Launch, Qualtrics Site Intercept
Marketing tools
Adobe Experience Platform, Qualtrics
Transparency
good

Site quality

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

Key observations

  1. Website is professionally designed and well maintained.
  2. Content is rich and relevant to healthcare services.
  3. Multiple contact methods are provided including phone and email.
  4. Use of modern analytics and marketing tools.
  5. No signs of malicious or suspicious activity.
  6. Domain registration and hosting are consistent with a reputable organization.
Technical notes

Notes

The website is built on Adobe Experience Manager CMS hosted on AWS infrastructure, utilizing modern JavaScript libraries including jQuery and YouTube Player API. Analytics and marketing are managed through Google Tag Manager, Adobe Launch, and Qualtrics Site Intercept. The site is mobile-optimized with responsive design and accessibility features. Performance is moderate, with potential for optimization in loading times. The technical stack is mature and well-integrated, supporting a professional user experience and scalable content management. Opportunities exist to enhance security headers and enable DNSSEC for improved resilience.
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 stanfordhealthcarenow.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 stanfordhealthcarenow.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.