Skip to main content

Security report for medtext.eu

MedText · Healthcare · N/a

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

Security score

58/100

Risk levelMedium

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

MedText is a specialized communication platform designed to provide GDPR-compliant messaging solutions for healthcare organizations. The service targets healthcare providers who require secure, efficient, and compliant communication tools to improve patient care coordination. The website presents a professional and consistent brand image, emphasizing compliance certifications and user testimonials to build trust. The business model is subscription-based, focusing on organizational use rather than individual consumers. Technically, the website is built on OctoberCMS and leverages modern web technologies including Google Analytics and Tag Manager for tracking. The site is mobile-optimized and provides a good user experience with clear navigation and professional design. Security is well addressed with HTTPS enforcement and claims of end-to-end encryption, although some security headers are not explicitly detected in the HTML content. Privacy compliance is strong, with a comprehensive privacy policy, cookie consent mechanism, and GDPR-focused messaging. The security posture is solid but could be improved by publishing explicit security policies and incident response contacts. No vulnerabilities or exposed sensitive data were detected in the content. The WHOIS data is privacy protected, which is common and justified for this type of healthcare communication service. Overall, the domain and website appear legitimate and trustworthy. The overall risk is low, with recommendations to enhance security headers, publish incident response information, and consider a vulnerability disclosure policy to further strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

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

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

      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 Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

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

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

Keep watching medtext.eu

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
95
Security headers
15
Email security
90
DNS health
80
Network security
20
GDPR outside view
45
Average
58

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

MedText occupies a niche market in healthcare communication, providing GDPR-compliant messaging tailored for healthcare providers. Its competitive advantage lies in its focus on compliance and ease of use, targeting hospitals, outpatient clinics, and emergency medical services. The subscription-based model suggests recurring revenue streams. The presence of ISO certifications (9001, 27001, 27701) indicates a strong commitment to quality and information security, which is critical in healthcare. The company leverages partnerships with healthcare institutions as evidenced by logos displayed on the site. Growth potential exists in expanding organizational subscriptions and enhancing platform capabilities. The marketing ecosystem includes social media presence on Facebook and LinkedIn, supporting brand awareness and customer engagement.

Security posture

The website demonstrates a mature security posture with HTTPS enforced and GDPR compliance prominently featured. The use of end-to-end encryption for messaging is a key security strength. However, the absence of explicit security headers such as Content Security Policy (CSP), HSTS, and X-Frame-Options reduces the overall security hardening. No incident response or vulnerability disclosure information is publicly available, which could hinder rapid response to security events. The cookie consent mechanism is well implemented, supporting privacy compliance. No exposed sensitive data or vulnerable libraries were detected. Overall, the security posture is good but could be improved with additional security controls and transparency.

Recommendations

  1. Implement and enforce security headers including CSP, HSTS, and X-Frame-Options to enhance protection against common web attacks.
  2. Publish a dedicated security policy and incident response contact information to improve transparency and readiness.
  3. Establish a vulnerability disclosure program or security.txt file to facilitate responsible reporting of security issues.
  4. Regularly audit third-party scripts and tracking tools to minimize privacy risks and ensure compliance.
  5. Enhance accessibility features to improve usability for all users, including those with disabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
MedText
Description
MedText is a GDPR compliant communication platform designed specifically for healthcare organizations to facilitate secure messaging and collaboration among healthcare providers.
Key services
Secure messaging app, Group messaging, Directory search for healthcare professionals, Compliance tools for GDPR
Content quality
good
Branding
consistent

Technology

Stack
Google Analytics, jQuery, Fancybox, FormBuilder plugin
Frameworks
OctoberCMS
Platforms
Web, iOS, Android
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • GDPR compliance
  • End-to-end encryption claims

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

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 focused on GDPR-compliant healthcare communication.
  3. No exposed sensitive data or security misconfigurations detected in HTML content.
  4. WHOIS data is privacy protected with no public registrant info.
  5. Site uses HTTPS with multiple Google Analytics tracking scripts.
  6. Contact is primarily via a detailed contact form; no direct emails or phone numbers publicly listed.
  7. ISO certifications prominently displayed indicating compliance focus.
  8. No security.txt or explicit incident response info found.
  9. Cookie consent mechanism is implemented with detailed cookie categories.
Technical notes

Notes

The website is built on OctoberCMS, a modern PHP-based content management system, indicating a flexible and extensible platform. It uses Google Fonts, Google Analytics, and Google Tag Manager for tracking and styling. The site loads multiple JavaScript libraries including jQuery and Fancybox for UI interactions. Performance is moderate with no major issues detected, and the site is mobile responsive. The presence of a detailed contact form with multiple fields indicates active lead generation and user engagement. No major technical debt or deprecated technologies were observed. Opportunities exist to improve accessibility and implement additional security headers to reduce risk.
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 medtext.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 medtext.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.