Skip to main content

Security report for nhn.no

Norsk helsenett SF · Healthcare · Norway

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

Security score

52/100

Risk levelMedium

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

Norsk helsenett SF is a Norwegian state-owned enterprise responsible for delivering and maintaining national ICT infrastructure and e-health solutions for the healthcare sector. The organization is well-established with a domain age of 25 years and operates under the Ministry of Health and Care Services. Their services include healthcare registers, videoconferencing, electronic death notifications, and membership in the national health network, targeting healthcare professionals and Norwegian citizens. The website content is rich, professionally designed, and well-structured, providing clear navigation and relevant information about their offerings and events. Technically, the website uses modern frontend technologies such as Tailwind CSS and Matomo for analytics, hosted on Azure and served via Fastly CDN. The site is mobile-optimized and accessible, though performance is moderate with a page load time of approximately 4.8 seconds. SEO and metadata are well implemented, including Open Graph tags for social sharing. From a security perspective, the website currently lacks a valid SSL certificate, resulting in no HTTPS availability, which is a critical issue. Additionally, no security headers or HSTS are implemented, and TLS protocols are disabled, exposing the site to potential risks. The SPF DNS record is properly configured, and no subdomain takeover vulnerabilities were found. Privacy compliance is good, with a comprehensive privacy policy and cookie policy present, though no explicit cookie consent mechanism is implemented. Contact information is available via a contact page, but no direct emails or phone numbers are exposed on the site. Overall, the website is trustworthy and credible, reflecting its government ownership and mature domain registration. However, the lack of HTTPS and proper SSL configuration significantly impacts its security posture and user trust. Strategic improvements in SSL deployment, security headers, and cookie consent mechanisms are recommended to enhance security and compliance.

Scanned

NIS2 and GDPR posture

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

    • 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

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

  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 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 nhn.no

This scan found 14 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
0
Security headers
70
Email security
50
DNS health
90
Network security
100
GDPR outside view
0
Average
52

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

Norsk helsenett SF holds a critical position as the national ICT infrastructure provider for Norway's healthcare sector. Its state ownership and long domain history reinforce its authoritative market position. The business model focuses on providing essential digital infrastructure and services to healthcare actors, including registers, e-health solutions, and communication platforms. The target customers are healthcare professionals, government entities, and Norwegian citizens. The company maintains partnerships with health directorates and other government bodies, as evidenced by linked domains and service integrations. The website content and event listings indicate active engagement with suppliers and stakeholders, supporting continuous sector collaboration and innovation.

Security posture

The current security posture reveals significant gaps, primarily due to the absence of a valid SSL certificate and disabled TLS protocols, which prevent secure HTTPS connections. This exposes users to risks such as data interception and undermines trust. The lack of security headers and HSTS further weakens the site's defense against common web attacks. However, the presence of a valid SPF record and no subdomain takeover vulnerabilities are positive indicators. Privacy practices are aligned with GDPR, with a comprehensive privacy policy and minimal user tracking via Matomo with disabled cookies. Incident response and vulnerability disclosure mechanisms are not evident, suggesting areas for maturity improvement. Overall, the security maturity is low to moderate, requiring urgent remediation of SSL/TLS issues.

Recommendations

  1. Deploy and maintain a valid SSL/TLS certificate to enable HTTPS and protect user data.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable deprecated versions to enhance encryption security.
  3. Implement HTTP security headers such as Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy to mitigate common web vulnerabilities.
  4. Activate HSTS with includeSubDomains and preload options to enforce HTTPS usage and prevent downgrade attacks.
  5. Introduce a cookie consent mechanism to comply fully with GDPR and enhance user privacy transparency.

Contact details published on the site

Legal name
Norsk helsenett SF
Registration number
994598759
Technical notes

Notes

The website is built using modern frontend technologies including Tailwind CSS and SimpleBar for UI components, and Matomo for privacy-conscious analytics. It is hosted on Azure Web Apps and served through Fastly CDN, ensuring reliable global delivery. The site is mobile-optimized and accessible, with good SEO practices including meta tags and Open Graph data. Performance is moderate with a page load time of approximately 4.8 seconds, which could be improved. No common CMS was detected, indicating a custom or proprietary solution. The DNS configuration is robust with multiple A records, MX records pointing to Outlook protection, and a valid SPF record. However, malformed CAA records and missing SSL/TLS configuration represent technical risks that should be addressed to improve security and user trust.
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 nhn.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 nhn.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.