Skip to main content

Security report for lilly.pl

Eli Lilly and Company · Healthcare · Poland

Low risk. 2 critical or high findings in Security headers and DNS health.

Security score

82/100

Risk levelLow

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

Eli Lilly and Company operates the localized Polish website www.lilly.com/pl to provide information about its pharmaceutical products, therapeutic areas, and corporate responsibility. The site targets healthcare professionals and patients in Poland, offering detailed content about the company's values, products, and safety information. The website demonstrates a mature digital infrastructure using modern JavaScript frameworks and includes comprehensive privacy and cookie consent mechanisms, reflecting compliance with GDPR and local regulations. Security posture is good with HTTPS and consent management, though explicit security policies and incident response information are not publicly detailed. Overall, the site is professional, trustworthy, and well-maintained, supporting Eli Lilly's market position as a leading pharmaceutical enterprise.

Scanned

NIS2 and GDPR posture

GDPR outside view
88/ 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. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • High

      Weak SPF Policy

      SPF record has permissive policy allowing any server to send email

      What to do: Use -all or ~all qualifier for better email security

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

Keep watching lilly.pl

This scan found 15 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
90
Security headers
65
Email security
80
DNS health
70
Network security
100
GDPR outside view
88
Average
82

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

The website reflects Eli Lilly's strong market presence in the healthcare sector, focusing on pharmaceutical manufacturing and distribution. The content emphasizes therapeutic areas such as diabetes, oncology, and autoimmune diseases, aligning with the company's global portfolio. The business model is B2B and B2C, targeting healthcare providers and patients. The site integrates marketing and tracking tools like Google Tag Manager and Facebook Pixel, indicating active digital marketing strategies. The absence of direct contact emails or phone numbers suggests a preference for controlled communication channels via contact forms. The company maintains consistent branding and legal compliance, reinforcing its credibility and regulatory adherence in Poland.

Security posture

The website enforces HTTPS and implements a robust cookie consent mechanism with opt-in/out options, demonstrating awareness of privacy regulations. However, no explicit security headers were detected in the provided data, and no dedicated security or incident response pages were found. The use of third-party scripts and tracking pixels introduces potential privacy risks, mitigated by user consent. The lack of a security.txt file or vulnerability disclosure policy limits transparency for security researchers. Overall, the security posture is solid but could be enhanced by publishing detailed security policies and implementing additional HTTP security headers.

Recommendations

  1. Implement and publish a dedicated security policy and incident response page to improve transparency.
  2. Add and enforce HTTP security headers such as Content-Security-Policy, Strict-Transport-Security, and X-Frame-Options.
  3. Publish a security.txt file to facilitate responsible vulnerability disclosure.
  4. Regularly audit third-party scripts and tracking technologies to minimize privacy risks.
  5. Enhance contact information availability for security and privacy inquiries.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Eli Lilly and Company
Description
Firma Lilly łączy troskę z innowacyjnością, tworząc leki, które poprawiają życie ludziom na całym świecie.
Key services
pharmaceutical products, medical devices, therapeutic area research
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, Nuxt.js, Google Tag Manager, Syrenis Cookie Consent, SVG graphics
Frameworks
Nuxt.js
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced (implied by URL)
  • Cookie consent with opt-in/out
  • Privacy policy compliance

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Facebook Pixel
Marketing tools
Syrenis Cookie Consent
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with rich content in Polish language.
  2. Strong corporate branding consistent with Eli Lilly and Company.
  3. Comprehensive cookie consent and privacy policy mechanisms implemented.
  4. No direct email addresses or phone numbers found; contact via contact form.
  5. No security.txt or explicit security policy pages found.
  6. No WHOIS data available for the exact queried domain string; likely query mismatch.
  7. Use of modern JavaScript frameworks and tracking technologies.
  8. No signs of adult or questionable content.
  9. No WAF or blocking mechanisms detected.
Technical notes

Notes

The website uses Nuxt.js, a modern Vue.js framework, indicating a contemporary front-end architecture. It leverages Google Tag Manager for analytics and Syrenis for cookie consent management, reflecting compliance with privacy laws. The site loads multiple JavaScript bundles and uses SVG for logos and icons, supporting responsive and accessible design. Performance is moderate, with preloading of critical assets. Accessibility features such as skip links and ARIA attributes are present, enhancing usability. SEO is supported by meta tags and alternate hreflang links for internationalization. Hosting details are not explicit, but the use of CDN domains suggests a distributed content delivery approach. Overall, the technical implementation is modern and well-structured.
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 lilly.pl. 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 lilly.pl.

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.