Skip to main content

Security report for publiczneodtwarzanie.pl

Telewizja Polsat Sp. z o.o. · Media · Poland

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

Security score

65/100

Risk levelMedium

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

The website www.publiczneodtwarzanie.pl represents Telewizja Polsat Sp. z o.o., offering licensed sports broadcasting packages tailored for the hospitality industry including bars, restaurants, and hotels in Poland. The business model revolves around subscription-based access to various sports TV packages, enabling legal public viewing of sports events. The site is professionally designed with clear navigation and relevant content targeting hospitality businesses seeking to legally broadcast sports content to their customers. Technically, the website employs a modern tech stack including Ruby on Rails, React components, and AWS S3 for media hosting. It integrates Google Tag Manager for analytics and tracking. The site is mobile optimized and SEO friendly, though accessibility features are basic. Performance is moderate with room for improvement in security headers and technical optimizations. From a security perspective, the site uses HTTPS with CSRF protections and a cookie consent mechanism, indicating good privacy compliance aligned with GDPR. However, no explicit security headers or incident response policies were found, and WHOIS data is unavailable, which slightly reduces trustworthiness. No vulnerabilities or exposed sensitive data were detected in the provided content. Overall, the website presents a legitimate and professional service with a solid business presence. The main risks relate to the lack of WHOIS transparency and missing security headers. Strategic improvements in these areas would enhance trust and security posture significantly.

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

8 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

  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 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';…

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

Keep watching publiczneodtwarzanie.pl

This scan found 23 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
50
Email security
70
DNS health
80
Network security
100
GDPR outside view
10
Average
65

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention publiczneodtwarzanie.pl, from OffSeq Breach.

Total records
7
Employees
0
Customers
7
Third parties
0
Weak passwords
0%

2 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for publiczneodtwarzanie.pl.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Telewizja Polsat Sp. z o.o. occupies a niche market position as a licensed provider of sports broadcasting rights for public venues in Poland's hospitality sector. Their competitive advantage lies in offering multiple tailored sports packages including Polsat Sport and ELEVEN SPORTS channels. The subscription model generates recurring revenue from bars, restaurants, and hotels. The company maintains a clear partnership with Polsat, a major media entity, enhancing brand credibility. Growth potential exists in expanding package offerings and digital delivery methods. The website supports customer acquisition through clear package descriptions, registration, and contact options. The partnership ecosystem includes AWS for hosting and Google for analytics. No direct competitors or subsidiaries were identified from the data.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and CSRF tokens implemented. Privacy compliance is strong with a comprehensive privacy policy and cookie consent modal. However, the absence of HTTP security headers such as Content Security Policy, HSTS, and X-Frame-Options represents a gap that could expose the site to certain web attacks. No vulnerability disclosure or incident response information is published, limiting transparency in security incident handling. The lack of WHOIS data reduces domain trust and complicates ownership verification. Overall, the security posture is adequate for the business type but could be improved by adopting additional security best practices and publishing incident response contacts.

Recommendations

  1. Implement standard HTTP security headers including CSP, HSTS, X-Frame-Options, and X-XSS-Protection to enhance protection against common web vulnerabilities.
  2. Publish a security.txt file or a dedicated vulnerability disclosure policy page to improve transparency and facilitate responsible vulnerability reporting.
  3. Enhance WHOIS transparency by ensuring domain registration data is publicly available or providing verifiable ownership information on the website.
  4. Add explicit incident response contact information or security contact emails to improve trust and readiness for security events.
  5. Conduct regular security audits and update third-party libraries to mitigate risks from vulnerable dependencies.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Telewizja Polsat Sp. z o.o.
Description
Provides legal public broadcasting of sports events in bars, restaurants, and hotels with various TV packages offered for the HoReCa sector.
Key services
Pakiet Mega Sport, Pakiet Polsat Sport, Pakiet Polsat Sport Premium, Pakiet ELEVEN SPORTS
Content quality
good
Branding
consistent

Technology

Stack
React (react component tooltip), Google Tag Manager, FontAwesome, AWS S3 (for image hosting)
Frameworks
Ruby on Rails
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • CSRF tokens present in meta tags
  • Cookie consent modal implemented

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is fully accessible with rich content and clear business purpose.
  2. No WHOIS data available from NASK registry, which is unusual for .pl domains.
  3. Privacy policy and cookie consent are implemented and GDPR compliant.
  4. Contact information is clearly provided with company email and phone numbers.
  5. No explicit security.txt or incident response info found.
  6. Use of modern web technologies and CDN for images.
  7. No signs of adult or questionable content.
  8. No visible security headers in provided data; potential area for improvement.
Technical notes

Notes

The website is built on a Ruby on Rails framework with React components for UI elements, indicating a modern and maintainable codebase. Static assets and images are served via AWS S3, supporting scalability and performance. Google Tag Manager is used for analytics and marketing tracking. The site is mobile responsive and SEO optimized with proper meta tags and canonical links. However, the absence of visible HTTP security headers and limited accessibility features suggest areas for technical improvement. Performance is moderate, likely influenced by external scripts and image sizes. Overall, the technical infrastructure supports the business needs but would benefit from enhanced security configurations and accessibility enhancements.
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 publiczneodtwarzanie.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 publiczneodtwarzanie.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.