Skip to main content

Security report for henryschein.com

Henry Schein, Inc. · Healthcare · United States

Partial score · DNS & email only

59/100

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

Henry Schein, Inc. is a well-established global distributor of medical and dental supplies, serving healthcare professionals with a broad portfolio of products and services. The company holds a strong market position as a Fortune 500 enterprise with a history dating back to 1932. Their website reflects a professional and consistent brand image targeting dental and medical professionals, offering solutions ranging from supplies to practice management software and educational resources. Technically, the site is built on a Microsoft IIS and ASP.NET stack, leveraging multiple third-party marketing and analytics tools, with moderate performance and good mobile optimization. However, the SSL certificate is invalid or missing, which significantly impacts the security posture. While security headers and content security policies are implemented, the lack of valid HTTPS and modern TLS protocols is a critical vulnerability. Privacy compliance is basic, with no visible cookie consent mechanism or GDPR indicators, and no public security or incident response policies. Overall, the website is functional and credible but requires urgent improvements in SSL configuration and privacy compliance to enhance trust and security.

Scanned

3 of 7 checks could not complete. The site may be unreachable or blocking automated scans, so the results below cover only what could be checked. Try a rescan later.

NIS2 and GDPR posture

NIS2 outside view
Not assessed
GDPR outside view
Not assessed

Both readouts depend on the site's pages, which could not be loaded in this scan.

Priority findings

1 finding 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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

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

Keep watching henryschein.com

This scan found 5 issues across 4 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
0
Email security
50
DNS health
85
Network security
100
Average
59

Not counted

  • Security headers: did not complete in this scan.
  • GDPR outside view: did not complete in this scan.
  • 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

Henry Schein operates in the healthcare sector as a distributor and service provider, with a diversified portfolio including dental, medical, orthodontics, and specialty markets. The company benefits from a large customer base, extensive supplier partnerships, and a global footprint across 33 countries. Their business model focuses on supplying products and services that improve healthcare practice performance. The presence of subsidiaries like Henry Schein One and Zahn Dental Laboratories indicates a broad ecosystem. The company leverages digital marketing and analytics extensively, indicating a mature digital strategy. Their corporate social responsibility program and investor relations transparency further strengthen their market reputation.

Security posture

The website demonstrates partial adherence to security best practices with several HTTP security headers and a comprehensive content security policy. However, the invalid SSL certificate and absence of TLS protocol support are critical weaknesses that expose users to potential man-in-the-middle attacks and data interception. The lack of OCSP stapling and session resumption further degrade security and performance. No public vulnerability disclosure or incident response information is available, indicating a gap in transparency and readiness. The site uses secure cookie flags appropriately but should improve SSL/TLS configuration urgently to meet modern security standards.

Recommendations

  1. Immediately renew or fix the SSL certificate to enable HTTPS with TLS 1.2 or higher.
  2. Implement a visible cookie consent banner and cookie policy to comply with privacy regulations.
  3. Publish clear terms of service, security policy, and vulnerability disclosure documents.
  4. Enable OCSP stapling and session resumption to improve SSL performance and security.
  5. Regularly audit and tighten the Content Security Policy to reduce unsafe-inline and unsafe-eval usage.
  6. Establish and publicize incident response contact channels and security frameworks adherence.
Technical notes

Notes

The website is hosted on Microsoft IIS 8.0 with ASP.NET Web Forms and Microsoft Commerce Server Enterprise Edition, indicating a legacy but stable enterprise platform. It uses a wide range of third-party services for analytics, marketing, and customer engagement, including Google Analytics, HubSpot, Marketo, LiveChat, and Akamai CDN. The site is mobile optimized with responsive design and uses modern JavaScript libraries like jQuery. Performance is moderate, with some caching disabled via headers. The absence of a valid SSL certificate and disabled TLS protocols represent significant technical debt and risk. The site lacks a common CMS, suggesting a custom or proprietary content management solution. Accessibility and SEO are basic to good, with proper meta tags and structured navigation.
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 henryschein.com. 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 henryschein.com.

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.