Skip to main content

Security report for sjomatnorge.no

Sjømat Norge · Other · Norway

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

Security score

60/100

Risk levelMedium

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

Sjømat Norge is Norway's largest seafood organization, dedicated to improving conditions for the Norwegian seafood industry. The website serves as an informational and advocacy platform targeting industry stakeholders and the general public interested in seafood. The business is well-established with a domain age of approximately 9 years, reflecting a stable market presence. Technically, the website is built on WordPress with a modern technology stack including jQuery, Google Fonts, and Cookiebot for consent management. Analytics are implemented via Matomo and Google Analytics, complemented by Google reCAPTCHA for bot protection. Security posture is solid with HTTPS enforced and standard security headers likely in place, although explicit security policies and incident response contacts are not found. Privacy compliance is partially addressed through Cookiebot consent mechanisms, but the absence of a dedicated privacy policy and terms of service pages indicates room for improvement. Overall, the website is professional, trustworthy, and safe for general audiences.

Scanned

NIS2 and GDPR posture

GDPR outside view
83/ 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 sjomatnorge.no

This scan found 22 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
52
Security headers
15
Email security
85
DNS health
85
Network security
40
GDPR outside view
83
Average
60

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

Sjømat Norge holds a leading position in the Norwegian seafood sector, functioning as an essential industry organization. Its business model revolves around advocacy, representation, and information dissemination to support the seafood industry. The website targets Norwegian seafood stakeholders and the public, providing relevant content and services. The organization appears medium-sized with consistent branding and a clear market focus. While the website integrates multiple marketing and analytics tools, it lacks explicit contact details and formal policy documents, which could enhance transparency and user trust. The partnership ecosystem includes major platforms like Google and Facebook for marketing and analytics, but no direct partner or subsidiary domains were identified.

Security posture

The website demonstrates a good security posture with HTTPS enabled and the use of security best practices such as Google reCAPTCHA and Cookiebot for consent management. No critical vulnerabilities or exposed sensitive data were detected in the HTML content. However, the absence of a published security policy, incident response information, and vulnerability disclosure mechanisms limits the overall security maturity. The site uses standard WordPress plugins and libraries, which should be regularly updated to mitigate risks. Security headers appear to be implemented, but explicit confirmation is lacking. Overall, the security posture is adequate but could be strengthened by formalizing policies and improving transparency around incident handling.

Recommendations

  1. Publish a comprehensive privacy policy page detailing GDPR compliance and data handling practices.
  2. Add a terms of service page to clarify user rights and obligations.
  3. Implement a security.txt file to facilitate vulnerability reporting and improve security transparency.
  4. Enhance accessibility features to meet recognized standards and improve user experience for all visitors.
  5. Regularly audit and update third-party scripts and plugins to minimize security risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Sjømat Norge
Description
Sjømat Norge er landets største sjømatorganisasjon. Vi arbeider for å bedre vilkårene for norsk sjømatnæring.
Key services
Advocacy, Industry representation, Information dissemination
Content quality
good
Branding
consistent

Technology

Stack
WordPress 6.5.7, jQuery 3.7.1, Google Fonts (Open Sans), Typekit Fonts, Cookiebot Consent Management, Matomo Analytics, Google reCAPTCHA, Simple Lightbox, Ultimate Addons for Contact Form 7
Frameworks
WordPress
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • Cookie consent management via Cookiebot
  • Use of Google reCAPTCHA for bot protection
  • No exposed sensitive data found in HTML

Analytics and tracking

Services
Matomo Analytics, Google Analytics
Tracking level
extensive
Privacy practices
basic

Advertising

Ad networks
Google AdSense, Meta Platforms (Facebook)
Tracking pixels
Cookiebot tracking, Facebook tracking pixel
Marketing tools
Matomo Analytics, Cookiebot
Transparency
good

Site quality

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

Key observations

  1. Website uses modern consent management with Cookiebot.
  2. No explicit privacy policy or terms of service pages found in provided content.
  3. Website is built on WordPress with standard plugins and scripts.
  4. Good use of HTTPS and security best practices observed.
  5. No contact emails or phone numbers explicitly found in the HTML content.
  6. Extensive use of third-party analytics and marketing scripts.
  7. No signs of adult or questionable content.
  8. No WAF or blocking mechanisms detected.
Technical notes

Notes

The website is built on a WordPress CMS platform using version 6.5.7, with a modern tech stack including jQuery 3.7.1, Google Fonts, and Typekit for typography. Cookiebot is used for cookie consent management, and analytics are handled via Matomo and Google Analytics. The site loads external scripts asynchronously and uses Google reCAPTCHA for bot protection. Performance is moderate with good mobile optimization and SEO practices evident through meta tags and structured data (JSON-LD). Hosting provider details are not explicit but likely involve a WordPress-optimized environment with CDN support. The site shows no signs of technical debt or major performance bottlenecks but could benefit from enhanced accessibility and formalized security documentation.
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 sjomatnorge.no. 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 sjomatnorge.no.

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.