Skip to main content

Security report for roobet.com

Roobet · Other · N/A

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

Security score

71/100

Risk levelMedium

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

Roobet is an online cryptocurrency casino platform positioning itself as one of the fastest growing in the crypto gambling market. The website offers crypto-based casino games targeting cryptocurrency users and online gamblers. The business model revolves around providing gambling services leveraging blockchain and crypto payments. Technically, the site is hosted on Cloudflare with integrations including Google Tag Manager, Seon fingerprinting for fraud prevention, and PaymentIQ for payment processing. The SSL certificate is valid but lacks modern TLS protocol support, which is a security concern. Security headers are well configured with HSTS enabled and preload, but the absence of privacy, cookie, and terms of service policies indicates compliance gaps. No contact or incident response information is provided, limiting transparency and trust. Overall, the site demonstrates moderate technical maturity but requires improvements in security posture and compliance documentation.

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

  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

      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

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

Keep watching roobet.com

This scan found 15 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
75
Security headers
45
Email security
90
DNS health
90
Network security
100
GDPR outside view
25
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

Technical appendix

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

Business context

Business profile

Roobet operates in the niche of crypto gambling, leveraging the growing interest in cryptocurrency for online gaming. Its market positioning as a fast-growing crypto casino suggests aggressive growth and user acquisition strategies. The business model likely generates revenue through casino game bets and possibly transaction fees. The use of third-party partners for payments and fraud prevention indicates a reliance on specialized services to manage operational risks. The absence of detailed company information and regulatory disclosures may impact trust with more cautious users. The platform targets crypto-savvy gamblers, a segment with specific regulatory and compliance challenges. Strategic partnerships with payment and security providers enhance operational capabilities but also introduce dependencies.

Security posture

The security posture of Roobet shows strengths in basic SSL implementation and security headers such as HSTS with preload, which protect against common web attacks. However, the lack of enabled TLS protocols (TLS 1.2 or 1.3) is a critical vulnerability that could expose users to insecure connections. The absence of privacy and cookie policies, terms of service, and incident response contacts indicates poor compliance with data protection regulations like GDPR. No DNSSEC is enabled, and CAA records appear malformed, reducing DNS security. The use of fingerprinting technology suggests advanced fraud detection but raises privacy concerns. Overall, the site has moderate security maturity but significant gaps in compliance and encryption standards.

Recommendations

  1. Enable and enforce modern TLS protocols (TLS 1.2 or TLS 1.3) to secure user connections.
  2. Publish comprehensive privacy, cookie, and terms of service policies with clear consent mechanisms.
  3. Provide clear contact information including incident response and data protection officer details.
  4. Implement DNSSEC and correct CAA records to enhance DNS security.
  5. Improve accessibility and SEO to enhance user experience and discoverability.
Technical notes

Notes

The website leverages Cloudflare for hosting and security, integrating third-party services such as Google Tag Manager for analytics, Seon for fingerprinting and fraud prevention, and PaymentIQ for payment processing. The tech stack includes Webflow as a CMS proxy. Performance is fast with good mobile optimization, but accessibility and SEO are basic. The SSL certificate is valid but no modern TLS protocols are enabled, which is a technical risk. DNSSEC is not enabled, and CAA records are malformed. The site uses multiple external domains for analytics and security services. No forms or social media links are present in the HTML content, limiting direct user engagement channels. Overall, the technical infrastructure is modern but requires updates to encryption protocols and compliance documentation.
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 roobet.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 roobet.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.