Skip to main content

Security report for eol.lv

SIA "EOL" · Other · Latvia

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

Security score

44/100

Risk levelHigh

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

SIA "EOL" is a Latvian company specializing in the design, installation, and maintenance of low-voltage and security systems, including fire safety, video surveillance, voice announcement, and security alarm systems. The company targets businesses and organizations requiring professional security solutions and positions itself as a competent local service provider. The website is professionally designed using Joomla CMS with modern frameworks and libraries, ensuring a good user experience and mobile responsiveness. Security-wise, the site uses HTTPS and CSRF tokens but lacks visible security headers and formal privacy or cookie policies, indicating room for improvement in compliance and security posture. Overall, the website is safe, business-focused, and moderately mature digitally, with clear contact information and a professional presentation.

Scanned

NIS2 and GDPR posture

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

    • 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 eol.lv

This scan found 26 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
62
Security headers
20
Email security
75
DNS health
75
Network security
20
GDPR outside view
10
Average
44

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 in the security systems sector, offering a range of services from fire safety systems to video surveillance and security alarms. Its business model is service-oriented, focusing on installation and maintenance. The website content and structure suggest a small-sized enterprise with a local market focus in Latvia. The presence of Google Analytics and Tag Manager indicates some level of digital marketing and user behavior tracking. However, the absence of privacy and cookie policies may expose the company to compliance risks under GDPR. The company appears to maintain a consistent brand image and provides clear contact channels, which supports customer trust and engagement.

Security posture

The website enforces HTTPS and uses CSRF tokens for AJAX requests, which are positive security practices. However, the lack of security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security reduces the overall security posture. No vulnerability disclosures or incident response contacts are provided, limiting transparency in security management. The use of third-party libraries like jQuery and Bootstrap is standard but requires regular updates to mitigate vulnerabilities. The site does not expose sensitive data or show signs of vulnerabilities in the analyzed content. Overall, the security posture is moderate but could be significantly improved with better header implementation and compliance documentation.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie consent mechanism to improve GDPR compliance.
  2. Add essential security headers (CSP, HSTS, X-Frame-Options, X-Content-Type-Options) to enhance protection against common web attacks.
  3. Create and publish a vulnerability disclosure policy or security.txt file to improve transparency and incident response readiness.
  4. Include incident response contact information such as security@ or abuse@ email addresses to facilitate reporting of security issues.
  5. Regularly audit and update third-party libraries and CMS components to reduce the risk of known vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
SIA "EOL"
Description
SIA "EOL" piedavā vājstrāvu un drošības sistēmu projektēšanu, uzstādīšanu un apkalpošanu. Uzņēmumā strādā kompetenti un atsaucīgi darbinieki, kuri regulāri papildina savas zināšanas atbilstoši jaunākajām tehnoloģiju tendencēm.
Key services
Ugunsdrošības sistēmas (Fire safety systems), Evakuācijas plāni (Evacuation plans), Instrukciju izstrāde (Instruction development), Balss izziņošanas sistēmas (Voice announcement systems), Videonovērošanas sistēmas (Video surveillance systems), Apsardzes sistēmas (Security systems)
Content quality
good
Branding
consistent

Technology

Stack
jQuery, Bootstrap, Font Awesome, Google Fonts, Google Tag Manager, Google Analytics, SP Page Builder, Slider Pro
Frameworks
Helix3
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • CSRF token used in AJAX setup

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. WHOIS data unavailable due to query limit error; no registrar or domain age info.
  3. No privacy, cookie, or terms of service policies found on the website.
  4. Contact information is clearly presented including phone, email, and contact form.
  5. Website uses Joomla CMS with Helix3 framework and common JS libraries.
  6. HTTPS is enabled and CSRF tokens are implemented for AJAX forms.
  7. No explicit security headers detected in the HTML content.
  8. Google Analytics and Tag Manager are used for tracking.
  9. No vulnerability disclosure or incident response information provided.
  10. Content is business-focused and safe for general audiences.
Technical notes

Notes

The website is built on Joomla CMS using the Helix3 framework, with front-end technologies including jQuery, Bootstrap, Font Awesome, and Google Fonts. It integrates Google Analytics and Google Tag Manager for tracking. The site is mobile responsive and has a moderate performance profile. The use of CSRF tokens in AJAX requests indicates attention to security in form handling. However, the absence of advanced security headers and privacy compliance features suggests technical debt in security and compliance areas. Hosting provider details are not discernible from the content. The website structure and code quality appear good, but SEO and accessibility could be further enhanced.
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 eol.lv. 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 eol.lv.

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.