Skip to main content

Security report for toender.dk

Tønder Kommune · Government · Denmark

Low risk. 3 critical or high findings in Security headers and SSL/TLS.

Security score

77/100

Risk levelLow

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

Tønder Kommune operates as the official municipal government website for the Tønder region in Denmark, providing residents and stakeholders with access to municipal services, public information, and citizen support. The website is positioned as a local government authority, serving a medium-sized audience within the government sector. The digital presence is built on modern web technologies including Nuxt.js, with a focus on accessibility, mobile optimization, and SEO best practices. The site implements a comprehensive cookie consent mechanism aligned with GDPR requirements, reflecting a mature approach to privacy compliance. However, the absence of WHOIS data limits the ability to fully verify domain registration legitimacy. Security posture is moderate, with HTTPS implied but lacking explicit security headers and published security policies. Overall, the website presents a professional and trustworthy interface suitable for its governmental role.

Scanned

NIS2 and GDPR posture

GDPR outside view
83/ 100 · Low
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

3 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 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';…

  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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching toender.dk

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. 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
77
Security headers
60
Email security
70
DNS health
70
Network security
100
GDPR outside view
83
Average
77

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 serves as a critical communication and service platform for Tønder Municipality, targeting residents and local stakeholders. Its business model is that of a government service provider, focusing on delivering essential municipal services and information. The site integrates multiple subdomains representing various municipal departments, indicating a structured internal ecosystem. While no direct revenue streams or commercial activities are evident, the site supports public administration functions. The use of a reputable cookie consent provider and SiteImprove analytics suggests a commitment to transparency and data-driven improvements. The lack of visible contact information and security policies may be areas for enhancement to strengthen stakeholder trust and engagement.

Security posture

The security maturity of the website is moderate. HTTPS is enforced as indicated by canonical URLs, and a cookie consent banner is implemented to comply with privacy regulations. However, no explicit security headers (such as Content Security Policy, HSTS, or X-Frame-Options) were detected in the provided data. There is no evidence of a published security policy, incident response plan, or vulnerability disclosure program. The site uses third-party scripts like SiteImprove for analytics, which are common but require ongoing monitoring for vulnerabilities. The absence of contact channels for security incidents and lack of security.txt file reduces the site's readiness for incident response. Overall, while basic security practices are in place, there is room for improvement in formalizing security governance and technical defenses.

Recommendations

  1. Implement and verify HTTP security headers including CSP, HSTS, and X-Frame-Options to enhance protection against common web attacks.
  2. Publish a clear security policy and incident response contact information to improve transparency and readiness.
  3. Establish a vulnerability disclosure program or security.txt file to facilitate responsible reporting of security issues.
  4. Audit all third-party scripts regularly to ensure they do not introduce vulnerabilities or privacy risks.
  5. Enhance contact information visibility, including official emails and phone numbers, to improve user trust and support.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Tønder Kommune
Description
Official website of Tønder Municipality providing information and services to residents and visitors.
Key services
Municipal services, Public information, Citizen support
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, CSS, HTML, CookieInformation consent management
Frameworks
Nuxt.js
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enforced (implied by canonical URL)
  • Cookie consent mechanism implemented

Analytics and tracking

Services
SiteImprove
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
SiteImprove
Marketing tools
CookieInformation consent management
Transparency
good

Site quality

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

Key observations

  1. Website is an official Danish municipal government site.
  2. Comprehensive cookie consent mechanism is implemented.
  3. No WHOIS data available to verify domain registration details.
  4. No contact emails or phone numbers explicitly found in provided HTML.
  5. No terms of service or explicit security policy pages detected.
  6. Use of modern JavaScript framework (Nuxt.js) and good SEO practices.
  7. No signs of adult or questionable content.
  8. External domains mostly subdomains of toender.dk indicating internal services.
Technical notes

Notes

The website is built using modern web technologies, notably the Nuxt.js framework, which supports server-side rendering and improved SEO. The site includes extensive CSS and JavaScript assets, with a focus on responsive design and accessibility. Cookie consent is managed via a third-party service (CookieInformation), ensuring GDPR compliance. Performance appears moderate, with many preloaded scripts and stylesheets indicating a complex but optimized frontend. No CMS was explicitly detected, suggesting a custom or framework-based solution. Hosting provider details are not available from the provided data. Technical risks include the absence of explicit security headers and potential dependency on third-party scripts without visible mitigation controls.
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 toender.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 toender.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.