Skip to main content

Security report for fm.dk

Finansministeriet · Government · Denmark

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

Security score

53/100

Risk levelMedium

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

Finansministeriet is the official Danish Ministry of Finance, providing authoritative information on government financial policies, economic agreements, and public sector finances. The website serves a broad audience including Danish citizens, government officials, and media, offering news, publications, and career information. The site is well-branded and professionally maintained, reflecting its government status. Technically, the site uses modern web technologies and the Umbraco CMS, but suffers from slow load times and lacks HTTPS, which is a critical security flaw. Privacy compliance is strong, with a comprehensive privacy policy and cookie consent mechanism implemented via Cookiebot. Security posture is weak due to the absence of SSL/TLS and security headers, exposing users to risks. Overall, the site is trustworthy and authoritative but urgently needs to address its SSL/TLS and security configuration to protect visitors and maintain credibility.

Scanned

This is an earlier scan of fm.dk. View the latest report

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

8 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

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

  2. 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';…

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

Keep watching fm.dk

This scan found 21 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
85
Security headers
15
Email security
50
DNS health
70
Network security
100
GDPR outside view
0
Average
53

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 Ministry operates as a government entity focused on financial governance and policy dissemination. Its market position is unique as the official source for Danish financial information. The business model is public service, funded by the government, with no commercial revenue streams. The site supports transparency and citizen engagement through news, reports, and contact channels. Partnerships with other government agencies and external service providers like Sitnet and Cookiebot are evident. Growth indicators include active content updates and digital engagement via social media. Strategic observations highlight the need for improved technical infrastructure to enhance user trust and security.

Security posture

The current security maturity is low due to the lack of HTTPS and modern TLS protocols, which are fundamental for secure communications. While SPF and DMARC records are properly configured, the absence of SSL/TLS exposes the site to interception and man-in-the-middle attacks. No security headers or incident response information are publicly available, indicating gaps in security best practices and transparency. The site uses Cookiebot for GDPR-compliant cookie consent, reflecting good privacy practices. Immediate remediation of SSL/TLS and implementation of security headers are critical to elevate the security posture and protect user data.

Recommendations

  1. Install and maintain 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) to enforce HTTPS usage.
  4. Add essential security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  5. Publish a clear security policy and incident response contact information to improve transparency and trust.

Contact details published on the site

Addresses
Legal name
Finansministeriet
Registration number
CVR: 10108330
Technical notes

Notes

The website is built on the Umbraco CMS platform and uses JavaScript libraries including Cookiebot for cookie consent and Cludo for search functionality. Hosting is managed by Sitnet, as indicated by DNS and MX records. Performance is suboptimal with a load time exceeding 14 seconds, likely due to resource count and page size. The site is mobile-optimized and accessible, with good SEO practices including meta tags and Open Graph data. However, the lack of HTTPS and modern security configurations represents significant technical debt and risk. Modernizing the SSL/TLS setup and optimizing resource loading would improve both security and user experience.
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. 75/100Medium28 findingsView report
Reviews of this site

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

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.