Skip to main content

Security report for lavash.lv

SIA LAVASH · Retail · Latvia

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

Security score

40/100

Risk levelHigh

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

Lavash.lv is an e-commerce platform based in Latvia specializing in bakery products such as lavash, pita, and matnakash, along with complementary grocery items including beverages, sweets, and meat products. The company targets general consumers and businesses like cafes and restaurants, offering next-day delivery across Latvian cities. The website is professionally designed with good navigation and mobile optimization, supporting multiple languages including Latvian, Russian, and Armenian. Technically, the site uses modern JavaScript libraries and secure HTTPS connections, with forms protected by CSRF tokens and input validation. However, there is no visible cookie consent mechanism or detailed security policy published. WHOIS data could not be retrieved due to query limits, limiting domain legitimacy verification. Overall, the site presents a trustworthy small retail business with room for improvement in privacy compliance and security transparency.

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

13 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

  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 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 lavash.lv

This scan found 28 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
65
DNS health
60
Network security
20
GDPR outside view
10
Average
40

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 lavash.lv, from OffSeq Breach.

No leaked records found

Breach holds no records for lavash.lv right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

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

Lavash.lv operates in the retail sector focusing on niche bakery and grocery products with Armenian cultural ties. Its business model is direct-to-consumer e-commerce with delivery services. The company participates in Latvian government digitalization programs, indicating growth and modernization efforts. Social media presence on Instagram and Facebook supports marketing and customer engagement. The absence of detailed WHOIS data and some compliance elements suggests a small to medium enterprise with potential to enhance trust signals. The product catalog and promotional offers indicate active inventory management and customer targeting strategies.

Security posture

The website enforces HTTPS and uses secure form practices including CSRF tokens and input validation, which are positive security indicators. However, the lack of security headers such as Content-Security-Policy and absence of published security or incident response policies represent gaps in security maturity. No vulnerabilities or exposed sensitive data were detected in the HTML content. The site would benefit from implementing a cookie consent mechanism and publishing a security policy to improve compliance and user trust. Incident response readiness and data protection officer contact information are not found, which could be a concern for GDPR compliance and breach management.

Recommendations

  1. Implement a comprehensive cookie consent banner to comply with GDPR and enhance privacy transparency.
  2. Publish a detailed security policy and incident response plan accessible to users.
  3. Add security headers like Content-Security-Policy, X-Frame-Options, and X-XSS-Protection to strengthen defense against common web attacks.
  4. Provide clear contact information for a Data Protection Officer or privacy contact to improve compliance and user confidence.
  5. Regularly monitor and update WHOIS information and consider publishing domain registration details to improve legitimacy and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
SIA LAVASH
Description
Lavash is an e-commerce platform specializing in bakery products such as lavash, pita, matnakash, and related food and beverage items including water, juices, sweets, and meat products. It offers delivery services across Latvian cities.
Key services
Online ordering of bakery and grocery products, Next day delivery in Latvia, Customer account management
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, Swiper.js, Bootstrap (modal dialogs), intl-tel-input (phone input formatting)
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Secure forms with CSRF tokens
  • Input validation on forms

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a Latvian e-commerce platform specializing in bakery and grocery products.
  2. Content is in Latvian language with options for Russian and Armenian.
  3. Multiple product categories with images and descriptions.
  4. Includes user account login and registration forms with validation.
  5. No WHOIS data available due to query limit error.
  6. No explicit cookie consent mechanism detected.
  7. Social media presence on Instagram and Facebook.
  8. No visible security.txt or vulnerability disclosure page.
  9. No explicit data protection officer contact found.
  10. No incident response or security policy pages found.
Technical notes

Notes

The website uses a modern JavaScript-based front end with libraries such as Swiper.js for carousels and intl-tel-input for phone input formatting. Bootstrap modals are used for dialogs. The site is mobile optimized and loads CSS and JS assets with versioning query parameters, indicating active maintenance. No CMS or hosting provider information is directly detectable. Performance appears moderate with room for optimization. Accessibility features are basic but present. SEO is supported by meta tags but could be enhanced with structured data and Open Graph tags, which are not found. The absence of analytics scripts suggests minimal user tracking, aligning with privacy considerations.
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 lavash.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 lavash.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.