Instant cyber security rating
Casino Games

To get a deeper insight into your entire organization, including surfacing data leaks and identity breaches, as well as your third-party vendors, book a free demo today.

Get a demo
Free trial

Last scanned: 2026-07-14

Powered by Breach Risk

Security Rating

UpGuard's Cyber Security Ratings range from 0 to 950. The higher the score, the better the security practices on the primary domain for Casino Games.

Website Security

  • X-Powered-By header exposed

    The X-Powered-By header reveals information about specific technology used on the server. This information can be used to exploit vulnerabilities. The server configuration should be changed to remove this header.

  • X-Frame-Options is not deny or sameorigin

    Browsers may display this website's content in frames. This can lead to clickjacking attacks.

  • CSP implemented unsafely

    The Content Security Policy may not restrict sources appropriately, or may contain 'unsafe-inline' without the use of a nonce or hash. This increases the risk of XSS attacks.

  • X-Content-Type-Options is not nosniff

    Browsers may interpret files as a different MIME type than what is specified in the Content-Type HTTP header. This can lead to MIME confusion attacks.

  • Secure cookies used

    Using secure cookies reduces the risk of third parties intercepting information contained in these cookies.

  • Server information header not exposed

    Ensuring the server information header is not exposed reduces the ability of attackers to exploit certain vulnerabilities.

  • CSP implemented without insecure active sources

    The Content Security Policy does not allow any insecure active sources.

  • HttpOnly cookies used

    Using HttpOnly cookies reduces the risk of client side script attacks, by preventing cookies being read on the client.

  • Referrer policy is not unsafe-url

    The website's Referrer Policy is not configured to allow unsafe information to be sent in the referrer header.

  • ASP.NET version header not exposing specific ASP.net version

    Ensuring the ASP.NET version header is not exposing a specific version makes it harder for attackers to exploit certain vulnerabilities.

  • ASP.NET version header not exposed

    Ensuring the ASP.NET version header is not exposed makes it harder for attackers to exploit certain vulnerabilities.

  • CSP implemented without insecure passive sources

    The Content Security Policy does not allow any insecure passive (img/media) sources.

  • CSP implemented without unsafe-eval

    A Content Security Policy is implemented to help protect against XSS and clickjacking attacks.

  • No unmaintained page detected

    The page appears to be maintained.

Email

  • DMARC policy is p=none

    DMARC policy is p=none. This provides no protection against fraudulent emails. The DMARC policy should be migrated to p=quarantine, and eventually p=reject.

  • SPF policy uses ~all

    Sender Policy Framework (SPF) record is too lenient as to which domains are allowed to send email on the domain's behalf. This record should preferably not use the ~all mechanism, as this does not instruct the mail receiver to reject messages from unauthorised sources. When DMARC is not being enforced, -all should be used on the SPF record.

  • DMARC policy exists

    DMARC protects against fraudulent emails being sent from a domain.

  • SPF enabled

    Sender Policy Framework (SPF) records prevent spammers from sending messages with forged addresses.

  • SPF syntax correct

    Sender Policy Framework (SPF) record passes basic syntax checks.

  • SPF ptr mechanism not used

    Sender Policy Framework (SPF) record does not include the ptr mechanism.

Network

  • 'HTTP' port open

    The 'HTTP' service is running and exposed to the internet. The configuration of the server should be reviewed and unnecessary ports closed.

DNS

  • DNSSEC not enabled

    DNSSEC records prevent third parties from forging the records that guarantee a domain's identity. DNSSEC should be configured for this domain.

  • CAA not enabled

    The domain does not contain a valid Certification Authority Authorization (CAA) record. A CAA record indicates which Certificate Authorities (CAs) are authorized to issue certificates for a domain.

  • No unregistered MX records detected

    No unregistered MX records that could lead to receiving mail on behalf of the target organization were detected.

  • No subdomain takeover vulnerability detected

    No dangling DNS records that could lead to subdomain takeover were detected.

Encryption

  • HTTP Strict Transport Security (HSTS) not enforced

    Without HSTS enforced, people browsing this site are more susceptible to man-in-the-middle attacks. The server should be configured to support HSTS.

  • Insecure SSL/TLS versions available

    Any version of the SSL protocol, and TLS prior to version 1.2, are now considered insecure. The server should disable support for these old protocols.

  • Weak cipher suites supported in TLS 1.2

    Weak cipher suites can potentially be broken by a well resourced attacker, and should not be supported by the server unless very old devices or browsers must be supported.

  • Certificate not found on our revoked certificate list

    The site's certificate chain was checked against our list of revoked certificates.

  • SSL available

    SSL is supported for this site.

  • HTTP requests are redirected to HTTPS

    All HTTP requests are redirected to HTTPS.

  • Hostname matches SSL certificate

    The site's hostname matches the SSL certificate.

  • SSL has not expired

    SSL certificate has not expired.

  • Trusted SSL certificate

    The certificate presented by this domain was issued by a trusted certificate authority.

  • SSL certificate chain present in server response

    A complete SSL certificate chain was presented by the server for this domain.

  • SSL chain certificates do not expire within 20 days

    SSL intermediate and root certificates do not expire within 20 days.

  • SSL expiration period shorter than 398 days

    The SSL certificate presented by the server has an expiration period shorter than 398 days.

  • SSL has more than 20% of its valid period remaining

    SSL certificate does not expire in less than 20% of its total valid period.

  • Strong SSL algorithm

    Industry standard SHA-256 encryption in use.

  • Strong public certificate key length

    The site's public certificate provides at least 112 bits of security strength.

Data leakage

  • WordPress plugin versions exposed

    Ensuring WordPress plugin versions are not exposed can make it harder for attackers to find exploits against your site.

  • No listable directories found

    No listable directories were found on the server.

  • WordPress user list not exposed

    Exposing the list of users on a WordPress site (via the WP-JSON API) can assist attackers in brute forcing credentials, as well as constitute a privacy risk.

  • No open cloud storage service detected

    No cloud storage service configured to allow anonymous file listing was detected.

  • Domain index is not a listable directory

    The domain index is not a listable directory.

IP/Domain Reputation

  • Not a suspected malware provider

    This website does not appear to contain malicious code.

  • No reports of botnet activity in the last 30 days

    This IP/domain has not been reported as a source of botnet activity in the last 30 days.

  • No reports of brute force login attempts in the last 30 days

    This IP/domain did not appear on any list of IPs and domains known to perform brute force login attempts in the last 30 days.

  • No reports of malware distribution in the last 30 days

    This IP/domain has been reported for distributing malware in the last 30 days.

  • No reports of unsolicited scanning in the last 30 days

    This IP/domain has not been reported for performing unsolicited scanning in the last 30 days.

  • Not suspected of unwanted software

    This website does not appear to be attempting to install unwanted software.

  • Not a suspected phishing page

    This site does not appear to be a forgery or imitation of another website.

  • No reports of phishing activity in the last 30 days

    This IP/domain has not been reported as a phishing site in the last 30 days.

  • No reports of botnet activity in the last 90 days

    This IP/domain has not been reported as a source of botnet activity in the last 90 days.

  • No reports of brute force login attempts in the last 90 days

    This IP/domain did not appear on any list of IPs and domains known to perform brute force login attempts in the last 90 days.

  • No reports of malware distribution in the last 90 days

    This IP/domain has been reported for distributing malware in the last 90 days.

  • No reports of unsolicited scanning in the last 90 days

    This IP/domain has not been reported for performing unsolicited scanning in the last 90 days.

  • No reports of phishing activity in the last 90 days

    This IP/domain has not been reported as a phishing site in the last 90 days.

Vulnerability Management

  • PHP 8.3.30 has potential vulnerabilities

    PHP 8.3.30 has vulnerabilities which might be exploitable under certain conditions. Affected domains should be checked to determine which vulnerabilities might pose a risk.

  • Not vulnerable to CVE-2014-0160 (Heartbleed)

    A bug in OpenSSL's implementation of the TLS heartbeat extension allows access to portions of memory on the targeted host e.g. cryptographic keys and passwords.

  • Not vulnerable to CVE-2014-3566 (POODLE)

    The server does not support SSLv3, and is not vulnerable to the POODLE attack.

  • Not vulnerable to CVE-2015-0204 (FREAK)

    The server does not offer RSA_EXPORT cipher suites, so clients are not vulnerable to the FREAK attack.

  • Not vulnerable to CVE-2015-4000 (Logjam)

    The server is using strong Diffie-Hellman parameters and is not vulnerable to the Logjam attack.

More security reports

Compare your security performance with other companies.

View all security reports