Skip to main content

Security report for leroyseafood.com

Lerøy Seafood Group · Other · Norway

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

Security score

68/100

Risk levelMedium

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

Lerøy Seafood Group is a world-leading seafood company with roots dating back to 1899, headquartered in Bergen, Norway. The company operates in seafood production and distribution, targeting a broad audience including consumers and business partners. The website reflects a professional corporate presence with consistent branding and good content quality. Technically, the site leverages Microsoft Azure hosting, Google Analytics, and various marketing and consent management tools, indicating a mature digital infrastructure. Security posture is strong with HTTPS, security headers, and a comprehensive cookie consent mechanism, though explicit security policies and contact information are lacking. Overall, the site is trustworthy and compliant with privacy regulations, but WHOIS data is not publicly available, which is common for corporate domains using privacy protection services.

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

This scan found 23 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
47
Security headers
15
Email security
80
DNS health
80
Network security
100
GDPR outside view
88
Average
68

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 holds a strong market position as a large seafood producer with a long history. Its business model focuses on seafood production and sales, supported by a network of related domains indicating regional presence. The website's use of advanced analytics and marketing tools suggests active engagement in digital marketing and customer insights. Absence of explicit contact details and terms of service pages may limit direct customer engagement online but does not detract from overall credibility. The partnership ecosystem includes related seafood domains, enhancing market reach and operational footprint.

Security posture

The website demonstrates a good security maturity level with enforced HTTPS, multiple security headers, and a robust cookie consent framework aligned with GDPR. No vulnerabilities or exposed sensitive data were detected in the HTML content. However, the lack of published security policies, incident response contacts, or vulnerability disclosure mechanisms indicates room for improvement in transparency and readiness. The absence of WHOIS data is typical for privacy-protected domains but should be monitored for legitimacy. Overall, the security posture is solid but could benefit from enhanced policy disclosures and contact channels.

Recommendations

  1. Publish a clear Terms of Service page to improve legal transparency.
  2. Add explicit security policy and incident response information accessible to users.
  3. Implement a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  4. Enhance accessibility features to improve compliance and user experience.
  5. Provide clear and verified contact information for general and security inquiries to build trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Lerøy Seafood Group
Description
Lerøy Seafood Group er et verdensledende sjømatselskap med røtter tilbake til 1899. Hovedkontoret ligger i Bergen.
Key services
Seafood production, Seafood distribution, Seafood sales
Content quality
good
Branding
consistent

Technology

Stack
Microsoft Azure, Google Tag Manager, Google Analytics, Azure Application Insights, Cloudflare, CookieInformation Consent Management, Optimizely, Sleeknote, Vimeo
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism implemented
  • Use of security headers
  • No exposed sensitive data detected

Analytics and tracking

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

Advertising

Tracking pixels
Optimizely, Sleeknote
Marketing tools
Optimizely, Sleeknote
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenge
  2. Comprehensive cookie consent mechanism implemented with detailed cookie descriptions
  3. No explicit contact emails or phone numbers found on main page HTML
  4. No Terms of Service or explicit security policy pages found
  5. Use of multiple Microsoft Azure services and Google Analytics for hosting and analytics
  6. Good SEO and meta tag implementation including Open Graph tags
  7. No signs of adult or questionable content
  8. WHOIS data unavailable publicly, indicating privacy protection
Technical notes

Notes

The website is hosted on Microsoft Azure and uses modern technologies including Google Tag Manager, Azure Application Insights, and various marketing and analytics tools such as Optimizely and Sleeknote. The site is mobile optimized with good SEO practices and a comprehensive cookie consent mechanism. Performance is moderate, with potential for improvement in accessibility. No CMS was explicitly detected, suggesting a custom or proprietary platform. The technical stack supports a professional and scalable digital presence suitable for a large enterprise.
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.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 leroyseafood.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.