Skip to main content

Security report for realsbet.com

Other · Brazil

Medium risk. 15 critical or high findings in Email security, DNS health and 4 other checks.

Security score

52/100

Risk levelMedium

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

The website reals.bet.br is currently inaccessible due to a Cloudflare-based location restriction, displaying a message that the service is not available in the visitor's location. The site appears to be related to online gambling or betting, as inferred from the domain and minimal textual content. Due to the blocking, no substantive business information, contact details, or policies are available for review. The technical infrastructure includes Cloudflare as a CDN and security provider, but no further technology stack details or CMS information can be determined. The security posture cannot be fully assessed given the lack of accessible content and headers. Overall, the site shows minimal digital maturity and lacks transparency in privacy and compliance documentation.

Scanned

NIS2 and GDPR posture

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

15 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. DNS health

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

    • Critical

      DNS Resolution Failed

      Unable to resolve domain A records

      What to do: Verify domain is properly configured and not expired

  3. 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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • 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';…

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

Keep watching realsbet.com

This scan found 31 issues across 7 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
57
Security headers
15
Email security
60
DNS health
45
Network security
100
GDPR outside view
35
Average
52

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 realsbet.com, from OffSeq Breach.

Total records
39,139
Employees
1
Customers
39,117
Third parties
21
Weak passwords
8%

Latest record dated 2025-07-20 · 16 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for realsbet.com.

Select it in the checkout above.

Masked preview

  • –wallet.realsbet.com2025-07-20

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)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

Given the domain and content, the business likely operates in the online gambling sector targeting Brazilian users, but enforces geo-restrictions possibly due to regulatory compliance. The absence of visible business or contact information limits assessment of market positioning or partnerships. The business model is presumably based on online betting services. No evidence of certifications, trust signals, or customer engagement mechanisms was found. The domain registration is consistent with a legitimate entity but lacks detailed registrant data.

Security posture

The security posture is difficult to evaluate due to the site being blocked by Cloudflare's WAF with a location-based access denial. No security headers or SSL details were available. The presence of Cloudflare suggests some level of security hardening. However, the absence of privacy policies, cookie consent, or incident response information indicates gaps in compliance and transparency. No vulnerabilities or exposed sensitive data were detected, but the analysis is limited by the blocked content.

Recommendations

  1. Implement a publicly accessible landing page with basic business and compliance information to improve transparency.
  2. Publish privacy and cookie policies with GDPR compliance details to enhance user trust and legal adherence.
  3. Provide clear contact information including support and security incident channels.
  4. Review and optimize WAF rules to allow access to non-restricted content for legitimate users and security assessments.
  5. Conduct a comprehensive security audit including SSL configuration and security headers implementation.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. Site content is blocked by Cloudflare with a location-based access denial message and embedded Cloudflare challenge scripts. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor

Technology

Stack
Cloudflare

Analytics and tracking

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is inaccessible due to location-based blocking by Cloudflare.
  2. No privacy, cookie, or terms of service policies found on the landing page.
  3. No contact information or business details are publicly available on the site.
  4. The site appears to be a gambling/betting platform based on domain and keywords but is blocked in the current location.
  5. No forms, social media links, or analytics scripts detected in the HTML content.
  6. Minimal HTML content with only a message indicating service unavailability.
  7. Cloudflare is used as a security and CDN provider.
  8. No security headers or SSL configuration details available from provided data.
Technical notes

Notes

The website uses Cloudflare for DNS and security services, indicating a modern approach to hosting and protection. However, the HTML content is minimal and lacks meta tags, structured data, or analytics scripts. No CMS or frameworks were detected. The site is not mobile-optimized or SEO-friendly based on the limited content. Performance and accessibility cannot be assessed due to content blocking. There is an opportunity to modernize the site with better content delivery, SEO, and compliance features once access restrictions are addressed.
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 realsbet.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 realsbet.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.