Skip to main content

Security report for doctowell.com

DoctoWell · Healthcare · N/a

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

Security score

67/100

Risk levelMedium

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

DoctoWell is a small healthcare technology company founded in 2020, offering AI-powered growth, medical, and administrative solutions targeted at healthcare providers and medical professionals. The website presents a professional design with good content relevance and user experience, focusing on AI-driven tools to optimize healthcare operations. Technically, the site uses HTTPS and Cloudflare DNS services, with web fonts loaded from external providers, but lacks advanced security headers and privacy compliance mechanisms. Security posture is moderate with no critical vulnerabilities detected, but improvements are needed in DNS security (DNSSEC) and security policy disclosures. Overall, the risk level is moderate with recommendations to enhance privacy policies, security headers, and contact transparency to improve trust and compliance.

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

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

      GDPR requires clear information about cookie usage

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

  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
    • 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 doctowell.com

This scan found 24 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
57
Security headers
30
Email security
60
DNS health
75
Network security
100
GDPR outside view
80
Average
67

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

The company operates in the healthcare and technology sectors, providing AI-based solutions for medical and administrative growth. Its business model appears to be B2B SaaS or service-oriented, targeting healthcare providers seeking operational efficiency. The domain age and WHOIS data align with a startup profile. No partner or subsidiary domains were identified. The lack of contact information and policies may limit customer trust and regulatory compliance. Market positioning is emerging with potential for growth in AI healthcare solutions.

Security posture

The website enforces HTTPS and has domain transfer protections in place, but lacks DNSSEC and security headers such as Content-Security-Policy or Strict-Transport-Security. No incident response or vulnerability disclosure information is provided. No exposed sensitive data or vulnerable libraries were detected in the HTML. Privacy compliance is weak due to missing privacy and cookie policies. Overall security maturity is moderate but requires enhancements to meet best practices and regulatory standards.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement and configure security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish comprehensive privacy and cookie policies with GDPR compliance and consent mechanisms.
  4. Add clear contact information including company emails and phone numbers for support and security incidents.
  5. Establish a vulnerability disclosure policy or security.txt file to improve transparency and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
DoctoWell
Description
DoctoWell provides AI-powered solutions focused on growth, medical, and administrative services, targeting healthcare providers and medical professionals to optimize their operations and patient management.
Key services
AI-powered medical solutions, Administrative automation, Growth and operational optimization
Content quality
good
Branding
moderate

Technology

Stack
Cloudflare DNS, Fonts Bunny (web fonts), HTML5, CSS3
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
70/100
Good practices seen
  • Domain uses HTTPS
  • Domain status clientTransferProhibited

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is accessible with full content and no blocking detected.
  2. No privacy, cookie, or terms of service policies found on the site.
  3. No contact emails, phone numbers, or physical addresses explicitly found in the content.
  4. No social media links or security incident contacts detected.
  5. Website uses HTTPS and Cloudflare DNS but lacks advanced security headers.
  6. Content is focused on AI-powered healthcare and administrative solutions.
  7. No advertising or tracking technologies detected in the provided HTML.
  8. No explicit or adult content detected; content is safe for general audiences.
Technical notes

Notes

The website uses modern web fonts and is hosted behind Cloudflare DNS, ensuring good availability and basic security. The HTML structure is valid with responsive design elements for mobile optimization. However, no advanced frameworks or CMS were detected, indicating a custom or lightweight build. Performance is moderate with no obvious blocking scripts or heavy resources. SEO is basic with meta viewport and title tags but lacks Open Graph or structured data for enhanced search presence. Accessibility features are minimal but present. Technical debt appears low but opportunities exist for modernization and security hardening.
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 doctowell.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 doctowell.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.