Skip to main content

Security report for betsafe.com.au

BetSafe Pty Ltd · Other · Australia

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

Security score

69/100

Risk levelMedium

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

BetSafe Pty Ltd operates a responsible gambling program primarily serving gaming venues and individuals in New South Wales and the Australian Capital Territory. Founded in 1998 by Paul Symond, the company offers a comprehensive suite of services including gambling counselling, self-exclusion programs, and consultancy services. The website positions BetSafe as a leading program in its sector with a long operational history and a membership base of over 80 venues. The business model focuses on providing support and compliance solutions to the gambling industry and affected individuals. Technically, the website is built using basic HTML, CSS, and JavaScript without modern frameworks or CMS detected. The site is accessible with no WAF or blocking mechanisms, but lacks advanced technical features such as security headers, cookie consent mechanisms, or analytics integrations. Mobile optimization and accessibility are basic, and performance is moderate. SEO is reasonably addressed through meta tags and structured navigation. From a security perspective, the site does not expose sensitive data and does not have visible vulnerabilities in the provided HTML. However, there is no explicit evidence of HTTPS enforcement or security headers, which lowers the security posture score. Privacy compliance is partially met with a privacy policy present but no cookie consent or GDPR indicators. Contact information is minimal, reducing trust signals. Overall, the site is legitimate and professional but could improve security and privacy practices. The overall risk assessment is moderate with no critical issues detected. Strategic recommendations include implementing HTTPS with strong SSL/TLS, adding security headers, introducing cookie consent mechanisms, enhancing contact transparency, and publishing a vulnerability disclosure policy to improve trust and compliance.

Scanned

NIS2 and GDPR posture

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

  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 SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching betsafe.com.au

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
75
Security headers
40
Email security
85
DNS health
60
Network security
100
GDPR outside view
53
Average
69

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

BetSafe holds a strong market position as a specialized responsible gambling program in Australia, targeting gaming venues and individuals affected by gambling issues. Its competitive advantage lies in its long history, independent evaluations, and comprehensive service offerings including counselling and self-exclusion. The business model is service-oriented, relying on memberships and consultancy engagements. Growth indicators include an expanding membership base and ongoing program development. The partnership ecosystem is limited in public data, with no identified subsidiaries or parent companies. The company maintains a focused operational scope with a clear mission in the gambling support sector.

Security posture

The security maturity level of the BetSafe website is moderate. While no immediate vulnerabilities or exposed sensitive data are evident, the absence of HTTPS confirmation and security headers represents a gap in best practices. There is no visible incident response or security policy documentation, and no contact channels for security issues are provided. Data protection practices are partially addressed through a privacy policy, but cookie consent and GDPR compliance indicators are missing. The security culture appears basic, with room for improvement in transparency and technical safeguards. The business impact of current gaps is moderate, primarily affecting user trust and regulatory compliance.

Recommendations

  1. Implement and enforce HTTPS with a valid SSL/TLS certificate to secure all website traffic.
  2. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web attacks.
  3. Introduce a cookie consent mechanism to comply with privacy regulations and enhance user trust.
  4. Publish clear contact information including security incident response contacts and enhance transparency with a security policy page.
  5. Develop and publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting and improve security posture.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
BetSafe Pty Ltd
Description
BetSafe is a responsible gambling program developed in 1998 by Paul Symond, considered a leading program with over 80 gaming venues in NSW and ACT. It offers resources, counselling, self-exclusion services, and consultancy.
Key services
Responsible gambling program membership, Online self-exclusion, Gambling counselling, Consultancy services
Content quality
good
Branding
consistent

Technology

Stack
HTML, CSS, JavaScript
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
good

Security

Observed score
50/100
Good practices seen
  • No visible forms collecting sensitive data on homepage
  • No exposed sensitive data in HTML

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

Design
basic
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is focused on responsible gambling programs and support services in Australia.
  2. No direct contact emails or phone numbers found on homepage or footer.
  3. Privacy policy is present and linked in footer.
  4. No cookie consent mechanism detected.
  5. No visible forms on homepage; forms may exist on subpages.
  6. No social media links detected.
  7. No security headers or advanced security configurations visible in HTML content.
  8. Website uses basic HTML, CSS, and JavaScript with no modern frameworks detected.
  9. No analytics or tracking scripts detected in provided HTML.
  10. No advertising or affiliate marketing detected.
Technical notes

Notes

The website uses a simple technology stack consisting of HTML, CSS, and JavaScript without modern frameworks or CMS platforms. The site structure is straightforward with linked CSS and JS files hosted on the same domain. Performance is moderate with no advanced optimization detected. Mobile optimization and accessibility are basic but functional. SEO is supported by meta tags and clear navigation menus. There is no evidence of third-party analytics, advertising, or tracking scripts in the provided HTML. The hosting provider and infrastructure details are not discernible from the data. Technical risks include outdated technology use and lack of modern security features.
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 betsafe.com.au. 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 betsafe.com.au.

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.