Skip to main content

Security report for lvbet.lv

Other · Latvia

Medium risk. 7 critical or high findings in GDPR outside view, Security headers and 2 other checks.

Security score

67/100

Risk levelMedium

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

The website lvbet.lv/casino/lv/ is an online casino platform targeting Latvian users, offering casino slots and live casino games. The site is built using modern frontend technologies including Angular and Webpack, with dynamic content loading indicated by skeleton loaders. The technical infrastructure appears moderately mature with some use of error tracking via Sentry. However, the site lacks visible privacy, cookie, and terms of service policies, as well as contact information, which impacts its compliance and trustworthiness. Security posture is moderate but could be improved by implementing security headers and stronger SSL configurations. WHOIS data is unavailable due to query limits, limiting domain legitimacy verification. Overall, the site is functional but requires enhancements in compliance, transparency, and security to improve trust and user confidence.

Scanned

NIS2 and GDPR posture

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

7 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

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

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

This scan found 22 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
55
Email security
80
DNS health
70
Network security
100
GDPR outside view
25
Average
67

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

Lvbet.lv operates in the online gambling sector, focusing on casino gaming services for the Latvian market. The business model revolves around providing digital casino slots and live dealer games. The platform targets adult online gamblers in Latvia, leveraging a modern web application framework for delivery. The absence of visible business registration, contact details, and compliance documentation limits transparency. The site likely generates revenue through player deposits and gaming activity. No clear partnerships or subsidiaries are identified from the data. Growth potential depends on regulatory compliance and market trust improvements.

Security posture

The security posture of the website is moderate. HTTPS is presumably enabled (given the URL scheme), but no explicit security headers were detected in the provided data. The site uses Sentry for error tracking, indicating some level of operational monitoring. However, the lack of visible privacy and cookie policies, absence of contact points for incident response, and missing security best practices such as CSP or X-Frame-Options headers represent compliance gaps. No vulnerabilities or exposed sensitive data were detected in the HTML content. The site should enhance its security framework and transparency to meet GDPR and industry standards.

Recommendations

  1. Implement and publish comprehensive privacy and cookie policies with GDPR compliance details.
  2. Add clear contact information including support emails and phone numbers for user and security incident reporting.
  3. Deploy and verify security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Perform WHOIS data verification and consider removing privacy protection if appropriate to increase trust.
  5. Enhance website accessibility and SEO metadata to improve user experience and search engine visibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Online casino platform offering casino slots and live casino games targeting Latvian market.
Key services
Casino slots, Live casino games
Content quality
basic
Branding
consistent

Technology

Stack
Angular (ng-version=19.0.6), Webpack, Sentry (error tracking), CSS variables, Custom fonts (Open Sans), JavaScript modules
Frameworks
Angular
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
50/100

Analytics and tracking

Services
Sentry
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Sentry
Transparency
poor

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. No visible privacy, cookie, or terms of service policies found in HTML content
  3. No contact emails, phone numbers, or physical addresses found
  4. Website uses Angular framework and modern frontend technologies
  5. No explicit security headers or SSL details available from provided data
  6. No visible certifications or compliance badges
  7. Content is mostly skeleton loaders indicating dynamic content loading
  8. No WAF or blocking detected, site content accessible
  9. Limited SEO metadata present, no description meta content
  10. No social media links or external contact points found
Technical notes

Notes

The website is built on Angular 19 with modular JavaScript and CSS variables for styling. It uses Webpack for bundling and includes Sentry for error monitoring. The site loads dynamic content with skeleton loaders, indicating asynchronous data fetching. Fonts are served via WOFF2 format for performance. No CMS or hosting provider information is evident. Performance is moderate with good mobile optimization. Accessibility features are basic, and SEO metadata is minimal. There is room for improvement in metadata completeness, accessibility compliance, and security header implementation.
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 lvbet.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 lvbet.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.