Skip to main content

Security report for pint-pharma.com.br

Pint-Pharma · Healthcare · Brazil

High risk. 8 critical or high findings in Network security, Security headers and 1 other check.

Security score

40/100

Risk levelHigh

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

Pint-Pharma is a pharmaceutical company focused on serving patients with rare diseases in Latin America, particularly Brazil. The company emphasizes a community-centric approach and participates in public health consultations, aiming to become a leader in its specialized market segment. The website reflects this positioning with content in Portuguese and links to relevant public health consultation pages. Technically, the site is built on WordPress with Elementor and hosted on a LiteSpeed server. While the site is accessible and well-structured with good design and navigation, there are notable security shortcomings, including the absence of modern TLS protocols and lack of HSTS enforcement. The SSL certificate is valid but the overall SSL/TLS configuration is weak. Privacy compliance is partial, with a cookie consent mechanism present but no visible privacy policy or terms of service. Contact information is limited to a contact form without direct emails or phone numbers. Overall, the site demonstrates moderate digital maturity but requires improvements in security and privacy compliance to enhance trust and protect users.

Scanned

NIS2 and GDPR posture

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

8 findings rated critical or high. Fix these first.

  1. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

  2. 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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';…

  3. GDPR outside view

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

    • 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

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

Keep watching pint-pharma.com.br

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

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 · found on this site
  • 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 company targets the healthcare sector with a focus on rare diseases, positioning itself as a specialized pharmaceutical provider in Latin America. Its business model includes product offerings and community engagement, leveraging public consultations to influence healthcare decisions. The website content and structure support this model, highlighting community-centric values and career opportunities. The lack of direct contact details and limited transparency on privacy and security policies may impact user trust. The company appears medium-sized with consistent branding and a clear market focus. Partnerships with government health agencies are implied through links to official public consultation sites.

Security posture

The website uses HTTPS with a valid SSL certificate but lacks support for modern TLS versions, which is a critical security gap. No HSTS header is present to enforce HTTPS, and OCSP stapling is disabled, reducing certificate revocation efficiency. Session resumption features are also disabled, potentially impacting performance and security. No security.txt or vulnerability disclosure policies are found, and no incident response contacts are provided. The cookie consent mechanism is implemented, indicating some privacy awareness. Overall, the security posture is basic and requires significant enhancements to meet best practices and compliance standards.

Recommendations

  1. Enable TLS 1.2 or TLS 1.3 protocols to secure communications effectively.
  2. Implement HSTS with includeSubDomains and preload to enforce HTTPS usage.
  3. Enable OCSP stapling to improve SSL certificate revocation checking.
  4. Publish a comprehensive privacy policy and terms of service to improve compliance and user trust.
  5. Provide direct contact information including emails and phone numbers for support and incident response.
  6. Consider adding a security.txt file and vulnerability disclosure policy to encourage responsible reporting.
  7. Improve accessibility features and SEO optimization for better user experience and discoverability.
  8. Regularly audit and update plugins and technologies to avoid vulnerabilities.
Technical notes

Notes

The website is built on WordPress 6.8.1 with Elementor page builder and several plugins including Complianz GDPR Cookie Consent and Beam Me Up Scotty. It runs on PHP 7.4.33 and is served by a LiteSpeed server. The site uses jQuery and other standard WordPress scripts. Performance data is unavailable, but the presence of caching (LiteSpeed Cache hit) suggests some optimization. Mobile optimization appears good based on responsive design elements. However, the SSL/TLS configuration is outdated with no modern TLS protocols enabled, which is a significant technical risk. The site lacks advanced security headers and session management features. No structured data (JSON-LD) or Open Graph metadata was found in the HTML content, limiting SEO and social media integration potential.
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 pint-pharma.com.br. 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 pint-pharma.com.br.

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.