Skip to main content

Security report for leroyseafood.nl

Lerøy Seafood Netherlands · Other · Netherlands

Medium risk. 5 critical or high findings in Security headers and SSL/TLS.

Security score

69/100

Risk levelMedium

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

Lerøy Seafood Netherlands operates as a seafood supplier and related services provider in the Netherlands, positioned as an important player within the seafood sector. The website presents a professional corporate image with consistent branding and good content quality focused on business audiences. The technical infrastructure leverages Microsoft Azure hosting, Google Tag Manager, and Application Insights for monitoring, indicating a mature digital setup. The site implements a comprehensive cookie consent mechanism aligned with GDPR requirements, reflecting good privacy compliance. Security posture is strong with HTTPS enforced and monitoring tools in place, though explicit security headers and incident response policies are absent. Overall, the website is trustworthy and well-maintained, with room for improvement in publishing security policies and contact information.

Scanned

NIS2 and GDPR posture

GDPR outside view
88/ 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 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';…

  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.

    • 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 leroyseafood.nl

This scan found 21 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
57
Security headers
15
Email security
90
DNS health
65
Network security
100
GDPR outside view
88
Average
69

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 is part of the Lerøy Seafood Group, a known entity in the seafood industry. The website links to related domains indicating a partnership ecosystem within the seafood and seaweed sectors. The business model appears B2B focused, supplying seafood products and providing market insights. The use of advanced analytics and marketing tools like Optimizely and Sleeknote suggests active engagement in digital marketing and user experience optimization. Absence of direct contact details on the homepage may indicate a preference for controlled communication channels or internal handling. The company targets business clients in the Netherlands and possibly broader European markets.

Security posture

The website demonstrates a solid security foundation with HTTPS and monitoring via Microsoft Application Insights. Cookie consent is managed professionally with clear categories and vendor disclosures. However, the lack of explicit security headers such as Content-Security-Policy and absence of published security policies or incident response contacts represent gaps in security transparency and maturity. No vulnerabilities or suspicious patterns were detected in the visible content. The site does not appear to be behind a WAF challenge or blocked by security mechanisms, allowing full content access. Overall, the security posture is good but could be enhanced by publishing formal security documentation and adding security headers.

Recommendations

  1. Publish a dedicated security policy and incident response contact information on the website.
  2. Implement and enforce security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Add a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  4. Include clear and accessible contact information for business and security inquiries.
  5. Regularly review and update cookie and privacy policies to maintain GDPR compliance and transparency.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Lerøy Seafood Netherlands
Description
Website voor Lerøy Seafood Netherlands.
Key services
Seafood supply, Market reports, Sustainability information
Content quality
good
Branding
consistent

Technology

Stack
Microsoft Azure, Google Tag Manager, Application Insights, CookieInformation Consent Management, Cloudflare (likely CDN/protection), Optimizely
Frameworks
ASP.NET Core
Platforms
Azure
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner with opt-in/out
  • Use of Application Insights for monitoring

Analytics and tracking

Services
Google Analytics, Microsoft Application Insights, Optimizely
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Application Insights, Optimizely
Marketing tools
Sleeknote
Transparency
good

Site quality

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

Key observations

  1. Comprehensive cookie consent mechanism implemented
  2. Use of multiple domains related to parent and sister companies
  3. Strong use of Microsoft Azure infrastructure
  4. No visible contact information on homepage or in HTML snippet
  5. No terms of service or security policy pages detected
  6. Good privacy compliance with clear cookie and privacy policies
  7. No signs of adult or questionable content
  8. No WAF or blocking mechanisms detected
Technical notes

Notes

The website is hosted on Microsoft Azure and uses modern technologies including ASP.NET Core, Google Tag Manager, and Application Insights. Performance is moderate with good mobile optimization and SEO practices. The site uses a comprehensive cookie consent management system from CookieInformation, ensuring compliance with privacy regulations. External integrations include Optimizely for A/B testing and Sleeknote for marketing. The technical stack is robust and suitable for a medium-sized enterprise, though explicit CMS identification was not possible. Opportunities exist to improve accessibility and add security headers to enhance protection and compliance.
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 leroyseafood.nl. 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 leroyseafood.nl.

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.