Skip to main content

Security report for 321med14.com

321 MED GmbH · Healthcare · Germany

High risk. 9 critical or high findings in Network security, Security headers and 2 other checks.

Security score

49/100

Risk levelHigh

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

321 MED GmbH is a German healthcare technology company specializing in digital reception and practice management software for medical facilities such as clinics, medical practices, and pharmacies. Their flagship product, the Online-Rezeption, offers a comprehensive suite of features including patient management, appointment scheduling, AI-powered telephone assistance, and workflow automation. The company has established a strong market presence with over 3,500 healthcare providers and 5 million patients served, emphasizing significant time savings and improved patient communication. The website reflects a mature, professional business with consistent branding and extensive media coverage. Technically, the website employs modern web technologies including jQuery, Usercentrics for GDPR-compliant consent management, Google Tag Manager, and Facebook Pixel for analytics and marketing. Hosting and DNS services leverage Cloudflare, although DNSSEC is not enabled. The site is mobile-optimized, accessible, and SEO-friendly, with fast loading times and rich multimedia content enhancing user engagement. From a security perspective, the site enforces HTTPS with a strong SSL configuration and integrates GDPR-compliant cookie consent. However, it lacks visible HTTP security headers and published security policies or incident response contacts. No vulnerabilities or exposed sensitive data were detected. The WHOIS data is consistent with the business claims, showing a domain age appropriate for the company's history and no privacy protection, which supports transparency. Overall, the website demonstrates a high level of professionalism, security, and compliance suitable for a healthcare software provider. Strategic improvements include enabling DNSSEC, publishing security policies, and adding incident response contacts to further enhance trust and security posture.

Scanned

NIS2 and GDPR posture

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

9 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
    • Critical

      Critical Service Exposed: PostgreSQL

      Port 5432 (PostgreSQL) is publicly accessible - PostgreSQL - Database server

      What to do: Immediately restrict access to PostgreSQL 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';…

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

Keep watching 321med14.com

This scan found 25 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
72
Security headers
20
Email security
90
DNS health
65
Network security
0
GDPR outside view
65
Average
52
After the cap
49

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

321 MED operates in the healthcare technology sector, targeting a broad range of medical providers from general practitioners to specialized clinics. Their SaaS business model focuses on digital transformation of patient reception and administrative workflows, leveraging automation and AI to reduce operational burdens. The company benefits from strong market validation through extensive user base and media presence. Their partnership ecosystem includes various medical centers and clinics showcased as references. The business model is subscription-based with a free trial phase, facilitating customer acquisition and retention. Growth indicators include media citations and testimonials from diverse medical professionals. The company maintains a clear focus on GDPR compliance and data protection, critical in healthcare IT. Strategic observations suggest continued expansion into specialized medical fields and enhancement of AI capabilities to maintain competitive advantage.

Security posture

The website exhibits a mature security posture with mandatory HTTPS and GDPR-compliant cookie consent mechanisms. The use of Usercentrics CMP and absence of exposed sensitive data indicate good data protection practices. However, the lack of DNSSEC and absence of HTTP security headers such as Content Security Policy, HSTS, and X-Frame-Options represent areas for improvement. No published security policy or incident response contact reduces transparency in vulnerability management. The site does not expose any known vulnerable libraries or insecure forms. Overall, the security maturity is good but can be enhanced by adopting additional security headers, enabling DNSSEC, and publishing formal security and incident response documentation. These steps would improve compliance with best practices and increase trustworthiness among healthcare clients.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement and publish HTTP security headers including Content Security Policy, HSTS, and X-Frame-Options.
  3. Publish a dedicated security policy page outlining security practices and compliance.
  4. Provide clear incident response contact information such as security@ or abuse@ email addresses.
  5. Consider adding a security.txt file to facilitate responsible vulnerability disclosure.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
321 MED GmbH
Description
321 MED is the online contact point between patients and healthcare providers (e.g. doctor's offices, clinics) - made by doctors. It offers a comprehensive software solution to digitize reception and administrative processes in medical practices, clinics, and medical care centers, simplifying appointment scheduling, patient communication, and management.
Key services
Patient management, Appointment scheduling and management, Digital check-in, Automated reminders and recalls, Internal practice communication, Online consultations, Patient data import/export, Multi-platform compatibility, Referrer portal, AI-powered telephone assistant
Content quality
excellent
Branding
consistent

Technology

Stack
jQuery, jQuery UI, Usercentrics CMP, Google Tag Manager, Facebook Pixel, Cloudflare DNS
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • GDPR compliant cookie consent via Usercentrics
  • No exposed sensitive data in HTML
  • No vulnerable libraries detected

Analytics and tracking

Services
Google Tag Manager, Facebook Pixel
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Facebook Pixel
Marketing tools
Usercentrics CMP
Transparency
good

Site quality

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

Key observations

  1. Website is professionally designed and well-structured.
  2. Content is comprehensive and targeted to healthcare providers.
  3. Strong emphasis on GDPR compliance and data protection.
  4. No direct contact emails or phone numbers found on main page; contact likely via forms or subpages.
  5. Multiple embedded videos and media references enhance trust.
  6. Use of modern tracking and consent management tools.
  7. No visible security policy or incident response contact information.
  8. No DNSSEC enabled, which is a minor security gap.
Technical notes

Notes

The website uses a modern and stable technology stack centered on jQuery and jQuery UI for frontend interactions. It integrates third-party services for consent management (Usercentrics), analytics (Google Tag Manager, Facebook Pixel), and video content (Streamable). Hosting and DNS are managed via Cloudflare, providing performance and security benefits, though DNSSEC is not enabled. The site is well-optimized for mobile devices and accessibility, with comprehensive CSS styling and responsive design. Performance is moderate with efficient loading of multimedia content. There is no detected CMS, suggesting a custom or proprietary platform. Technical risks are minimal but include the absence of some security headers and DNSSEC, which could be addressed to reduce attack surface and improve resilience.
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 321med14.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 321med14.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.