Skip to main content

Security report for sanlucar.com

SanLucar Fruit S.L.U. · Retail · Spain

High risk. 7 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

44/100

Risk levelHigh

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

SanLucar Fruit S.L.U. is a well-established company specializing in fresh fruits, vegetables, and related products, with a strong emphasis on quality, sustainability, and natural health benefits. The website reflects a mature digital presence with comprehensive product categories, corporate responsibility initiatives, and multilingual support targeting consumers and business partners globally. Technically, the site is built on WordPress with modern plugins and a reputable theme, offering good SEO and user experience. However, the absence of a valid SSL certificate and HTTPS severely impacts the security posture, exposing users to potential risks and undermining trust. Privacy policies and cookie consent mechanisms are present and appear GDPR compliant, supporting responsible data handling. Overall, while the business and content quality are high, urgent improvements in SSL/TLS implementation are necessary to enhance security and user trust.

Scanned

NIS2 and GDPR posture

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

7 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

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

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

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  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 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 sanlucar.com

This scan found 20 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
0
Security headers
15
Email security
50
DNS health
80
Network security
100
GDPR outside view
18
Average
44

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

SanLucar operates in the retail sector focusing on fresh produce, convenience foods, delicatessen, and plants. The company has a mature market position supported by 27 years of domain registration and a consistent brand image. Their business model includes direct consumer engagement and B2B partnerships, supported by a multilingual website and active social media channels. The company demonstrates commitment to quality and sustainability through certifications like the DREAMS-Programme and detailed quality promises. The website content and navigation cater well to their target audience, including consumers, retailers, and partners. No suspicious patterns or inconsistencies were found in domain registration or website content, indicating a legitimate and credible business operation.

Security posture

The website currently lacks a valid SSL certificate and does not support any TLS protocols, resulting in unencrypted HTTP traffic. This is a critical security gap that exposes users to interception and undermines trust. No advanced security headers such as HSTS are implemented, and OCSP stapling is disabled. The site shows no signs of common vulnerabilities like Heartbleed or POODLE, and no subdomain takeover risks were detected. Privacy policies and cookie consent are implemented, indicating awareness of compliance requirements. However, the lack of HTTPS and modern encryption protocols significantly lowers the security score and poses a risk to data confidentiality and integrity. Incident response and vulnerability disclosure mechanisms are not found, suggesting limited readiness for security incidents.

Recommendations

  1. Immediately install and configure a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable deprecated versions.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  4. Enable OCSP stapling to improve certificate revocation checking performance and security.
  5. Add security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  6. Establish an incident response page or contact channel for security issues and vulnerability disclosures.
  7. Regularly audit and update all plugins and themes to mitigate vulnerabilities.
  8. Enhance transparency by publishing data retention policies and DPO contact information if applicable.
  9. Improve performance monitoring and optimize loading times for better user experience.
  10. Maintain consistent branding and trust signals across all digital channels.
Technical notes

Notes

The website is powered by WordPress 6.8.1 using the Enfold theme and several plugins including Yoast SEO, WPML for multilingual support, Popup Builder, and Max Mega Menu. It uses jQuery 3.7.1 and MediaElement.js for media playback. The hosting provider is Acens Technologies, S.L.U., with Apache as the web server. The site employs caching and minified CSS/JS assets for performance. However, no SSL/TLS is configured, and no modern TLS protocols are enabled, which is a major technical deficiency. The site is mobile optimized with responsive design and accessibility features. SEO is enhanced by structured data (JSON-LD) and Open Graph tags. Performance metrics are not provided but the use of caching suggests moderate performance. The technical stack is modern but security implementation requires urgent improvement.
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 sanlucar.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 sanlucar.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.