Skip to main content

Security report for jexen.dk

Skandiaweb A/S · Other · Denmark

High risk. 11 critical or high findings in GDPR outside view, Email security and 3 other checks.

Security score

30/100

Risk levelHigh

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

The website jexen.dk represents a small Danish web design and hosting service provider, Skandiaweb A/S, established in 2007. The site is built on an outdated Joomla 1.5 CMS platform with basic content and navigation primarily targeting local businesses or individuals seeking web services. The company appears to have a modest market position with a focus on web design and hosting. Technically, the site uses legacy JavaScript libraries and lacks modern security features such as HTTPS and security headers, which exposes it to potential vulnerabilities. The presence of a cookie consent banner indicates some awareness of privacy regulations, but the absence of a privacy policy and terms of service pages highlights compliance gaps. Analytics are handled via a self-hosted Piwik (Matomo) instance, suggesting some control over user data collection. Overall, the website's security posture is weak due to outdated software and missing HTTPS, and privacy compliance is minimal. Strategic improvements in security, privacy documentation, and technology modernization are recommended to enhance trust and compliance.

Scanned

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

11 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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  2. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

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

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

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

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

Keep watching jexen.dk

This scan found 23 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
0
Security headers
25
Email security
60
DNS health
75
Network security
20
GDPR outside view
0
Average
30

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

Skandiaweb A/S operates as a local web design and hosting provider in Denmark, leveraging Joomla CMS for client websites. The business model centers on service provision with a focus on small to medium-sized clients. The company maintains partnerships with related domains for hosting and analytics services, indicating an integrated service ecosystem. Growth indicators are limited from the website content, but the domain age and consistent WHOIS data support business legitimacy. The lack of visible social media presence or advanced marketing tools suggests a traditional or low-scale digital marketing approach. The company could benefit from expanding digital presence and updating technology to remain competitive.

Security posture

The security posture of jexen.dk is currently weak. The absence of HTTPS is a critical vulnerability that undermines data confidentiality and user trust. The use of Joomla 1.5 and old JavaScript libraries introduces known security risks due to lack of updates and patches. No security headers or incident response information are present, and no privacy policy is published, which may expose the company to regulatory risks under GDPR. The cookie consent mechanism is a positive aspect but insufficient alone. Incident response readiness and data protection officer contact details are missing, indicating immature security governance. Immediate remediation of HTTPS and CMS upgrades are essential to reduce risk.

Recommendations

  1. Implement HTTPS with a valid SSL/TLS certificate to secure all website traffic.
  2. Upgrade Joomla CMS to the latest supported version to mitigate known vulnerabilities.
  3. Publish a comprehensive privacy policy and terms of service to improve compliance and transparency.
  4. Update all JavaScript libraries to current secure versions and implement security headers (CSP, HSTS, X-Frame-Options).
  5. Establish and publish incident response procedures and designate a data protection officer contact.

Contact details published on the site

Addresses
Legal name
Skandiaweb A/S
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Skandiaweb A/S
Description
Website for a company providing web design and hosting services, created and hosted by Skandiaweb A/S based in Copenhagen, Denmark.
Key services
Web design, Web hosting, Content management
Content quality
basic
Branding
moderate

Technology

Stack
Joomla! 1.5, jQuery 1.4.2, MooTools, rokbox
Frameworks
Joomla
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
35/100
Good practices seen
  • Cookie consent banner implemented

Analytics and tracking

Services
Piwik (Matomo)
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Piwik (Matomo)
Transparency
basic

Site quality

Design
basic
User experience
basic
Content relevance
basic
Navigation
good
Professionalism
basic
Trustworthiness
moderate

Key observations

  1. Website uses outdated Joomla CMS version 1.5, which is no longer supported and may pose security risks.
  2. No privacy policy or terms of service pages found.
  3. Cookie consent banner is present and functional, indicating some GDPR awareness.
  4. Contact information includes phone and physical address in HTML comments but no email addresses visible.
  5. No HTTPS detected in provided data; site base URL is HTTP, which is a critical security concern.
  6. Use of Piwik (Matomo) analytics hosted on a related domain indicates some control over data collection.
  7. No social media links or email contacts found on the homepage.
  8. No security headers or advanced security mechanisms detected.
  9. Website content is minimal and mostly image-based with basic navigation.
  10. No forms detected on the homepage or in provided HTML content.
Technical notes

Notes

The website is built on Joomla 1.5 CMS, which is outdated and unsupported, posing significant security risks. The JavaScript stack includes jQuery 1.4.2 and MooTools, both old versions lacking modern security fixes. The site uses rokbox for image display and a custom cookie consent script. Hosting appears to be managed by Skandiaweb A/S, with analytics via a self-hosted Piwik instance on skandialytics.dk. Performance is moderate with basic mobile optimization and accessibility. SEO is minimal with basic meta tags but no structured data or Open Graph tags. The site lacks HTTPS, which is a major technical deficiency. Modernization of the tech stack and security hardening are recommended to improve 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 jexen.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 jexen.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.