Skip to main content

Security report for regjeringen.no

Regjeringen.no · Government · Norway

Medium risk. 4 critical or high findings in Security headers and GDPR outside view.

Security score

63/100

Risk levelMedium

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

Regjeringen.no is the official Norwegian government website providing comprehensive insights into the work of the government and its ministries. It serves as a key communication channel for news, documents, and public engagement, targeting Norwegian citizens and stakeholders interested in government affairs. The website is well-branded, professionally designed, and offers excellent content quality with clear navigation and accessibility features. Technically, the site uses modern analytics tools such as Matomo and Microsoft Application Insights, but suffers from slow load times and lacks a valid SSL certificate, which critically impacts its security posture. The absence of HTTPS and security headers exposes the site to potential risks and undermines user trust. Privacy compliance is strong, with a clear cookie consent mechanism and a comprehensive privacy policy. Contact information is transparent, including phone and physical address details. Overall, the site is highly credible as a government portal but urgently needs to address its SSL/TLS configuration to improve security and user trust.

Scanned

This is an earlier scan of regjeringen.no. View the latest report

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
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

4 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 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. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

Need hands-on remediation? Email guard@offseq.com

Keep watching regjeringen.no

This scan found 13 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
50
Security headers
70
Email security
50
DNS health
85
Network security
85
GDPR outside view
40
Average
63

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 website operates as a government information portal, providing authoritative content on policies, government members, and official documents. Its market position is strong as the official source for Norwegian government information. The business model is non-commercial, focusing on transparency and public service. The site targets a broad audience including citizens, media, and international observers. The use of modern analytics indicates a commitment to understanding user engagement. The domain is mature and consistent with the organization's history. No partnerships or subsidiaries are explicitly linked. The site’s content and structure support its role as a trusted government resource.

Security posture

The security posture of regjeringen.no is currently weak due to the lack of a valid SSL certificate and absence of HTTPS, which is a critical vulnerability for any modern website, especially a government portal. No security headers are implemented, and advanced SSL features like HSTS and OCSP stapling are missing. While no known vulnerabilities or malware are detected, the missing HTTPS exposes users to risks such as data interception and man-in-the-middle attacks. The site does implement cookie consent and privacy policies, indicating awareness of privacy regulations. Incident response and security policies are not explicitly found on the site. Immediate remediation of SSL/TLS configuration is recommended to enhance security and trust.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  3. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Enable OCSP stapling and session resumption to improve SSL performance and security.
  5. Publish explicit security and incident response policies, including contact channels for security issues.

Contact details published on the site

Addresses
Legal name
Departementenes digitaliseringsorganisasjon (DIO)
Registration number
932 931 311
Technical notes

Notes

The website uses a combination of modern JavaScript libraries including jQuery and Slick Carousel, along with analytics tools Matomo and Microsoft Application Insights. Hosting is managed via Microsoft Azure DNS, indicating a robust infrastructure. However, the site suffers from slow load times (~6.4 seconds) and lacks a valid SSL certificate, which is a significant technical debt. The HTML is well-structured with proper meta tags, Open Graph, and JSON-LD structured data for SEO and social sharing. Accessibility and mobile optimization are well addressed. There is no detected CMS or framework explicitly identified. The site uses custom scripts for cookie consent and user interaction. Overall, the technical implementation is solid but requires urgent security upgrades and performance optimization.
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

Earlier scans of this domain

  1. 78/100Low24 findingsView report
  2. 78/100Low24 findingsView report
Reviews of this site

Share your experience with regjeringen.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 regjeringen.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.