Skip to main content

Security report for dibk.no

Direktoratet for byggkvalitet · Government · Norway

Medium risk. 5 critical or high findings in GDPR outside view and SSL/TLS.

Security score

75/100

Risk levelMedium

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

Direktoratet for byggkvalitet is a Norwegian government agency dedicated to ensuring the construction of safe, environmentally friendly, and accessible buildings. It serves a broad audience including private individuals, professional users, municipalities, and construction industry stakeholders by providing digital building application services, regulatory guidance, enforcement, and certification. The agency holds a strong market position as the authoritative body for building quality and regulations in Norway. The website demonstrates a mature technical infrastructure utilizing modern JavaScript libraries such as jQuery, Bootstrap, RequireJS, and TinyMCE, built on the Episerver CMS platform. The site is well-optimized for mobile devices, accessible, and SEO-friendly, with comprehensive metadata and structured content. Performance is moderate, with deferred script loading and good use of modern web standards. Security posture is solid with enforced HTTPS and no visible exposure of sensitive data. However, the absence of explicit security headers and a cookie consent mechanism indicates room for improvement in compliance and security best practices. The use of Matomo analytics reflects a privacy-conscious approach, though no explicit cookie banner was detected. Overall, the website is professional, trustworthy, and well-aligned with its government mandate. Strategic recommendations include implementing a cookie consent banner, publishing a security policy and incident response contacts, adding security headers, and considering a vulnerability disclosure page to enhance transparency and compliance.

Scanned

NIS2 and GDPR posture

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

5 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: Google APIs

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

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

This scan found 19 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
67
Security headers
75
Email security
80
DNS health
90
Network security
100
GDPR outside view
35
Average
75

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 agency operates as a government entity providing essential regulatory and advisory services in the construction sector. Its business model centers on governance, compliance enforcement, and digital service provision rather than commercial revenue generation. The target customers include private citizens, professional builders, and municipal authorities. The website content and structure indicate a well-established organization with consistent branding and a comprehensive service offering. The agency maintains a strong partnership ecosystem with related government and regulatory bodies, as evidenced by numerous internal and external links. Growth indicators include active news updates, public consultations, and digital service enhancements.

Security posture

The website exhibits a mature security posture with mandatory HTTPS and no detected vulnerabilities or exposed sensitive information. The lack of visible security headers such as Content-Security-Policy and absence of explicit incident response contacts or security policies suggest moderate maturity in security governance. The use of Matomo analytics aligns with privacy best practices, but the missing cookie consent mechanism is a compliance gap under GDPR. No security.txt or vulnerability disclosure page was found, limiting transparency for security researchers. Overall, the site is secure but could benefit from enhanced security policy publication and technical header implementation.

Recommendations

  1. Implement a cookie consent banner to comply with EU cookie regulations and improve privacy compliance.
  2. Publish a clear security policy and incident response contact information on the website.
  3. Add security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options to strengthen technical security.
  4. Provide explicit contact channels for reporting security incidents or vulnerabilities, such as security@ or abuse@ email addresses.
  5. Consider publishing a vulnerability disclosure or security.txt file to enhance transparency and encourage responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Direktoratet for byggkvalitet
Description
Vi bidrar til at det blir bygget sikre, miljøvennlige og tilgjengelige bygninger, og at kravene til byggverk blir fulgt.
Key services
Digital building application services, Regulatory guidance and enforcement, Building product documentation and control, Central approval and certification services, Information and advisory services
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, jQuery, Bootstrap, RequireJS, TinyMCE
Frameworks
Foundation (CSS media queries classes detected)
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced (canonical link uses https)
  • No inline sensitive data exposure
  • Use of deferred script loading

Analytics and tracking

Services
Matomo
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Matomo
Transparency
basic

Site quality

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

Key observations

  1. Website is a Norwegian government agency site focused on building quality and regulations.
  2. Content is comprehensive, well-structured, and professionally presented.
  3. No direct company emails or phone numbers found in the HTML; contact is via contact page.
  4. No explicit cookie consent banner detected despite use of tracking scripts.
  5. Security headers not explicitly visible in provided data; HTTPS is enforced.
  6. Use of Matomo analytics indicates privacy-conscious tracking compared to commercial alternatives.
  7. No visible security.txt or vulnerability disclosure page.
  8. No signs of WAF or blocking mechanisms; site fully accessible.
Technical notes

Notes

The website is built on a modern technology stack including jQuery, Bootstrap, RequireJS, and TinyMCE, integrated within the Episerver CMS platform. The site uses Foundation CSS media queries for responsive design, ensuring good mobile optimization and accessibility. Performance is moderate with deferred script loading and preloading of key assets. SEO is well addressed with proper meta tags, Open Graph data, and canonical links. No major technical debt or outdated libraries were detected. Opportunities exist to improve security headers and implement cookie consent mechanisms to align with best practices and regulatory requirements.
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 dibk.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 dibk.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.