Skip to main content

Security report for oslomet.no

OsloMet · Education · Norway

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

Security score

68/100

Risk levelMedium

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

OsloMet is a Norwegian state university specializing in education and research across health, society, technology, and pedagogy. It holds a significant position as a major urban university in Norway, offering a broad range of higher education programs and engaging in active research collaborations. The website targets students, researchers, and the academic community, providing comprehensive information about studies, research news, and collaboration opportunities. Technically, the site employs modern JavaScript libraries such as jQuery and LoadJS and integrates Siteimprove Analytics for performance and accessibility monitoring. However, the website suffers from a critical security deficiency due to the absence of a valid SSL certificate and HTTPS support, exposing users to potential risks. The security posture is further weakened by missing security headers and lack of HSTS, although email authentication via DMARC is properly configured. Overall, the site demonstrates good content quality, accessibility, and business credibility but requires urgent security improvements to protect user data and maintain trust.

Scanned

NIS2 and GDPR posture

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

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

    • 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

    • High

      Third-party services without privacy policy

      Detected services: Facebook, LinkedIn

      What to do: Document all third-party data sharing in your privacy policy

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

Keep watching oslomet.no

This scan found 10 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
50
Security headers
95
Email security
50
DNS health
90
Network security
100
GDPR outside view
25
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

OsloMet operates as a public university with a clear focus on education and research services, primarily serving the Norwegian academic and student community. Its market position is strong within Norway's higher education sector, supported by multiple national research centers and collaborations. The business model is non-commercial, funded by the government, focusing on knowledge dissemination and innovation. The website reflects this with extensive content on studies, research news, and community engagement. The presence of social media channels and a newsletter subscription indicates active outreach and engagement strategies. No commercial partnerships or subsidiaries are evident from the data. The domain registration and WHOIS data confirm legitimacy and consistency with the institution's profile.

Security posture

The current security posture of the website is weak due to the lack of HTTPS and an invalid SSL certificate, which is a critical vulnerability that undermines user trust and data confidentiality. While email security is robust with a strict DMARC reject policy and SPF records, the absence of TLS protocols, HSTS, and security headers exposes the site to potential man-in-the-middle attacks and other web-based threats. No incident response or security policy information is publicly available, indicating potential gaps in transparency and preparedness. The site does not provide a vulnerability disclosure or security.txt file, limiting external security collaboration. Immediate remediation of SSL/TLS issues and implementation of standard security headers are recommended to elevate the security posture.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable insecure protocols.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  4. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  5. Publish a clear security policy and incident response contact information on the website.
  6. Introduce a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  7. Optimize website performance to reduce load times and improve user experience.
  8. Maintain and regularly update third-party libraries to avoid vulnerabilities.

Contact details published on the site

Addresses
Technical notes

Notes

The website uses a modern JavaScript-based front-end stack including jQuery, LoadJS for script loading, LazySizes for lazy loading images, Moment.js for date handling, LightGallery for media display, and FitVids for responsive video embeds. Siteimprove Analytics is integrated for monitoring accessibility and performance. The DNS setup includes Microsoft Outlook mail protection and SPF/DKIM/DMARC records, indicating good email security practices. However, the lack of a valid SSL certificate and disabled TLS protocols represent significant technical debt and security risk. The site is hosted on infrastructure with DNS servers under uninett.no, suggesting academic/government hosting. Performance is poor with a load time exceeding 10 seconds and a large page size, indicating opportunities for optimization. Accessibility and SEO are well addressed with proper meta tags, Open Graph data, and responsive design. No CMS or backend platform is explicitly detected.
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 oslomet.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 oslomet.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.