Skip to main content

Security report for cmsbetconstruct.com

BetConstruct · Technology · N/a

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

Security score

70/100

Risk levelMedium

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

The website backoffice.betconstruct.com serves as an internal backoffice platform for BetConstruct, a technology provider specializing in betting and gaming solutions. The platform appears designed for business users such as partners and internal staff, offering tools for sportsbook management, user and partner management, and CRM functionalities. The site is part of an enterprise-level business model focused on B2B services within the technology industry. The content is minimal and functional, lacking public marketing or customer-facing information. Technically, the site is built on an older AngularJS 1.3.13 framework, supplemented by Kendo UI and RequireJS for modular loading. It integrates analytics and chat support via Mixpanel and Hoory SDK respectively. The site shows moderate performance and basic mobile optimization but lacks modern SEO and accessibility features. No CMS or hosting provider details are evident from the source. From a security perspective, the site uses HTTPS but does not exhibit explicit security headers in the provided HTML. The use of an outdated AngularJS version introduces potential vulnerabilities. No privacy, cookie, or terms of service policies are present, indicating gaps in compliance and transparency. External links are mostly to trusted domains except for one unusual rate widget domain, which should be reviewed. No WAF or blocking mechanisms were detected, and no sensitive data exposure was found. Overall, the site is functional for its internal business purpose but requires modernization of its technology stack, improved security practices, and enhanced privacy compliance to reduce risk and improve trustworthiness.

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

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

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

Keep watching cmsbetconstruct.com

This scan found 20 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
82
Security headers
15
Email security
85
DNS health
85
Network security
100
GDPR outside view
50
Average
70

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

BetConstruct operates as a technology provider in the betting and gaming sector, targeting operators and partners with software solutions such as sportsbook management and CRM tools. The backoffice platform supports internal and partner operations rather than direct consumer engagement. The company likely generates revenue through B2B licensing and service agreements. The presence of a customer support portal on Atlassian indicates a structured support ecosystem. The business model is enterprise-focused with a mature market position. The lack of public contact information and policies on this subdomain suggests it is not intended for public marketing but for operational use. Strategic partnerships and integrations with external services like Hoory and Mixpanel support customer engagement and analytics.

Security posture

The security posture of the backoffice.betconstruct.com site is moderate but with notable weaknesses. HTTPS is used, ensuring encrypted communications. However, the absence of security headers such as Content Security Policy (CSP), X-Frame-Options, and HSTS reduces protection against common web attacks. The AngularJS version is outdated and may expose the site to known vulnerabilities including XSS. No privacy or cookie policies are present, indicating compliance gaps with GDPR and other regulations. The site lacks visible incident response or security policy documentation. Analytics and chat integrations increase the attack surface and require careful configuration. Overall, the site needs security hardening, policy publication, and technology updates to meet enterprise security standards.

Recommendations

  1. Upgrade AngularJS framework to a current supported version or migrate to a modern framework to mitigate known vulnerabilities.
  2. Implement comprehensive security headers including CSP, HSTS, X-Frame-Options, and X-Content-Type-Options.
  3. Publish clear privacy, cookie, and terms of service policies to improve compliance and user trust.
  4. Conduct a security audit focusing on input validation, XSS, and injection vulnerabilities.
  5. Review and validate all third-party integrations, especially the external rate widget domain, for security and privacy risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
BetConstruct
Description
Backoffice platform for BetConstruct, a technology provider in the betting and gaming industry.
Key services
Sportsbook management, User management, CRM tools, Partner management
Content quality
basic
Branding
consistent

Technology

Stack
AngularJS 1.3.13, Kendo UI, RequireJS, Alasql, Font Awesome, Icomoon, Mixpanel, Hoory SDK
Frameworks
AngularJS
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
55/100
Good practices seen
  • Use of HTTPS assumed (URL is https)
  • No exposed sensitive data in HTML
  • Use of AngularJS with custom validation directives

Analytics and tracking

Services
Mixpanel
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Mixpanel
Marketing tools
Mixpanel, Hoory SDK
Transparency
poor

Site quality

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

Key observations

  1. Website is a business backoffice portal for BetConstruct employees or partners.
  2. No public-facing marketing or customer service content found.
  3. No privacy, cookie, or terms of service pages detected in provided HTML.
  4. No contact emails or phone numbers found in the HTML content.
  5. Use of outdated AngularJS version may pose security risks.
  6. External links mostly to trusted domains except one unusual domain for rate widget.
  7. No explicit security headers or meta tags found in HTML source.
  8. No structured data (JSON-LD) or Open Graph metadata present.
  9. No forms with user input fields detected except partner selection search box.
  10. No social media links or company contact info visible.
Technical notes

Notes

The website uses a legacy AngularJS 1.3.13 framework combined with Kendo UI components and RequireJS for module loading. It integrates third-party analytics (Mixpanel) and chat support (Hoory SDK). The site loads multiple CSS frameworks including Font Awesome and Icomoon for icons. Performance is moderate with asynchronous script loading but could benefit from modernization. The site lacks structured data and SEO meta tags, limiting search engine visibility. Accessibility features are basic, and mobile optimization is minimal. No CMS or hosting provider information is discernible. The technical debt from outdated frameworks and missing security headers poses risks to stability and security.
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 cmsbetconstruct.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 cmsbetconstruct.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.