Skip to main content

Security report for e-boks.dk

e-Boks Group · Technology · Denmark

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

Security score

64/100

Risk levelMedium

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

e-Boks Group operates Denmark's leading digital mailbox platform, serving millions of users with secure digital post and document management services. The company is well-established, owned by reputable parent companies Nets and PostNord, and targets both private individuals and businesses. Their platform supports secure communication with public authorities and private entities, leveraging MitID for authentication and providing mobile app access for convenience. Technically, the website employs modern JavaScript frameworks and integrates Cookiebot for privacy compliance, but critically lacks a valid SSL certificate, exposing users to security risks. The absence of HTTPS and security headers significantly lowers the security posture score. Privacy policies and cookie consent mechanisms are comprehensive and GDPR compliant, reflecting a strong commitment to user privacy. Overall, the website is professionally designed with excellent content quality and user experience, but urgent improvements in SSL/TLS configuration and security headers are necessary to enhance trust and security.

Scanned

NIS2 and GDPR posture

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

7 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 e-boks.dk

This scan found 20 issues across 5 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
100
Security headers
15
Email security
85
DNS health
85
Network security
85
GDPR outside view
15
Average
64

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention e-boks.dk, from OffSeq Breach.

Total records
1,181
Employees
2
Customers
1,031
Third parties
148
Weak passwords
20%

Latest record dated 2026-05-15 · 12 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for e-boks.dk.

Select it in the checkout above.

Masked preview

  • –jira.e-boks.dk2026-05-15
  • –jira.e-boks.dk2025-11-02

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

e-Boks holds a dominant market position in Denmark's digital mailbox sector, with a large user base and extensive document throughput. Their business model revolves around providing secure digital communication channels for public and private sectors, monetized through service agreements with governmental bodies and enterprises. The company benefits from strong partnerships and a robust ecosystem of support domains and services. Growth indicators include a large monthly user visit count and ongoing investments in mobile and digital services. The platform's integration with MitID and Cookiebot demonstrates adherence to regulatory requirements and user trust. Strategic observations highlight the need to modernize security infrastructure to maintain competitive advantage and regulatory compliance.

Security posture

The current security maturity level is moderate to low due to the lack of a valid SSL certificate and absence of HTTPS enforcement, which is a critical vulnerability for any website handling sensitive user data. While authentication via MitID and cookie consent mechanisms are positive security practices, the missing TLS protocols, HSTS, OCSP stapling, and security headers expose the platform to potential man-in-the-middle attacks and reduce user trust. No evidence of incident response or vulnerability disclosure policies was found, indicating potential gaps in security governance. Compliance with GDPR is supported by comprehensive privacy and cookie policies. The business impact of these vulnerabilities is high given the sensitive nature of the services provided. Immediate remediation of SSL/TLS issues and implementation of security headers is recommended to improve the security posture.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across all domains.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable deprecated 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, X-Content-Type-Options, and Referrer-Policy.
  5. Establish and publish a vulnerability disclosure policy and security.txt file to improve transparency and incident response readiness.
Technical notes

Notes

The website uses a modern JavaScript stack including jQuery 3.7.0 and Cookiebot for cookie consent management. Hosting is managed via Cloudflare DNS and nameservers, indicating use of a CDN and potential security services. The CMS is likely Umbraco based on domain references. Performance is moderate with a page load time of approximately 5.9 seconds and a page size of ~193 KB, which is acceptable but could be optimized. Mobile optimization and accessibility are good, with responsive design and accessibility features evident. SEO is well addressed with proper meta tags and Open Graph data. However, the lack of SSL/TLS and security headers represents a significant technical debt and risk. Modernization of security infrastructure and performance tuning are recommended to enhance reliability and user trust.
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 e-boks.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 e-boks.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.