Security report for comm-sante.com
COMM Santé · Healthcare · France
COMM Santé is a specialized communication agency based in Bordeaux, France, focusing exclusively on the healthcare sector. The company offers a range of services including digital and social media management, press relations and influence, strategic communication, medical education and training, event management, and management of learned societies. The website presents a professional and consistent brand image targeting healthcare professionals and organizations. Technically, the site is built on WordPress with common modern web technologies such as jQuery, Google Fonts, and Google reCAPTCHA, indicating a moderate level of digital maturity. Performance and mobile optimization are adequate, though accessibility could be improved. Security posture is decent with HTTPS and CAPTCHA integration, but lacks visible security headers and published security policies. Privacy compliance is partially addressed through a GDPR cookie consent mechanism, but the absence of a clear privacy policy and terms of service pages is a gap. The WHOIS data is missing or unavailable, which raises some concerns about domain registration legitimacy, though the active and professional website presence mitigates this somewhat. Overall, the site is functional and professional but would benefit from enhanced transparency and security documentation.
Scanned
NIS2 and GDPR posture
- NIS2 outside view
- Not assessed
- GDPR outside view
- Not assessed
Both readouts depend on the site's pages, which could not be loaded in this scan.
Priority findings
4 findings rated critical or high. Fix these first.
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
- RFC 8996
- RFC 7568
- Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: tls_versions TLSv1.2, TLSv1.3
- NIS2 21(2)(h)
- IR 2024/2690 9.2(b): Implementing Regulation (EU) 2024/2690, Annex point 9.2(b): Cryptography
- NIST SC-8(1): NIST SP 800-53 Rev. 5 SC-8(1): Cryptographic Protection
- 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
- NIS2 21(2)(h)
- IR 2024/2690 9.2(b): Implementing Regulation (EU) 2024/2690, Annex point 9.2(b): Cryptography
- NIST SC-13: NIST SP 800-53 Rev. 5 SC-13: Cryptographic Protection
- High
DNS health
DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.
- High
Domain Expires Soon
Domain expires in 8 days
What to do: Renew domain registration before expiration
- High
Network security
Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.
- High
High-Risk Service Exposed: FTP
Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer
What to do: Consider restricting access to FTP or implementing strong authentication
- 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
- High
Need hands-on remediation? Email guard@offseq.com
Keep watching comm-sante.com
This scan found 16 issues across 4 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
- 52
- Email security
- 75
- DNS health
- 60
- Network security
- 20
- Average
- 52
Not counted
- Security headers: did not complete in this scan.
- GDPR outside view: did not complete in this scan.
- 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
Security posture
Recommendations
- Publish a comprehensive privacy policy page detailing data collection, usage, and user rights to improve GDPR compliance and user trust.
- Add a terms of service page to clarify user and client agreements and legal protections.
- Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to harden the website against common attacks.
- Provide clear contact information for security incidents or data protection officer to enhance incident response readiness and compliance.
- Verify and update WHOIS domain registration information to ensure transparency and legitimacy, or use a privacy protection service with clear justification.
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- Company
- COMM Santé
- Description
- COMM Santé, l'agence spécialisé en communication santé pour tous les acteurs de la santé.
- Key services
- Digital & social media, Relations presse & influence, Communication stratégique, Medical education & formation, Événementiel, Management des sociétés savantes
- Content quality
- good
- Branding
- consistent
Technology
- Stack
- WordPress, jQuery, LiteSpeed Cache, Google reCAPTCHA, Google Fonts
- Platforms
- Web
- Performance
- moderate
- Mobile
- good
- Accessibility
- basic
- SEO
- good
Security
- Observed score
- 75/100
- Good practices seen
- HTTPS enforced
- Google reCAPTCHA integration
- GDPR cookie consent mechanism
Analytics and tracking
- Services
- Google Analytics
- Tracking level
- moderate
- Privacy practices
- basic
Advertising
- Transparency
- basic
Site quality
- Design
- good
- User experience
- good
- Content relevance
- good
- Navigation
- good
- Professionalism
- good
- Trustworthiness
- moderate
Key observations
- Website is fully accessible with no blocking or WAF challenge
- Content is in French and focused on healthcare communication services
- No explicit privacy policy or terms of service pages found
- Cookie consent mechanism is implemented and GDPR focused
- No direct contact emails or phone numbers found on homepage content
- Social media links to LinkedIn and Twitter are present
- Uses WordPress CMS with common plugins and Google services
- No security headers detected in provided data
- WHOIS data is missing or domain unregistered, which is unusual
Technical notes
Notes
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.
- MITRE CWE (opens in a new tab)4.20 (2026-04-30) · CWE Terms of Use (free use with attribution, © MITRE)
- OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
- MITRE CAPEC (opens in a new tab)3.9 (2023-01-24) · CAPEC Terms of Use (free use with attribution, © MITRE)
- OWASP ASVS (opens in a new tab)5.0.0 · CC BY-SA 4.0
- OWASP Web Security Testing Guide (opens in a new tab)latest (checklist.json, master) · CC BY-SA 4.0
- OWASP Secure Headers Project (opens in a new tab)2026-10-18 · Apache-2.0
- Mozilla Server Side TLS (intermediate) (opens in a new tab)6.0 · MPL-2.0
- NIST SP 800-53 Rev. 5 (OSCAL catalog) (opens in a new tab)5.2.0 · Public domain (US Government work)
- Directive (EU) 2022/2555 (NIS2) (opens in a new tab)OJ L 333, 27.12.2022 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Commission Implementing Regulation (EU) 2024/2690 (opens in a new tab)OJ L, 18.10.2024 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Regulation (EU) 2016/679 (GDPR) (opens in a new tab)OJ L 119, 4.5.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive 2002/58/EC (ePrivacy), consolidated (opens in a new tab)19.12.2009 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- RFC Editor metadata (opens in a new tab)per-RFC (obsolete RFCs rejected) · IETF Trust Legal Provisions (metadata only)
- NIST CSRC, W3C TR, IETF Datatracker, EDPB, EUR-Lex CELLAR and gesetze-bayern.de (opens in a new tab)per document · Titles and links only
- NIST NVD CVE API 2.0 (opens in a new tab)live records · Public domain (NVD); CVE® records © MITRE, free use
- W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
- ETSI EN 301 549 (opens in a new tab)V3.2.1 (2021-03), clause headings · Clause numbers and titles only (© ETSI)
- Directive (EU) 2019/882 (European Accessibility Act) (opens in a new tab)OJ L 151, 7.6.2019 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive (EU) 2016/2102 (Web Accessibility Directive) (opens in a new tab)OJ L 327, 2.12.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Retrieved 2026-10-25
Feedback on this report
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with comm-sante.com. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review comm-sante.com.