Skip to main content

Security report for lidl.lt

LIDL Lietuva · Retail · Lithuania

Medium risk. 4 critical or high findings in GDPR outside view and DNS health.

Security score

74/100

Risk levelMedium

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

LIDL Lietuva operates as a large retail supermarket chain in Lithuania, offering weekly promotions and a variety of food and non-food products. The website is professionally designed with a modern frontend technology stack including Vue.js, and it provides comprehensive privacy and cookie consent mechanisms compliant with GDPR. However, the absence of WHOIS data and explicit contact or security incident information limits the ability to fully verify domain legitimacy and security posture. The website employs HTTPS and tracking tools such as Google Analytics and Kameleoon, indicating a mature digital infrastructure. Security best practices are partially implemented, but the lack of security headers and vulnerability disclosure information suggests room for improvement. Overall, the website presents a trustworthy and professional retail presence with moderate technical and security maturity.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
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

4 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

      Third-party services without privacy policy

      Detected services: Facebook, LinkedIn, YouTube

      What to do: Document all third-party data sharing in your privacy policy

  2. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • High

      Weak SPF Policy

      SPF record has permissive policy allowing any server to send email

      What to do: Use -all or ~all qualifier for better email security

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

Keep watching lidl.lt

This scan found 18 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
100
Security headers
80
Email security
75
DNS health
50
Network security
100
GDPR outside view
40
Average
74

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 lidl.lt, from OffSeq Breach.

No leaked records found

Breach holds no records for lidl.lt 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

LIDL Lietuva holds a strong market position as a major retail supermarket chain targeting Lithuanian consumers. Its business model focuses on weekly promotional catalogs and a broad product range. The company leverages digital tools for marketing and analytics, including cookie consent management and A/B testing platforms. While the website content and branding are consistent and professional, the lack of publicly available WHOIS and contact details may impact perceived transparency. The company appears to prioritize privacy compliance and user experience, but could enhance trust by publishing more detailed business and security information.

Security posture

The website enforces HTTPS and uses cookie consent tools to comply with privacy regulations, reflecting a good baseline security posture. However, no explicit security headers (such as CSP, HSTS, or X-Frame-Options) were detected in the HTML content, which could expose the site to certain web-based attacks. The absence of a published security policy, incident response contacts, or vulnerability disclosure program indicates limited transparency in security governance. No vulnerabilities or exposed sensitive data were found in the analyzed content. Overall, the security posture is moderate but could be strengthened by adopting additional security headers and publishing security-related policies and contacts.

Recommendations

  1. Implement and publish comprehensive security headers including Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options.
  2. Publish a clear security policy and incident response contact information on the website.
  3. Establish and publicize a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  4. Improve WHOIS registration transparency to enhance domain trustworthiness.
  5. Add explicit company contact information including emails and phone numbers to improve business credibility and user trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
LIDL Lietuva
Description
Kviečiame peržiūrėti aktualius kainų leidinius, pasiūlymus ir akcijas. Maisto prekių pasiūlymai ir naujos ne maisto prekės kiekvieną savaitę.
Key services
Weekly promotions, Food and non-food product sales, Digital catalogs
Content quality
good
Branding
consistent

Technology

Stack
Vue.js 2.6.14, Google Tag Manager, OneTrust Cookie Consent, Kameleoon A/B Testing
Frameworks
Vue.js
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Cookie consent with opt-in/out
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics, Kameleoon
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Kameleoon
Marketing tools
OneTrust Cookie Consent, Kameleoon
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with rich content in Lithuanian
  2. Strong privacy and cookie consent mechanisms implemented
  3. No explicit contact or security incident information found
  4. WHOIS data unavailable, limiting domain trust analysis
  5. Modern frontend technology stack used (Vue.js)
  6. No WAF or blocking detected
  7. No visible security headers in HTML source
  8. No email addresses or phone numbers explicitly found in HTML
  9. No social media links explicitly found in HTML content provided
Technical notes

Notes

The website uses a modern frontend framework (Vue.js 2.6.14) and integrates multiple third-party scripts for analytics (Google Analytics), consent management (OneTrust), and A/B testing (Kameleoon). The site is mobile-optimized and includes accessibility features. Performance is moderate based on script usage and content complexity. No CMS or hosting provider information was detected from the HTML content. The site uses structured data (JSON-LD) for organization branding and SEO. Technical debt appears low, but the absence of security headers and WHOIS transparency are notable risks. Opportunities exist to enhance security and transparency to align with best practices.
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 lidl.lt. 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 lidl.lt.

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.