Skip to main content

Security report for sts.pl

STS · Other · Poland

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

Security score

67/100

Risk levelMedium

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

STS is a prominent Polish bookmaker specializing in sports betting services. The website targets adult users interested in gambling and offers an online platform for placing bets on various sports. The business appears to be large and well-established within Poland, focusing on the gambling sector. The website's technical infrastructure is based on modern JavaScript frameworks, likely Angular, and integrates third-party widgets such as Sir.Sportradar for sports data. However, the site relies heavily on client-side rendering, resulting in minimal static HTML content in the snapshot provided. Security-wise, the site uses HTTPS and Google Tag Manager with default denied consent settings, indicating some privacy awareness. Nevertheless, there is a lack of visible security headers, privacy policies, cookie consent mechanisms, and contact information, which are critical for compliance and trust. Overall, the site shows moderate technical maturity but needs improvements in privacy compliance and security best practices.

Scanned

NIS2 and GDPR posture

GDPR outside view
10/ 100 · Critical
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. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

  2. 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"

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

Keep watching sts.pl

This scan found 21 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
77
Security headers
45
Email security
85
DNS health
85
Network security
100
GDPR outside view
10
Average
67

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

STS holds a leading position in the Polish sports betting market, operating an online gambling platform. Its business model revolves around providing betting services to adult customers, leveraging partnerships with sports data providers like Sportradar. The company likely generates revenue through betting margins and possibly promotional activities. The absence of public WHOIS data suggests privacy protection, common in gambling industries to protect business and customer data. The website's branding is consistent, targeting a specific niche audience. However, the lack of visible contact and compliance information may impact customer trust and regulatory adherence. The company should consider enhancing transparency and compliance disclosures to strengthen its market position.

Security posture

The website demonstrates a basic security posture with HTTPS enabled and the use of Google Tag Manager configured to deny ad and analytics storage by default. However, the absence of visible security headers such as Content Security Policy, HSTS, and X-Frame-Options is a concern. No forms or input fields were detected in the static HTML snapshot, limiting assessment of input validation and secure data handling. The lack of published privacy and cookie policies, as well as incident response contacts, indicates gaps in compliance and readiness. These factors reduce the overall security maturity and expose the business to potential regulatory and operational risks. Enhancing security headers, publishing comprehensive policies, and providing clear incident response channels are recommended.

Recommendations

  1. Implement comprehensive privacy and cookie policies with explicit user consent mechanisms to ensure GDPR compliance.
  2. Add and enforce security headers such as Content Security Policy, HSTS, and X-Frame-Options to strengthen security posture.
  3. Publish clear contact information including support and incident response channels to improve transparency and trust.
  4. Improve SEO metadata and accessibility features to enhance user experience and search engine visibility.
  5. Regularly audit third-party scripts and libraries to avoid vulnerabilities and ensure secure integrations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
STS
Description
STS is a bookmaker company offering sports betting services primarily targeting Polish customers.
Key services
sports betting, online gambling
Content quality
basic
Branding
consistent

Technology

Stack
JavaScript, Material Icons, Google Tag Manager, Sir.Sportradar Widget
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
50/100
Good practices seen
  • Uses HTTPS (inferred from URL)
  • Google Tag Manager with default denied consent for ad and analytics storage

Analytics and tracking

Services
Google Tag Manager
Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website content is minimal in the provided HTML snapshot, likely relying on client-side rendering.
  2. No visible privacy, cookie, or terms of service pages found in the HTML snapshot.
  3. No contact emails, phone numbers, or physical addresses found in the HTML snapshot.
  4. No forms detected in the HTML snapshot; user interaction likely handled dynamically.
  5. Use of Google Tag Manager with default denied consent indicates some privacy awareness but no explicit consent mechanism visible.
  6. Fonts and icons are loaded from trusted external sources.
  7. No security headers visible in the HTML content; server headers not provided for analysis.
  8. No explicit security or incident response information found.
  9. No certifications or compliance badges visible.
  10. Website targets adult users interested in sports betting in Poland.
Technical notes

Notes

The website uses a modern JavaScript framework, likely Angular, indicated by the presence of Angular Material CSS variables and custom elements like <app-mweb>. It preloads multiple custom fonts and uses external resources such as Google Fonts and Material Icons. The integration of third-party widgets from Sportradar suggests reliance on external sports data providers. The site employs Google Tag Manager for analytics and tracking, configured with default denied consent for ad and analytics storage, indicating some privacy consideration. The static HTML content is minimal, implying client-side rendering dominates, which may impact SEO and initial load performance. No CMS or hosting provider information is directly discernible from the HTML snapshot. Performance is moderate with basic mobile optimization and accessibility. The site would benefit from server-side rendering or prerendering to improve SEO and accessibility.
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 sts.pl. 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 sts.pl.

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.