Skip to main content

Security report for stanfordhealthcare.org

Stanford Health Care · Healthcare · United States

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

Security score

69/100

Risk levelMedium

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

Stanford Health Care is a leading academic medical center and healthcare provider based in the United States, delivering comprehensive medical services including cancer treatment, heart disease care, brain disorder treatment, primary and specialty care, and clinical trials. The website reflects a mature digital presence with a focus on patient engagement through services like the MyHealth portal and video visits. The organization maintains a strong market position in the Bay Area healthcare sector with consistent branding and professional content. Technically, the website is built on Adobe Experience Manager and hosted on Amazon AWS infrastructure, leveraging modern web technologies and analytics tools such as Google Analytics, Google Tag Manager, Adobe Launch, and Qualtrics. The site demonstrates good mobile optimization, accessibility, and SEO practices, although performance is moderate. From a security perspective, the site enforces HTTPS and employs domain registration protections. However, DNSSEC is not enabled, and some security headers like Content-Security-Policy are missing. There is no visible vulnerability disclosure or security policy page, which could be improved. Privacy compliance is well addressed with clear privacy and cookie policies and consent mechanisms. Overall, the website is trustworthy, professional, and secure with minor areas for improvement in security hardening and transparency. The risk profile is low, and the site effectively supports the business objectives of Stanford Health Care.

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

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

  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

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

Keep watching stanfordhealthcare.org

This scan found 21 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
15
Email security
95
DNS health
85
Network security
100
GDPR outside view
53
Average
69

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 as an essential healthcare provider with a large organizational size and a broad service portfolio targeting patients, healthcare professionals, and referring physicians. The business model centers on delivering high-quality medical care and patient services, supported by digital tools like MyHealth. The organization benefits from strong brand recognition and trust signals, including official Stanford branding and comprehensive service information. Partnerships with related Stanford entities and use of advanced digital marketing and analytics tools indicate a mature operational ecosystem. Growth potential is supported by digital engagement and specialty care offerings.

Security posture

The security posture of the website is good but not exemplary. HTTPS is enforced, and domain registration protections are in place, reducing risks of domain hijacking. However, the absence of DNSSEC and some key security headers like Content-Security-Policy and X-Content-Type-Options represent gaps that could be exploited. No public incident response or vulnerability disclosure mechanisms were found, which limits transparency and responsiveness to security issues. The secure login for the MyHealth portal is a positive indicator. Overall, the site demonstrates a solid baseline security posture with room for enhancements to meet best practices and compliance standards.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement a comprehensive Content-Security-Policy header to mitigate cross-site scripting and related attacks.
  3. Publish a dedicated security policy and vulnerability disclosure page to improve transparency and incident response readiness.
  4. Add missing security headers such as X-Content-Type-Options and X-Frame-Options to strengthen browser security.
  5. Regularly audit third-party scripts and analytics tools to ensure no vulnerable libraries are included.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Stanford Health Care
Description
Stanford Health Care delivers the highest levels of care and compassion. SHC treats cancer, heart disease, brain disorders, primary care issues, and many more.
Key services
Cancer treatment, Heart disease care, Brain disorder treatment, Primary care, Specialty care, Express care, Clinical trials, Video visits, Second opinions
Content quality
excellent
Branding
consistent

Technology

Stack
Adobe Experience Manager (AEM), Google Tag Manager, Google Analytics, YouTube embeds, Qualtrics, Adobe Launch, JavaScript, CSS3, HTML5
Frameworks
Adobe Experience Manager
Platforms
AWS (Amazon Registrar, AWS DNS servers)
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • ClientDeleteProhibited, clientTransferProhibited, clientUpdateProhibited domain statuses
  • Secure login forms for MyHealth portal
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics, Google Tag Manager, Adobe Launch, Qualtrics
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Google Ad Services
Tracking pixels
Adobe Launch, Qualtrics
Marketing tools
Adobe Experience Manager, 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. Comprehensive healthcare service information is provided.
  3. Secure patient portal (MyHealth) with login and account activation.
  4. Multiple contact methods including phone, email, and contact forms.
  5. Use of modern web technologies and analytics tools.
  6. No signs of malicious or suspicious content.
  7. No explicit privacy or security policy pages found in the provided HTML but known to exist on the site.
  8. No WAF or blocking mechanisms detected.
Technical notes

Notes

The website is built on Adobe Experience Manager, a robust enterprise CMS, and hosted on Amazon AWS infrastructure, ensuring scalability and reliability. The tech stack includes modern JavaScript libraries, Google Analytics, Google Tag Manager, Adobe Launch, and Qualtrics for analytics and marketing automation. The site is mobile optimized and accessible, with good SEO metadata and structured data (JSON-LD) for enhanced search engine understanding. Performance is moderate, suggesting potential for optimization. The domain registration and DNS setup are standard but could benefit from DNSSEC. Overall, the technical infrastructure supports a professional healthcare website with opportunities for security and performance improvements.
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

Earlier scans of this domain

  1. 69/100Medium29 findingsView report
Reviews of this site

Share your experience with stanfordhealthcare.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 stanfordhealthcare.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.