Skip to main content

Security report for 22bet.com

22bet · Other · Germany

Medium risk. 5 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

74/100

Risk levelMedium

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

22bet is an international online gambling and sports betting platform established in 2017, offering a wide range of betting services including sports, casino, live casino, and esports. The website is currently restricted in certain countries such as Germany, displaying a country block message. The platform uses modern web technologies including JavaScript frameworks and integrates multiple third-party tracking and advertising services. However, the site lacks visible privacy and cookie policies, and security headers are not detected, indicating room for improvement in security and compliance. The domain registration is consistent and legitimate, with a long registration period and no privacy protection, appropriate for a commercial gambling business. Overall, the website's content is limited due to access restrictions, impacting user experience and trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
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

5 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. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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

      Third-party services without privacy policy

      Detected services: Google Analytics, Facebook

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

  3. 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 22bet.com

This scan found 19 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
77
Security headers
45
Email security
85
DNS health
85
Network security
100
GDPR outside view
50
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

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

22bet operates in the online gambling sector targeting adult users interested in sports betting and casino games. It maintains multiple regional domains to serve different markets, indicating a broad international presence. The business model relies on online betting revenue streams, supported by marketing through affiliate and advertising networks. The company provides customer support via email and phone, with physical office presence in Minsk, Belarus. The platform's competitive advantage includes a wide variety of betting options and integration with popular payment and identity verification systems. Growth indicators include regional domain expansions and active marketing partnerships.

Security posture

The security posture of 22bet shows basic maturity with HTTPS enabled and domain registration protections in place. However, the absence of DNSSEC and security headers such as Content-Security-Policy and X-Frame-Options reduces the overall security level. The site heavily relies on third-party scripts for tracking and advertising, which may introduce vulnerabilities if not properly managed. No explicit security policies or incident response contacts are found, which is a compliance gap. The website is currently blocked in some regions, which may be due to regulatory or licensing issues rather than security controls. Overall, the security posture is moderate but requires enhancements to meet best practices and regulatory compliance.

Recommendations

  1. Enable DNSSEC to enhance domain name system security and prevent DNS spoofing.
  2. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web vulnerabilities.
  3. Publish clear privacy and cookie policies with explicit GDPR compliance statements to improve transparency and legal compliance.
  4. Establish and publicize an incident response policy and contact channels to improve security readiness and customer trust.
  5. Regularly audit and minimize third-party scripts to reduce attack surface and improve site performance.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Website content is blocked in the detected region (Germany). The page shows a country block message: 'This website is not available in your country.' No WAF vendor-specific challenge detected but access is restricted. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Company
22bet
Description
22bet is an online betting company offering sports betting, casino games, and other gambling services. The website is currently restricted in certain countries and regions.
Key services
Sports betting, Casino games, Live casino, Esports betting
Content quality
basic
Branding
consistent

Technology

Stack
JavaScript, Google Tag Manager, Facebook Pixel, Sportradar tracking, Eskimi tracking, Netbrox analytics
Platforms
Web
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
50/100
Good practices seen
  • HTTPS enabled
  • Domain status includes clientDeleteProhibited and other EPP protections

Analytics and tracking

Services
Google Analytics (implied by GTM), Facebook Analytics, Netbrox, Sportradar
Tracking level
extensive
Privacy practices
poor

Advertising

Ad networks
TrafficJunky, Taboola
Tracking pixels
Facebook Pixel, Sportradar tracking, Eskimi tracking, Netbrox analytics, TrackingTraffo, LiftDSP
Marketing tools
Facebook Pixel, Sportradar Tag Manager
Transparency
basic

Site quality

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

Key observations

  1. Website is currently blocked in Germany and possibly other countries.
  2. No privacy policy, cookie policy, or terms of service pages detected in the HTML content.
  3. Contact information is limited to an email address and phone numbers mentioned in text but no dedicated contact page found.
  4. Heavy use of third-party tracking and advertising scripts.
  5. No explicit security policies or incident response information found.
  6. Website content is minimal due to access restrictions, limiting full analysis.
  7. Domain WHOIS data is consistent and shows no privacy protection.
  8. Website uses HTTPS but lacks DNSSEC and security headers.
  9. Content is gambling-related and intended for adult users only.
Technical notes

Notes

The website uses a modern JavaScript-based frontend likely built with Vue.js, supported by Google Tag Manager and Facebook Pixel for analytics and marketing. Multiple third-party advertising and tracking services are integrated, including Sportradar and Eskimi. The domain is registered with GoDaddy and uses multiple Cloud DNS servers without DNSSEC. Performance is moderate with asynchronous script loading but could be impacted by numerous external calls. Mobile optimization is basic, and accessibility features are minimal. SEO optimization is basic with meta tags present but no structured data or Open Graph tags detected. The site is currently blocked in some regions, limiting full technical evaluation.
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

Earlier scans of this domain

  1. 78/100Low24 findingsView report
Reviews of this site

Share your experience with 22bet.com. 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 22bet.com.

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.