Skip to main content

Security report for medscinet.com

Omda · Healthcare · Norway

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

Security score

60/100

Risk levelMedium

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

Omda is a healthcare technology company specializing in secure, standardized software solutions for clinical research and medical data analytics. Their offerings include comprehensive platforms for clinical trials, quality registries, biobank management, patient-reported outcome measurements, and healthcare intelligence. The company targets clinical researchers, healthcare professionals, and academic institutions, positioning itself as a key player in health analytics software with a medium-sized presence and a foundation dating back to 1999. Technically, the website is built on WordPress with a modern tech stack including jQuery, SEO plugins, and cookie consent management. The site is well-structured, mobile-optimized, and uses HTTPS with moderate performance. However, some security best practices such as security headers and explicit security policies are missing. From a security perspective, the site benefits from HTTPS and cookie consent but lacks published security policies, incident response contacts, and advanced security headers. The domain is long-established and registered through a reputable registrar, indicating legitimacy. No WAF or blocking mechanisms were detected. Overall, Omda's website demonstrates good professionalism and technical maturity but would benefit from enhanced privacy and security disclosures to improve compliance and trust. Strategic recommendations include publishing privacy and security policies, adding security headers, and providing clear contact information for incident response.

Scanned

NIS2 and GDPR posture

GDPR outside view
80/ 100 · Low
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. 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';…

  2. GDPR outside view

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

    • 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

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

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

Keep watching medscinet.com

This scan found 22 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
15
Email security
85
DNS health
80
Network security
20
GDPR outside view
80
Average
60

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

Omda operates in the healthcare technology sector, providing specialized software solutions for clinical research and health data analytics. Their business model focuses on B2B engagements with healthcare organizations, research institutions, and academia. The company leverages a portfolio of products addressing clinical trials, registries, biobanks, and patient outcome measurements, supporting regulatory compliance and data-driven decision making. Market positioning is strengthened by comprehensive service offerings and downloadable product literature. The company appears medium-sized with a stable foundation since 1999 and consistent branding. Partnerships or subsidiaries were not explicitly identified in the analyzed content.

Security posture

The website's security posture is moderate. HTTPS is enforced, and cookie consent is implemented, indicating attention to basic privacy requirements. However, the absence of security headers such as Content-Security-Policy and lack of published security or incident response policies represent gaps. No vulnerabilities or exposed sensitive data were detected in the content. The WHOIS data shows a stable domain registration without privacy protection, supporting legitimacy. To improve security maturity, Omda should publish security policies, implement recommended HTTP headers, and provide incident response contacts.

Recommendations

  1. Publish a comprehensive privacy policy and terms of service pages accessible from the website footer or main navigation.
  2. Implement and publish a dedicated security policy outlining security practices and incident response procedures.
  3. Add HTTP security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection.
  4. Provide clear contact information including company emails and phone numbers for general and security-related inquiries.
  5. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Omda
Description
Omda provides secure standardized software solutions for clinical researchers and medical professionals to gather, manage, and analyze medical data, enabling innovations in medical practice and scientific knowledge.
Key services
Omda Research - clinical trials and study management, Omda Health Intelligence - healthcare data insights and decision support, Quality registries management, Biobank management, Patient-reported outcome measurements, Process and outcome improvement, Post-market surveillance
Content quality
good
Branding
consistent

Technology

Stack
WordPress 6.7.2, jQuery 3.7.1, jQuery UI, Events Manager plugin, Dash Effortless Digital Asset Management plugin, GeneratePress theme and child theme, Rank Math SEO plugin, CookieYes consent management
Frameworks
WordPress
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Cookie consent mechanism implemented

Analytics and tracking

Services
Fathom Analytics
Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
Fathom Analytics
Marketing tools
Rank Math SEO, CookieYes
Transparency
basic

Site quality

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

Key observations

  1. Website is professionally designed and content-rich focused on health analytics software
  2. No explicit privacy policy or terms of service pages found on the analyzed page
  3. Cookie consent mechanism is implemented via CookieYes
  4. No direct contact emails or phone numbers found on this page
  5. Uses WordPress CMS with common plugins and modern SEO practices
  6. No security headers detected in provided data; SSL is enabled
  7. WHOIS data shows domain is old and stable with no privacy protection
  8. No signs of WAF or content blocking
Technical notes

Notes

The website is built on WordPress 6.7.2 with a child theme of GeneratePress, utilizing jQuery and jQuery UI libraries. Plugins include Events Manager, Dash Effortless Digital Asset Management, Rank Math SEO, and CookieYes for cookie consent. The site loads external fonts from Google Fonts and uses Fathom Analytics for tracking. Performance is moderate with good mobile optimization and basic accessibility features. The hosting provider is not explicitly identified but DNS uses hyp.net name servers. The site has valid meta tags and structured data in JSON-LD format, enhancing SEO. Technical debt is low, but security enhancements are recommended.
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 medscinet.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 medscinet.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.