Skip to main content

Security report for casinosincanada.com

CasinosInCanada.com · Hospitality · Canada

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

Security score

72/100

Risk levelMedium

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

CasinosInCanada.com is a specialized online platform dedicated to providing comprehensive information, reviews, and community engagement for Canadian online and land-based casino players. The site offers unique player protection services including a blacklist for dishonest casinos and a rating system based on real player reviews and RTP data. Technically, the site is built on Bitrix CMS, hosted on Google infrastructure, and uses modern web technologies including Google Tag Manager and reCAPTCHA for security. However, the SSL configuration lacks modern TLS protocol support and could be improved. Security headers are present but could be enhanced with HSTS and DNSSEC. The site demonstrates good content quality, user experience, and trust indicators such as Trustpilot integration and transparent affiliate disclosures. Overall, the platform holds a strong market position in the Canadian gambling information sector with a medium-sized operation and a focus on player safety and transparency.

Scanned

NIS2 and GDPR posture

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

4 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 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 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 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 casinosincanada.com

This scan found 16 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
60
Security headers
45
Email security
95
DNS health
85
Network security
90
GDPR outside view
58
Average
72

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

The platform targets Canadian casino players and international enthusiasts, providing a broad range of services including casino ratings, player reviews, blacklists, bonuses, guides, and community forums. Its business model relies on affiliate marketing partnerships with casinos and bonus providers, as well as community-driven content. The site emphasizes transparency and player protection, differentiating itself from competitors by not moderating or deleting negative reviews and offering compensation guarantees for trusted casinos. The presence of multiple affiliate domains indicates a robust partnership ecosystem. Growth indicators include a large volume of player reviews and active community engagement. The platform's strategic focus on trust and authenticity positions it well in a competitive market.

Security posture

The site exhibits a moderate security maturity level with several best practices implemented such as HttpOnly and SameSite cookie flags, no self-signed certificates, and absence of known SSL vulnerabilities. However, critical gaps exist including the lack of support for TLS 1.2 or higher, no HSTS policy, and absence of DNSSEC and CAA records. There is no publicly disclosed security policy or incident response information, which may impact user trust and regulatory compliance. The site uses Google reCAPTCHA to mitigate automated abuse. Overall, while basic security controls are in place, enhancements are needed to meet higher security standards and compliance requirements.

Recommendations

  1. Enable TLS 1.2 or higher protocols to secure data in transit effectively.
  2. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload to prevent protocol downgrade attacks.
  3. Configure DNSSEC and CAA records to improve domain security and control certificate issuance.
  4. Publish a security policy and incident response plan to enhance transparency and user trust.
  5. Add a security.txt file to facilitate vulnerability disclosure and improve security posture.
Technical notes

Notes

The website is powered by Bitrix Site Manager CMS running on an nginx server hosted on Google infrastructure. It uses Google Tag Manager and Google reCAPTCHA for analytics and security respectively. The site is optimized for mobile with good design and user experience. Performance is fast with no resource or page size issues reported. SEO is well addressed with meta tags and structured data (JSON-LD) for the website entity. However, the SSL configuration is outdated with no TLS protocols enabled, which poses a risk. The site uses multiple affiliate redirect domains indicating a complex affiliate marketing infrastructure. Overall, the technical infrastructure is solid but requires modernization in security protocols and DNS configurations.
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 casinosincanada.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 casinosincanada.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.