Skip to main content

Security report for healthtrio.com

mPulse · Healthcare · United States

Medium risk. 4 critical or high findings in GDPR outside view and SSL/TLS.

Security score

73/100

Risk levelMedium

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

mPulse is a well-established company founded in 1998, specializing in digital health engagement solutions. Their product suite includes predictive analytics, omnichannel engagement, health portals, content management, acquisition and payments, and a HITRUST-certified Health Experience and Insights Platform (HXI). The company targets healthcare organizations such as health plans, providers, and related stakeholders, positioning itself as a leader in the healthcare technology sector. The website demonstrates professional design, clear navigation, and strong branding consistency, reflecting a mature digital presence. Technically, the website is built on WordPress using Elementor as the page builder, with integrations including jQuery, HubSpot Analytics, Google Tag Manager, and Warmly widgets. Hosting appears to be on Amazon AWS infrastructure. The site shows good mobile optimization and SEO practices, though accessibility features are basic. Performance is moderate, with room for improvement in loading speed and accessibility. From a security perspective, the site uses HTTPS with a good SSL configuration and domain registration protections. However, DNSSEC is not enabled, and no security headers were detected in the provided data. There is no publicly available security policy, incident response contact, or vulnerability disclosure information, which are areas for improvement. No critical vulnerabilities or exposed sensitive data were found. Overall, the website and business present a low-risk profile with strong business credibility and technical maturity. Strategic recommendations include enabling DNSSEC, publishing privacy and cookie policies with consent mechanisms, adding security and incident response information, and implementing security headers to enhance protection and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
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

4 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.

    • 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

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  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.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching healthtrio.com

This scan found 21 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
52
Security headers
80
Email security
75
DNS health
80
Network security
100
GDPR outside view
53
Average
73

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

mPulse operates in the healthcare technology sector, focusing on digital health engagement and analytics solutions. Their business model is B2B SaaS and services, targeting health plans, providers, and healthcare organizations. The company leverages advanced predictive analytics and omnichannel engagement to improve health outcomes and business impact. Market positioning is strong with a HITRUST-certified platform and a broad product suite. The presence of client logos from leading healthcare organizations indicates a solid partnership ecosystem. Growth indicators include recent acquisitions and active content marketing. The company maintains a professional online presence with consistent branding and comprehensive product offerings.

Security posture

The security posture of mPulse's website is moderate to good. HTTPS is enforced with a valid SSL certificate, and domain registration includes protective status flags. However, DNSSEC is not enabled, which could improve DNS security. No security headers such as Content Security Policy or HSTS were detected, representing a potential area of vulnerability. The absence of published security policies, incident response contacts, or vulnerability disclosure mechanisms limits transparency and readiness perception. No exposed sensitive data or vulnerable libraries were identified. Overall, the site follows basic security best practices but would benefit from enhanced security controls and published policies to improve trust and compliance.

Recommendations

  1. Enable DNSSEC to strengthen DNS security and prevent spoofing.
  2. Publish comprehensive privacy and cookie policies including GDPR compliance details and implement a cookie consent mechanism.
  3. Add security headers such as Content Security Policy, HSTS, X-Frame-Options, and X-Content-Type-Options to improve browser security.
  4. Create and publish a security policy and incident response contact information to enhance transparency and readiness.
  5. Implement a vulnerability disclosure policy or security.txt file to facilitate responsible reporting of security issues.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
mPulse
Description
mPulse provides health experience and insights products that create consumer-centric journeys for better health outcomes and business impact.
Key services
Predictive Analytics, Omnichannel Engagement, Health Portals, Content Hub, Acquisition & Payments, Health Experience and Insights Platform (HXI)
Content quality
excellent
Branding
consistent

Technology

Stack
jQuery, Elementor, WordPress, Yoast SEO, Google Tag Manager, HubSpot Analytics, Warmly Widget, Swiper.js
Frameworks
Elementor (WordPress page builder)
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Domain status includes clientDeleteProhibited, clientRenewProhibited, clientTransferProhibited, clientUpdateProhibited

Analytics and tracking

Services
HubSpot Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
HubSpot Analytics
Marketing tools
HubSpot, Warmly
Transparency
basic

Site quality

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

Key observations

  1. Website is professionally designed and well-structured
  2. Content is focused on healthcare digital engagement solutions
  3. No direct contact emails or phone numbers found on the homepage HTML
  4. No explicit privacy, cookie, or terms of service pages detected in the provided content
  5. Use of modern web technologies and SEO best practices
  6. No security.txt or vulnerability disclosure information found
  7. No explicit security or incident response policies published on the site
  8. Strong branding and consistent messaging
  9. Presence of client logos and case studies indicating trustworthiness
Technical notes

Notes

The website is built on WordPress CMS with Elementor page builder, leveraging modern JavaScript libraries such as jQuery and Swiper.js for UI components. It integrates marketing and analytics tools including HubSpot Analytics and Google Tag Manager. Hosting is via Amazon AWS DNS infrastructure, indicating reliable cloud hosting. The site is mobile optimized and uses SEO best practices including structured data (JSON-LD) and Open Graph tags. Performance is moderate, with some lazy loading and preloading optimizations. Accessibility features are basic but present. Technical risks include lack of DNSSEC and missing security headers, which could be addressed to reduce attack surface and improve compliance.
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 healthtrio.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 healthtrio.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.