Skip to main content

Security report for oddschecker.com

Other · N/a

Medium risk. 6 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

The analyzed page is a Cloudflare security challenge page for www.oddschecker.com, designed to verify user identity before granting access to the main site. This indicates the site employs bot mitigation and abuse prevention mechanisms. However, the page content is minimal and does not provide any business, contact, or policy information. The WHOIS lookup failed to retrieve any domain registration data, which raises concerns about domain legitimacy or privacy protection usage. The technical infrastructure includes JavaScript fingerprinting and Cloudflare services, but no further CMS or hosting details are visible. Security posture is limited due to lack of visible headers and policies, but the presence of Cloudflare challenge is a positive security control. Overall, the site is operational but the analysis is limited by the WAF challenge and missing WHOIS data.

Scanned

NIS2 and GDPR posture

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

6 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 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

  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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching oddschecker.com

This scan found 18 issues across 5 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
45
Email security
100
DNS health
80
Network security
100
GDPR outside view
50
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

Due to the page being a security verification checkpoint, no direct business intelligence data is available from this content. Oddschecker is known as a betting odds comparison platform, but this page does not provide insights into market positioning, revenue streams, or partnerships. The lack of visible contact or corporate information limits business credibility assessment. The domain WHOIS absence is unusual for a commercial site and may indicate privacy protection or registration issues.

Security posture

The site uses Cloudflare for bot mitigation, which is a strong security measure against automated abuse. However, no security headers or SSL configuration details are visible in the provided data. The absence of privacy and cookie policies and contact information for incident response reduces compliance and transparency. The domain WHOIS data is missing, which is a negative indicator for trust. Overall, security posture is moderate but incomplete due to limited data and WAF blocking.

Recommendations

  1. Publish clear privacy and cookie policies accessible before or after the verification step.
  2. Ensure WHOIS data is properly registered and publicly available to improve trust.
  3. Implement and expose security headers such as CSP, HSTS, and X-Frame-Options.
  4. Provide visible contact information and incident response channels on accessible pages.
  5. Optimize the verification page to allow some metadata and SEO content for better indexing and user trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. Page is a Cloudflare security challenge page verifying user identity before redirecting to main site. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Description
The page is a security verification checkpoint to confirm user identity before accessing the main Oddschecker website.
Content quality
basic

Technology

Stack
JavaScript, Cloudflare (implied by challenge script), HTML5, CSS3

Security

Observed score
25/100
Good practices seen
  • Use of Cloudflare challenge script for bot mitigation

Analytics and tracking

Site quality

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

Key observations

  1. Website content is blocked by a Cloudflare security challenge page.
  2. No WHOIS data available indicating possible privacy protection or domain registration issues.
  3. No visible privacy, cookie, or terms of service policies on this page.
  4. No contact information or business details are present on this page.
  5. No forms or user input fields are present except the automated verification script.
  6. External script loaded from a subdomain of oddschecker.com for fingerprint verification.
  7. Page is minimal and designed solely for bot/abuse prevention.
  8. No SEO or accessibility metadata found in this HTML snippet.
  9. No social media or external links present except the redirect URL.
  10. No visible security headers or SSL details available from provided data.
Technical notes

Notes

The page uses modern JavaScript and CSS for a clean verification UI. It loads a fingerprint verification script from a subdomain, indicating a custom or third-party bot detection solution. The presence of Cloudflare challenge scripts confirms use of a major WAF provider. No CMS or hosting provider is identifiable from the snippet. Performance and accessibility cannot be fully assessed due to minimal content and WAF blocking. The technical implementation is functional for its purpose but lacks transparency and user-facing content.
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 oddschecker.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 oddschecker.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.