Skip to main content

Security report for medme.pl

medme · Healthcare · Poland

Medium risk. 6 critical or high findings in GDPR outside view, Security headers and 1 other check.

Security score

72/100

Risk levelMedium

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

Medme is a Polish online platform specializing in pharmaceutical product reservations with local pharmacy pickup services. The website targets Polish consumers seeking convenient and quick access to medicines without queues. It operates on a Magento e-commerce platform with a modern Hyvä theme, integrating Google Maps API for location-based services and multiple tracking and marketing tools such as Google Tag Manager, GetResponse, and SalesManago. The site demonstrates a good level of digital maturity with responsive design and structured data for SEO. Security posture is solid with HTTPS enforcement and security headers, although explicit privacy and terms of service pages are not found, which impacts compliance confidence. WHOIS data is unavailable from the Polish registry, limiting domain trust assessment. Overall, the site is professional and trustworthy but would benefit from enhanced transparency and compliance documentation.

Scanned

NIS2 and GDPR posture

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

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

      Third-party services without privacy policy

      Detected services: Google Analytics, Google APIs

      What to do: Document all third-party data sharing in your privacy policy

  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 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 medme.pl

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. 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
77
Security headers
70
Email security
80
DNS health
80
Network security
100
GDPR outside view
25
Average
72

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 medme.pl, from OffSeq Breach.

Total records
234
Employees
0
Customers
168
Third parties
66
Weak passwords
24%

6 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 medme.pl.

Select it in the checkout above.

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

Technical appendix

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

Business context

Business profile

Medme holds a significant position in the Polish healthcare e-commerce sector by providing an online reservation system for medicines and pharmacy services. Its business model focuses on bridging consumers with local pharmacies, enhancing convenience and accessibility. The platform leverages partnerships with Google for maps and tracking services and integrates marketing tools to optimize customer engagement. The absence of public WHOIS data is a limitation but does not detract from the evident operational scale and technical sophistication. The company targets a broad consumer base in Poland, emphasizing ease of use and local service availability. Growth potential lies in expanding service offerings and improving compliance transparency.

Security posture

The website employs HTTPS with good SSL configuration and implements key security headers, indicating a mature security posture. The use of cookie consent mechanisms aligns with GDPR requirements, though the lack of a visible privacy policy and terms of service pages suggests gaps in compliance documentation. No vulnerabilities or exposed sensitive data were detected in the HTML content. The integration of multiple third-party scripts necessitates ongoing monitoring to mitigate supply chain risks. Incident response and vulnerability disclosure mechanisms are not evident, which could be improved to enhance security readiness. Overall, the security posture is strong but could benefit from formalized policies and contact channels.

Recommendations

  1. Publish comprehensive privacy policy and terms of service pages accessible from the homepage.
  2. Provide clear contact information including support and security contacts to improve trust and compliance.
  3. Implement a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  4. Enhance accessibility features to meet broader compliance and usability standards.
  5. Regularly audit and update third-party scripts and tracking tools to minimize security risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
medme
Description
Portal rezerwacyjny umożliwiający dokonywanie rezerwacji produktów w wybranej aptece w całej Polsce. Zarezerwuj leki online i odbierz w wybranej aptece. Szybko, wygodnie i bez kolejek.
Key services
Online medicine reservation, Pharmacy location search, Local pharmacy pickup
Content quality
good
Branding
consistent

Technology

Stack
Google Tag Manager, Google Maps API, Magento (e-commerce platform), RequireJS, Alpine.js, New Relic Browser monitoring, GetResponse tracking
Frameworks
Magento Hyvä theme
Platforms
Magento Commerce
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner with consent management
  • Use of security headers
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Tag Manager, New Relic Browser, GetResponse
Tracking level
extensive
Privacy practices
basic

Advertising

Tracking pixels
New Relic, GetResponse, SalesManago
Marketing tools
GetResponse, SalesManago
Transparency
basic

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. Content is in Polish language targeting Polish users.
  3. No explicit privacy policy or terms of service pages found in the HTML content.
  4. Cookie consent mechanism is implemented with third-party consent management.
  5. No explicit contact emails or phone numbers found in the HTML content.
  6. Uses Magento e-commerce platform with Hyvä theme.
  7. Integrates Google Maps API for pharmacy location services.
  8. Extensive use of JavaScript for tracking and user interaction.
  9. No adult or NSFW content detected.
  10. WHOIS data is missing or not publicly available from the Polish registry.
Technical notes

Notes

The website is built on Magento with the Hyvä theme, indicating a modern and performant e-commerce infrastructure. It uses RequireJS for module loading, Alpine.js for reactive components, and integrates Google Maps API for location services. Tracking and analytics are implemented via Google Tag Manager, New Relic Browser monitoring, and GetResponse, reflecting a mature digital marketing setup. The site is mobile-optimized with responsive design and includes structured data for SEO. Performance is moderate, with potential improvements in script loading and accessibility. Hosting details are not explicit, but the use of CDN-hosted static assets suggests a distributed content delivery approach. Overall, the technical stack is robust and well-suited for the business model.
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 medme.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 medme.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.