Skip to main content

Security report for lzvo.lv

LZVO · Healthcare · Latvia

Medium risk. 2 critical or high findings in Security headers and SSL/TLS.

Security score

71/100

Risk levelMedium

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

LZVO (Latvijas Zāļu verifikācijas organizācija) is a Latvian organization dedicated to ensuring the safety of medicines for all residents of Latvia by operating a pharmaceutical verification system aimed at preventing counterfeit medicines from reaching consumers. The website reflects a professional and authoritative presence with clear navigation and comprehensive information targeted at system users, manufacturers, IT suppliers, and the general public. The organization maintains compliance with GDPR and provides detailed cookie consent mechanisms, demonstrating a commitment to privacy and transparency. Technically, the website employs modern web technologies including Google Analytics, Google Tag Manager, Cookiebot for consent management, and Mapbox for mapping services. The site is mobile-optimized and uses HTTPS with a good SSL configuration, although explicit security headers are not evident in the HTML source. The content quality is good, with consistent branding and relevant healthcare industry focus. From a security perspective, the site shows good practices such as encrypted connections and cookie consent but lacks published incident response or security policies and security.txt files. No vulnerabilities or suspicious patterns were detected in the visible content. The absence of WHOIS data limits domain age and registrant verification, but the overall trust indicators and business information suggest legitimacy. Overall, LZVO's website is a well-structured, secure, and privacy-compliant platform serving an essential healthcare function in Latvia. Strategic improvements could include enhanced security headers, explicit incident response information, and WHOIS transparency to further strengthen trust and security posture.

Scanned

NIS2 and GDPR posture

GDPR outside view
88/ 100 · Low
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

2 findings rated critical or high. Fix these first.

  1. 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 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';…

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching lzvo.lv

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. 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
62
Security headers
65
Email security
85
DNS health
85
Network security
40
GDPR outside view
88
Average
71

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

No leaked records found

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

LZVO operates in the healthcare sector as a national pharmaceutical verification organization in Latvia. Its business model revolves around regulatory compliance and public safety by providing a system to verify medicines and prevent counterfeit distribution. The organization targets multiple stakeholders including system users, manufacturers, IT suppliers, and the general population. The website indicates medium organizational size with ISO certifications as trust signals. The presence of a LinkedIn profile and detailed cookie policies reflect a mature digital presence. The organization appears well-positioned within its niche market, focusing on compliance and education rather than commercial revenue streams. Partnerships and related domains like dev.lzvo.lv support its operational ecosystem.

Security posture

The website demonstrates a moderate to good security posture with HTTPS enforced and cookie consent mechanisms aligned with GDPR. However, the absence of explicit security headers such as Content Security Policy (CSP), HSTS, and X-Frame-Options is a notable gap. No security.txt or vulnerability disclosure policies are published, limiting transparency in incident response. The use of third-party scripts like Google Analytics and Mapbox introduces typical risks but appears managed through consent. No exposed sensitive data or vulnerabilities were detected in the HTML content. Overall, the security maturity is adequate for the organization's purpose but could be enhanced by adopting additional security best practices and publishing incident response contacts.

Recommendations

  1. Implement and enforce security headers including CSP, HSTS, and X-Frame-Options to mitigate common web attacks.
  2. Publish a security.txt file and vulnerability disclosure policy to improve transparency and incident response readiness.
  3. Provide explicit incident response contact information such as security@ or abuse@ email addresses on the website.
  4. Regularly audit and update third-party scripts and libraries to minimize vulnerabilities.
  5. Enhance accessibility features and conduct periodic security assessments to maintain compliance and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
LZVO
Description
Mēs rūpējamies par drošām zālēm visiem Latvijas iedzīvotājiem - verifikācijas sistēmas mērķis ir novērst viltotu zāļu izplatīšanas iespējas un nonākšanu pie patērētājiem
Key services
Medicine verification system, Alerts and warnings, Documentation and normative acts, Information for system users and manufacturers
Content quality
good
Branding
consistent

Technology

Stack
Google Analytics, Google Tag Manager, Cookiebot, Mapbox, Bootstrap, Swiper.js, Google Fonts
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

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

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Google
Marketing tools
Cookiebot
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 no blocking or WAF challenges.
  2. Strong cookie consent implementation with detailed cookie categories and third-party disclosures.
  3. Use of modern web technologies and analytics tools.
  4. Clear business focus on pharmaceutical verification and public safety.
  5. Contact information is limited but includes a verified phone number and LinkedIn profile.
  6. No visible security headers detected in HTML source; potential area for improvement.
  7. WHOIS data unavailable, limiting domain age and registrant verification.
  8. Privacy policy is comprehensive and GDPR compliant.
  9. No terms of service page explicitly found.
  10. No explicit security or incident response policies published.
Technical notes

Notes

The website uses a modern technology stack including Bootstrap for responsive design, Swiper.js for sliders, Google Fonts for typography, and Cookiebot for cookie consent management. Analytics are handled via Google Analytics and Google Tag Manager, with Mapbox providing mapping services. The site is served over HTTPS with a valid SSL certificate, ensuring encrypted communications. Performance is moderate with room for optimization. The CMS is not explicitly identified, suggesting a custom or less common platform. Accessibility is basic but functional. SEO is supported by proper meta tags and Open Graph data. The site architecture supports clear navigation and user experience. Technical risks include the lack of security headers and limited WHOIS transparency.
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 lzvo.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 lzvo.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.