Skip to main content

Security report for hortim.cz

Hortim · Retail · Czech Republic

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

Security score

73/100

Risk levelMedium

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

Hortim is a well-established Czech company specializing in the wholesale and comprehensive service of fresh fruit and vegetables, including farming, packing, storage, ripening, and logistics. The company operates multiple subsidiaries and brands, serving a broad market with significant annual throughput. Their website reflects a mature digital presence with multilingual support and detailed service descriptions. Technically, the site is built on WordPress with modern plugins and frameworks, ensuring good performance and SEO optimization. Security posture is solid with HTTPS, cookie consent, and reCAPTCHA, though some security headers and explicit incident response information are missing. The absence of WHOIS data limits domain trust verification, but the professional presentation and certifications support business credibility. Overall, Hortim demonstrates a strong market position with room for enhanced transparency and security documentation.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
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. 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

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics, Facebook, LinkedIn, Cloudflare

      What to do: Document all third-party data sharing in your privacy policy

  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 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';…

  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 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 hortim.cz

This scan found 18 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
75
Security headers
65
Email security
75
DNS health
80
Network security
100
GDPR outside view
40
Average
73

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

Hortim holds a significant position in the fresh produce wholesale sector in the Czech Republic and neighboring markets, supported by a network of subsidiaries and premium brands. Their business model integrates farming and logistics, providing end-to-end solutions. The company targets business customers requiring reliable supply chains for fresh produce. Their certifications and sustainability projects indicate a commitment to quality and environmental responsibility. The multilingual website and career portal suggest ongoing growth and international outreach. Partnerships and subsidiary domains reinforce a diversified ecosystem. However, the lack of publicly available WHOIS data and direct contact details on the website may pose challenges for trust verification in some contexts.

Security posture

The website employs HTTPS with a valid SSL certificate and integrates Google reCAPTCHA to protect forms, indicating a baseline security awareness. Cookie consent is implemented in compliance with GDPR requirements. However, the absence of key security headers such as Content-Security-Policy and Strict-Transport-Security reduces defense-in-depth. No explicit security or incident response policies are published, and no security.txt file is found, limiting transparency for vulnerability reporting. No vulnerabilities or exposed sensitive data were detected in the HTML content. Overall, the security posture is good but could be improved by adding security headers, incident response information, and vulnerability disclosure mechanisms.

Recommendations

  1. Implement security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to enhance protection against common web attacks.
  2. Publish a dedicated security policy and incident response page to improve transparency and readiness.
  3. Add a security.txt file to facilitate responsible vulnerability disclosure.
  4. Enhance accessibility features to meet compliance standards and improve user experience for all users.
  5. Provide clear company contact information including emails and phone numbers to improve trust and communication.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Hortim
Description
V Hortimu dnes umíme komplexní služby s čerstvým ovocem a zeleninou, od pěstování zeleniny na farmě, až po logistiku.
Key services
Farming, Packing, Storage, Ripening, Logistics and timely delivery
Content quality
excellent
Branding
consistent

Technology

Stack
WordPress, Yoast SEO plugin, jQuery 3.3.1, Slick Carousel, Google Tag Manager, Google reCAPTCHA, Facebook SDK, TermsFeed Cookie Consent
Frameworks
Bootstrap CSS
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Google reCAPTCHA for forms
  • Cookie consent mechanism
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics (via Google Tag Manager)
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Facebook SDK
Marketing tools
Facebook Pixel
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with rich content and multiple language versions
  2. Strong branding and consistent design
  3. Comprehensive cookie consent and privacy policy implementation
  4. No contact emails or phone numbers explicitly found in HTML content
  5. No visible forms collecting personal data on homepage
  6. Use of modern web technologies and SEO best practices
  7. No security.txt or explicit incident response info found
  8. WHOIS data unavailable, limiting domain trust verification
Technical notes

Notes

The website is built on WordPress CMS using a modern tech stack including Bootstrap for responsive design, jQuery, and Slick Carousel for UI components. SEO is enhanced via the Yoast SEO plugin, and analytics are managed through Google Tag Manager and Facebook Pixel. The site loads external scripts from reputable CDNs, ensuring performance and reliability. Mobile optimization is good with responsive layouts and viewport settings. Accessibility is basic but could be improved. No major technical debt or outdated libraries were detected. Hosting provider details are not explicitly available. Overall, the technical infrastructure supports a professional and performant web presence with opportunities for further optimization 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 hortim.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 hortim.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.