Skip to main content

Security report for lujakatto.fi

Lujakatto Oy · Retail · Finland

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

Security score

56/100

Risk levelMedium

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

Lujakatto Oy is a Finnish company specializing in roofing products and installation services, offering a streamlined e-commerce platform where customers can order both products and installation with transparent pricing. The company targets Finnish homeowners and property managers, positioning itself as a niche regional provider with a focus on quality service and convenience. Technically, the website uses modern front-end technologies such as UIkit and jQuery, but lacks a valid SSL certificate, which impacts security and trust. The site is moderately performant and mobile-optimized, with clear navigation and good content relevance. Security posture is weak due to missing HTTPS and security headers, exposing the site to potential risks. Privacy policies and terms of service are present but basic, with no advanced compliance or incident response information. Overall, the domain registration data aligns well with the business claims, indicating legitimacy. Strategic improvements in security and privacy compliance are recommended to enhance trust and protect user data.

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

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

    • 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

  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 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 lujakatto.fi

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. 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
100
Security headers
45
Email security
70
DNS health
80
Network security
40
GDPR outside view
0
Average
56

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 company operates a combined product and service business model, selling roofing materials alongside installation services. Its market positioning is focused on Finnish residential and commercial roofing needs, leveraging an online platform for ordering and customer engagement. The presence of campaigns and social media activity suggests active marketing efforts. The business appears small in size with a clear local focus. The website content and structure support a professional image, though there is room for improvement in technical and security aspects. No evidence of partnerships or subsidiaries was found beyond the website builder service. The company maintains clear contact channels and legal registration information, supporting business credibility.

Security posture

The website currently lacks a valid SSL certificate, resulting in no HTTPS support, which is a critical security deficiency. No modern TLS protocols are enabled, and no security headers such as HSTS or Content-Security-Policy are present. OCSP stapling and session resumption are also disabled, reducing security and performance. No vulnerability disclosures or incident response contacts are provided. Privacy compliance is basic with a privacy policy present but no cookie consent mechanism. The absence of security best practices and critical security controls exposes the site and its users to risks such as data interception and trust issues. Immediate remediation of SSL/TLS and security headers is advised.

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 or TLS 1.3) and disable deprecated protocols.
  3. Implement security headers including HSTS, Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Add a cookie consent mechanism to improve privacy compliance and user trust.
  5. Establish and publish an incident response policy and contact channels for security issues.

Contact details published on the site

Addresses
Legal name
Lujakatto Oy
Registration number
3410559-9
Technical notes

Notes

The website uses a modern front-end stack with UIkit framework, jQuery, and htmx for dynamic content. Leaflet is used for map-related features. The CMS appears to be Kotisivutehdas, a Finnish website builder platform. DNS is managed by Euronic with no DNSSEC or CAA records enabled. Performance is moderate with a page load time of approximately 4 seconds and a page size of ~700 KB. Mobile optimization is good with responsive design elements. SEO is basic with minimal meta descriptions and keywords. No analytics or tracking scripts were detected in the provided content. The lack of HTTPS and security headers represents a significant technical risk. Hosting provider details are limited but DNS servers are located in Finland and Europe.
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 lujakatto.fi. 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 lujakatto.fi.

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.