Skip to main content

Security report for florence.cz

Care Comm s.r.o. · Healthcare · Czech Republic

Medium risk. 10 critical or high findings in GDPR outside view, Email security and 3 other checks.

Security score

54/100

Risk levelMedium

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

Florence.cz is a Czech professional healthcare journal focused on nursing and related medical professions. Operated by Care Comm s.r.o., it provides current news, expert articles, educational resources, and job listings for healthcare professionals. The website is well-structured, content-rich, and targets healthcare practitioners primarily in the Czech Republic. Technically, the site uses a mix of JavaScript libraries including jQuery, Google Fonts, and integrates third-party advertising and tracking services such as Facebook Pixel and Google Analytics. The site is served over HTTPS with cookie consent mechanisms in place, reflecting good privacy compliance. However, the absence of WHOIS data for the domain raises concerns about domain registration transparency. Security headers are not visibly implemented, and no explicit security or incident response policies are published. Overall, the site presents a professional and trustworthy front for its niche audience but would benefit from enhanced security practices and clearer domain registration information.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
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

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

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

  2. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

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

This scan found 27 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
42
Security headers
35
Email security
60
DNS health
60
Network security
100
GDPR outside view
25
Average
54

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention florence.cz, from OffSeq Breach.

No leaked records found

Breach holds no records for florence.cz right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Florence.cz holds a niche position as a specialized healthcare media outlet in the Czech Republic, focusing on nursing and healthcare professions. Its business model relies on subscriptions, advertising, and partnerships with healthcare organizations. The site demonstrates consistent branding and professional content quality, supported by a parent company Care Comm s.r.o. The presence of partner domains and event calendars indicates an active engagement with the healthcare community. Growth potential exists through expanded digital offerings and enhanced user engagement. The lack of visible phone contacts and limited public company registration details may limit some user trust but does not detract significantly from its market presence.

Security posture

The website enforces HTTPS and uses cookie consent banners aligned with GDPR requirements, indicating a baseline of security and privacy awareness. However, the lack of security headers such as Content-Security-Policy and X-Frame-Options reduces protection against common web attacks. The use of multiple third-party scripts introduces potential risk vectors that require ongoing monitoring. No vulnerability disclosure or incident response information is publicly available, which could hinder timely security issue reporting and resolution. The missing WHOIS data is a notable gap in domain transparency, which could be a risk factor. Overall, the security posture is moderate but could be significantly improved with additional controls and transparency.

Recommendations

  1. Implement and enforce security headers including Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options to enhance protection against web vulnerabilities.
  2. Publish clear terms of service, security policy, and incident response contact information to improve transparency and user trust.
  3. Add a security.txt file to facilitate vulnerability reporting and improve security communication.
  4. Investigate and resolve the missing WHOIS data to ensure domain registration transparency and legitimacy.
  5. Enhance accessibility features and mobile optimization to improve user experience and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Care Comm s.r.o.
Description
Florence publishes current information and professional articles on nursing theory and practice, including news, case studies, practical experiences, and research work. It also informs about legislative and management news relevant to healthcare professions.
Key services
Publishing professional nursing articles, News and updates in healthcare, Educational event calendar, Job offers in healthcare, Subscription services
Content quality
good
Branding
consistent

Technology

Stack
jQuery, Google Fonts, Facebook Pixel, Mapy.cz API, Cookie Consent scripts, Advertiser.fontai.com ad scripts
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Cookie consent with opt-in/out
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics (via gtag.js)
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
advertiser.fontai.com
Tracking pixels
Facebook Pixel
Marketing tools
Facebook Pixel
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content in Czech language.
  2. No WHOIS data available, which is unusual and may indicate privacy protection or registration issues.
  3. Professional healthcare journal with clear navigation and multiple content sections.
  4. Cookie consent and privacy policy are implemented and GDPR compliant.
  5. Use of multiple third-party scripts including advertising and tracking pixels.
  6. No visible security headers detected in HTML source; recommend adding.
  7. No contact phone numbers explicitly found; only email and contact form references.
  8. No terms of service or explicit security policy pages found.
  9. No vulnerability disclosure or security.txt found.
  10. No adult or questionable content detected; content is safe for general audiences.
Technical notes

Notes

The website uses a traditional web stack with jQuery and several CSS stylesheets for layout and presentation. It integrates Google Fonts for typography and Mapy.cz API for mapping features. Advertising is managed through advertiser.fontai.com scripts, and user tracking is implemented via Facebook Pixel and Google Analytics. The site loads asynchronously and appears moderately performant. No CMS is explicitly detected, suggesting a custom or proprietary platform. The site is mobile responsive with basic accessibility features but lacks advanced ARIA roles or landmarks. Technical debt appears low but could be reduced by consolidating scripts and improving security headers.
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 florence.cz. 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 florence.cz.

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.