Skip to main content

Security report for pennstatehealth.org

Penn State Health · Healthcare · United States

Medium risk. 3 critical or high findings in Security headers and SSL/TLS.

Security score

75/100

Risk levelMedium

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

Penn State Health is a large, multi-hospital healthcare system serving central Pennsylvania, providing comprehensive medical services to patients and communities. The website reflects a professional healthcare provider with clear branding and a focus on patient care. The organization leverages modern web technologies including Drupal 10 CMS and integrates multiple analytics and marketing tools to optimize user experience and outreach. The presence of structured data and official social media links enhances credibility and discoverability. Technically, the website is built on a mature and scalable platform with good mobile optimization and accessibility features. Performance is moderate, supported by CDN and third-party services. Security posture is strong with HTTPS enforced and cookie consent mechanisms in place, although explicit security headers and published security policies are absent. No critical vulnerabilities or exposed sensitive data were detected in the analyzed content. The WHOIS data is unavailable due to query failure or privacy protection, which is common for healthcare entities to safeguard registrant information. Despite this, the website's content, branding, and external references strongly indicate legitimacy. Privacy compliance is well addressed with a comprehensive cookie consent banner and GDPR-related mechanisms. Overall, the website presents a trustworthy and professional digital presence for Penn State Health, with recommendations to enhance security transparency and incident response readiness to further strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

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

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

This scan found 20 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
47
Security headers
55
Email security
70
DNS health
80
Network security
100
GDPR outside view
95
Average
75

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 pennstatehealth.org, from OffSeq Breach.

Total records
66
Employees
0
Customers
66
Third parties
0
Weak passwords
3%

6 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 pennstatehealth.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

Penn State Health occupies a significant position in the regional healthcare market as a multi-hospital system serving central Pennsylvania. Its business model focuses on providing hospital and medical services to a broad patient base. The organization benefits from strong brand recognition associated with Penn State University and leverages partnerships and social media channels to engage its audience. Revenue streams likely include patient care services, insurance reimbursements, and community health programs. The website's integration of analytics and marketing tools suggests a data-driven approach to patient engagement and outreach. Growth indicators include digital maturity and consistent branding. No direct parent or subsidiary companies were identified from the website content.

Security posture

The website demonstrates a mature security posture with mandatory HTTPS and a robust cookie consent mechanism ensuring user privacy and compliance with GDPR. However, the absence of explicit security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options represents an area for improvement. No security policy or incident response contact information is publicly available, which could hinder rapid response to security incidents. The use of multiple third-party analytics and marketing services is transparent, but continuous monitoring for vulnerabilities in these integrations is recommended. Overall, the security posture is strong but could benefit from enhanced transparency and formalized security documentation.

Recommendations

  1. Implement and publish comprehensive security headers including CSP, HSTS, and X-Frame-Options to enhance protection against common web attacks.
  2. Develop and make publicly available a security policy and incident response plan with clear contact channels to improve transparency and readiness.
  3. Establish a vulnerability disclosure program or security.txt file to encourage responsible reporting of security issues.
  4. Regularly audit third-party scripts and analytics tools to ensure they do not introduce vulnerabilities or privacy risks.
  5. Enhance privacy policy visibility and detail to cover all data processing activities and retention policies comprehensively.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Penn State Health
Description
Penn State Health is a multi-hospital health system serving patients and communities across central Pennsylvania.
Key services
Hospital care, Medical services, Patient care
Content quality
good
Branding
consistent

Technology

Stack
PHP SDK 1.5.12, Drupal 10 CMS, Bootstrap 3.3.7, Google Tag Manager, Cookiebot, Monsido heatmaps, Invoca, Piwik Pro analytics, Modal Video
Frameworks
Drupal
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Piwik Pro, Monsido, Google Analytics (implied via tags)
Tracking level
extensive
Privacy practices
good

Advertising

Ad networks
Google DoubleClick, Meta Platforms, Inc., Adobe Inc.
Tracking pixels
Cookiebot, Monsido, Invoca, Piwik Pro
Marketing tools
Google AdSense, Facebook Ads
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenge
  2. Content is professionally presented and relevant to healthcare
  3. Strong cookie consent and privacy mechanisms implemented
  4. WHOIS data unavailable, likely due to privacy protection or query error
  5. Multiple analytics and marketing tools used with transparency
  6. No security policy or incident response info publicly available
  7. No vulnerability disclosure or security.txt found
  8. No explicit contact emails found in HTML content
  9. Phone and address found in structured data only
  10. Mobile and accessibility features are well implemented
Technical notes

Notes

The website is built on Drupal 10 CMS, leveraging PHP SDK and Bootstrap for responsive design. It integrates multiple third-party services including Cookiebot for consent management, Monsido for heatmaps, Invoca for call tracking, and Piwik Pro for analytics. The site uses modern web standards and is mobile optimized with good accessibility features. Performance is moderate, with some reliance on external CDNs and scripts. The technical stack is well maintained but could benefit from performance tuning and security header enhancements. No deprecated or vulnerable libraries were detected in the provided content.
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 pennstatehealth.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 pennstatehealth.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.