Skip to main content

Security report for stryker.com

Stryker · Healthcare · United States

Medium risk. 6 critical or high findings in GDPR outside view and SSL/TLS.

Security score

55/100

Risk levelMedium

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

Stryker is a large multinational healthcare company specializing in medical devices and healthcare solutions, serving a global audience including healthcare professionals and patients. The website serves as an international homepage with localized country sites, reflecting a broad global presence. Technically, the site is built on Adobe Experience Manager and hosted via AWS CloudFront, utilizing various marketing and analytics technologies such as Adobe DTM, Google Analytics, and Marketo. However, the website lacks a valid SSL certificate and does not serve content over HTTPS, which is a critical security deficiency. Security headers are implemented but cannot compensate for the absence of HTTPS. Privacy and cookie policies are not found, and no explicit contact information is provided on the homepage, which impacts privacy compliance and user trust. Overall, the site demonstrates moderate business credibility but requires urgent improvements in security and privacy compliance to meet modern standards.

Scanned

NIS2 and GDPR posture

GDPR outside view
0/ 100 · Critical
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. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

  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.

    • 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 stryker.com

This scan found 12 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. The full timeline opens with your unlock code.

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
Security headers
95
Email security
50
DNS health
85
Network security
100
GDPR outside view
0
Average
55

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

Stryker operates in the healthcare sector with a strong global footprint, offering medical technologies and services. The business model targets both healthcare providers and patients, leveraging a network of localized country sites to cater to diverse markets. The company uses advanced marketing and analytics tools to engage users and optimize digital presence. The lack of visible contact information and privacy policies on the homepage suggests these may be located deeper within the site or managed through other channels. The domain registration data aligns well with the company's identity, supporting legitimacy and trustworthiness. The company appears to maintain consistent branding and a professional digital presence, though content quality on the homepage is basic.

Security posture

The website's security posture is weak due to the absence of a valid SSL certificate and lack of HTTPS support, exposing users to potential interception risks. While security headers such as CSP, HSTS (disabled), X-Frame-Options, and X-XSS-Protection are present, they are insufficient without HTTPS. No vulnerabilities like Heartbleed or POODLE were detected, but the lack of modern TLS protocols and OCSP stapling further degrade security. No incident response or security policy information is found, and no vulnerability disclosure or security.txt files are present. The extensive use of third-party marketing and tracking scripts increases the attack surface and privacy risks. Immediate remediation of SSL/TLS configuration and publication of privacy and security policies are recommended.

Recommendations

  1. Install and configure a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable and enforce modern TLS protocols (TLS 1.2 or TLS 1.3) and OCSP stapling for improved security and performance.
  3. Publish comprehensive privacy and cookie policies with clear GDPR compliance statements.
  4. Provide clear contact information including security incident response contacts.
  5. Review and tighten Content Security Policy to remove unsafe-inline and unsafe-eval directives.
  6. Implement a security.txt file and vulnerability disclosure policy to enhance transparency.
  7. Audit third-party scripts to minimize privacy risks and improve user trust.
  8. Enhance website accessibility and SEO optimizations for better user experience.
  9. Improve content quality and navigation clarity to support user engagement.
  10. Regularly review and update security headers and compliance documentation.
Technical notes

Notes

The website is built on Adobe Experience Manager, leveraging Apache server and hosted on AWS CloudFront CDN. It uses jQuery and Adobe Helix RUM for performance monitoring, along with Google Tag Manager and Google Charts for analytics and visualization. The site employs a complex Content Security Policy allowing multiple trusted domains for scripts, images, and media. However, the SSL/TLS configuration is missing, with no TLS protocols enabled, which is a critical technical flaw. Performance data is unavailable, but the use of CDN and modern analytics suggests moderate technical maturity. The site is mobile responsive at a basic level and includes some accessibility features. SEO metadata is minimal, with no privacy or terms of service metadata detected. Overall, the technical stack is modern but undermined by the lack of HTTPS and incomplete privacy compliance.
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 stryker.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 stryker.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.