Skip to main content

Security report for medline.eu

Medline · Healthcare · N/a

Low risk. 2 critical or high findings in Security headers and SSL/TLS.

Security score

81/100

Risk levelLow

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

Medline Europe operates as a significant healthcare supplier supporting clinicians, patients, and communities. The website presents a professional and consistent brand image with a focus on medical supplies and healthcare services. The company targets healthcare professionals and institutions across Europe, positioning itself as a trusted business partner in the healthcare sector. The digital presence is built on a Magento e-commerce platform, leveraging modern web technologies and third-party services such as Algolia for search and Cookiebot for privacy compliance. The technical infrastructure is mature, with good mobile optimization and SEO practices, although some improvements in accessibility and security headers could enhance the overall quality. Security posture is strong with HTTPS enforced and cookie consent implemented, but lacks explicit security policies and incident response information. Overall, the website is trustworthy and professionally maintained, though WHOIS data is privacy protected, limiting domain age and registrant verification.

Scanned

NIS2 and GDPR posture

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

2 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 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 medline.eu

This scan found 15 issues across 5 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
65
Security headers
75
Email security
60
DNS health
85
Network security
100
GDPR outside view
100
Average
81

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

Medline's market positioning as a healthcare supplier is supported by a comprehensive website targeting European healthcare providers. The business model appears to be a mix of B2B and B2C, focusing on medical supplies and healthcare support services. The company leverages partnerships with technology providers for search and analytics, indicating a strategic approach to digital marketing and customer engagement. The absence of explicit contact information and privacy policies on the main page suggests potential areas for improvement in transparency. The use of privacy protection in WHOIS is typical for large enterprises to protect corporate data. The company likely operates at a large scale given the technology stack and content quality.

Security posture

The website enforces HTTPS and uses a cookie consent mechanism compliant with GDPR standards, indicating a good baseline for privacy and security. However, the lack of visible security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options reduces the overall security posture. No vulnerabilities or exposed sensitive data were detected in the provided content. The absence of a published security policy, incident response contacts, or vulnerability disclosure program limits transparency and readiness for security incidents. Recommendations include adding these policies and improving header configurations to enhance security maturity.

Recommendations

  1. Implement and publish a comprehensive privacy policy and terms of service to improve transparency and compliance.
  2. Add explicit security headers (CSP, HSTS, X-Frame-Options) to strengthen web security.
  3. Publish a security policy and incident response contact information to demonstrate readiness and build trust.
  4. Establish a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  5. Enhance accessibility features to improve compliance with accessibility standards and user experience.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Medline
Description
Medline is more than your business partner. We support clinicians, patients and communities at large.
Key services
Medical supplies, Healthcare support services
Content quality
good
Branding
consistent

Technology

Stack
Magento, jQuery, RequireJS, Algolia Search, Amasty extensions, Google Tag Manager, Cookiebot
Frameworks
Magento Commerce
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner implemented
  • Google Tag Manager for analytics

Analytics and tracking

Services
Google Analytics, Mouseflow
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Mouseflow
Marketing tools
Cookiebot
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 challenges
  2. WHOIS data is unavailable or privacy protected, limiting domain age and registrant verification
  3. Cookie consent mechanism is implemented with Cookiebot
  4. No explicit privacy policy or terms of service pages detected in the provided content
  5. No contact emails or phone numbers explicitly found in the HTML content provided
  6. Website uses Magento CMS with multiple modern JavaScript libraries and tracking tools
  7. Security headers are not explicitly visible in the provided data; recommend adding
  8. No visible security.txt or vulnerability disclosure policy
  9. Good SEO and mobile optimization observed
  10. No social media links explicitly found in the provided HTML snippet
Technical notes

Notes

The website is built on Magento CMS with extensive use of JavaScript libraries including jQuery, RequireJS, and Algolia Search for enhanced user experience. The hosting infrastructure includes Azure Blob Storage for web tracking scripts, indicating a cloud-based deployment. Performance is moderate with good mobile responsiveness and SEO optimization. The site uses Google Tag Manager and Mouseflow for analytics and user behavior tracking, integrated with Cookiebot for consent management. Technical debt appears low, but improvements in accessibility and security headers are recommended to modernize and secure the platform further.
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 medline.eu. 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 medline.eu.

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.