Skip to main content

Security report for lauri.lv

Lauru dārzi · Retail · Latvia

Medium risk. 9 critical or high findings in GDPR outside view, Email security and 2 other checks.

Security score

59/100

Risk levelMedium

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

Lauru dārzi is a small local retail business based in Latvia specializing in the sale of gardening products such as flower pots, Samteņu seedlings, and cucumbers. The website provides basic product pricing and contact information, targeting local customers interested in gardening supplies. The business appears to have been founded in 2021 and operates primarily through direct retail sales. The website is built using the Webnode CMS platform and is hosted on AWS Cloudfront CDN, indicating a modern but basic technical infrastructure. Google Tag Manager is used for analytics and tracking, but no advanced frameworks or e-commerce platforms are detected. Security posture is moderate with HTTPS enabled, but lacks important security headers and privacy policy documentation. Contact information is limited to a phone number and physical location, with no email or social media presence found. Overall, the website is functional but basic, with room for improvement in privacy compliance and security best practices.

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

9 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. 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. 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 lauri.lv

This scan found 25 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
72
Security headers
35
Email security
60
DNS health
75
Network security
100
GDPR outside view
10
Average
59

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 retail sector focused on gardening products, serving a local Latvian market. Its competitive advantage lies in direct sales of specific plant-related products at affordable prices. The business model is straightforward retail without e-commerce capabilities. The website content and structure suggest a small-scale operation with limited digital maturity. There is no evidence of partnerships or subsidiaries. Growth indicators are not visible, and the company does not display certifications or trust badges. The partnership ecosystem includes Webnode as the CMS provider and AWS Cloudfront for hosting. Strategic observations include the need to enhance online presence, add privacy and security policies, and improve contact channels to build customer trust.

Security posture

The website demonstrates a basic security posture with HTTPS enabled, ensuring encrypted communication. However, the absence of security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security reduces protection against common web attacks. No vulnerabilities or exposed sensitive data were detected in the analysis. The lack of privacy policy and incident response information indicates compliance gaps, particularly with GDPR requirements. The use of Google Tag Manager introduces moderate tracking but without clear privacy disclosures. Incident response readiness and security culture indicators are not evident. Overall, the security maturity is low to moderate, suitable for a small retail site but requiring improvements to meet best practices and regulatory compliance.

Recommendations

  1. Implement a comprehensive privacy policy page to improve GDPR compliance and user trust.
  2. Add essential security headers (CSP, X-Frame-Options, HSTS) to enhance website security.
  3. Provide clear contact information including a company email address for customer and security inquiries.
  4. Establish terms of service and incident response contact details to improve transparency and preparedness.
  5. Regularly audit third-party scripts and tracking tools to ensure they do not introduce vulnerabilities or privacy risks.

Contact details published on the site

Addresses
Legal name
Lauru dārzi
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Lauru dārzi
Description
Retail business selling flower pots, seedlings, and cucumbers with pricing and contact information provided.
Key services
Sale of flower pots, Sale of Samteņu seedlings, Sale of cucumbers
Content quality
basic
Branding
moderate

Technology

Stack
JavaScript, CSS, Google Tag Manager
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
70/100
Good practices seen
  • HTTPS enabled
  • No exposed sensitive data

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. WHOIS data unavailable due to query limit error
  2. Website is a small local retail business focused on gardening products
  3. No privacy policy or terms of service pages found
  4. Cookie consent mechanism present with moderate confidence
  5. HTTPS is enabled and content loads fully without blocking
  6. Uses Webnode CMS and AWS Cloudfront CDN
  7. Google Tag Manager is used for analytics and tracking
  8. No contact email found, only a phone number and physical location
  9. No security headers detected in provided data
  10. Content is safe and suitable for general audiences
Technical notes

Notes

The website is built on the Webnode CMS platform and uses AWS Cloudfront as a CDN for static content delivery, which supports good performance and availability. The technology stack includes standard web technologies such as HTML, CSS, and JavaScript, with Google Tag Manager integrated for analytics. The site is mobile optimized with responsive design elements. However, the site lacks advanced frameworks or modern JavaScript libraries. SEO optimization is basic with meta tags and Open Graph tags present but no structured data like JSON-LD. Accessibility features are minimal. Performance is moderate, with no evident critical technical debt but opportunities exist for modernization and enhanced security configurations.
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 lauri.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 lauri.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.