Skip to main content

Security report for pfizer.com

Pfizer · Healthcare · United States

Medium risk. 7 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

51/100

Risk levelMedium

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

Pfizer is a globally recognized pharmaceutical company specializing in healthcare products and medicines. The company operates at an enterprise scale within the healthcare sector, targeting healthcare professionals, patients, investors, and partners. The website is intended to provide information about Pfizer's pharmaceutical products, vaccines, and research and development efforts. However, the current website content is inaccessible due to a Cloudflare security challenge, preventing a full content and user experience assessment. From a technical perspective, the website is protected by Cloudflare, which provides security and performance services. However, the SSL/TLS configuration is critically lacking, with no valid certificate detected and no modern TLS protocols enabled. This severely impacts the security posture and trustworthiness of the site. Security headers are present and configured with best practices such as X-Frame-Options and Content-Type options, but these cannot compensate for the absence of HTTPS. The security posture is weak due to the lack of HTTPS and the presence of a Cloudflare WAF challenge page blocking content access. No privacy, cookie, or terms of service policies are detectable in the provided HTML content, and no contact information or forms are visible. The domain WHOIS data aligns well with Pfizer's brand and business, indicating high legitimacy and trustworthiness. Overall, the website's current state limits the ability to perform a comprehensive analysis, and the security and privacy compliance scores are low. Strategic recommendations include immediate installation and maintenance of a valid SSL/TLS certificate, enabling HSTS, and improving privacy and cookie policy transparency. Additionally, reducing or customizing the WAF challenge to allow legitimate user access would improve user experience and content accessibility.

Scanned

This is an earlier scan of pfizer.com. View the latest report

NIS2 and GDPR posture

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

7 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

  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

  3. 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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • 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';…

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

Keep watching pfizer.com

This scan found 14 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
0
Security headers
55
Email security
50
DNS health
85
Network security
100
GDPR outside view
15
Average
51

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 pfizer.com, from OffSeq Breach.

Total records
19,705
Employees
46
Customers
4,486
Third parties
15,173
Weak passwords
6%

Latest record dated 2026-06-06 · 211 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 pfizer.com.

Select it in the checkout above.

Masked preview

  • –prodfederate.pfizer.com2026-06-06
  • –prodfederate.pfizer.com2026-06-05
  • –sendfile.pfizer.com2026-05-30
  • –logonv0dmz.pfizer.com2026-05-26
  • –logonsso.pfizer.com2026-05-25

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Pfizer holds a leading position in the global pharmaceutical market, focusing on research, development, manufacturing, and distribution of healthcare products and vaccines. The company targets a broad audience including healthcare professionals, patients, and investors. Its business model is centered on innovation in pharmaceuticals and vaccines, supported by a strong global presence. The domain registration data supports the company's legitimacy and long-standing market presence. However, the website's current technical and content limitations restrict digital engagement and may impact customer trust and information dissemination. There is no evidence of partnerships or subsidiaries from the provided data, and no direct revenue stream insights are available from the website content.

Security posture

The website's security maturity is low due to the absence of a valid SSL/TLS certificate and lack of HTTPS enforcement. While security headers are implemented, critical vulnerabilities exist such as no HSTS, no OCSP stapling, and no session resumption. The Cloudflare WAF challenge indicates an active security control but also blocks content access, which may hinder legitimate user interactions. There is no visible incident response or vulnerability disclosure information, and no data protection officer contact details are found. Compliance with GDPR or other privacy regulations cannot be confirmed due to missing policies. Overall, the security posture requires urgent improvements to meet industry standards and user expectations.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate supporting TLS 1.2 or 1.3 to secure all website traffic.
  2. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives to enforce HTTPS.
  3. Publish clear and comprehensive privacy and cookie policies with consent mechanisms to improve compliance.
  4. Provide visible contact information including security incident response contacts to enhance trust and transparency.
  5. Review and optimize WAF challenge settings to balance security with user accessibility and experience.
Technical notes

Notes

The website is hosted behind Cloudflare, which provides CDN and security services. The absence of a valid SSL certificate and disabled TLS protocols represent critical technical debt and security risk. The HTML content is minimal and serves only as a Cloudflare challenge page requiring JavaScript and cookies, indicating restricted access to the actual website content. No CMS or frameworks are detectable from the provided data. Performance metrics are unavailable due to blocked content. The presence of Cloudflare Insights indicates some level of analytics tracking. The technical infrastructure requires modernization and proper security configuration to support business operations effectively.
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

Earlier scans of this domain

  1. 69/100Medium28 findingsView report
Reviews of this site

Share your experience with pfizer.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 pfizer.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.