Skip to main content

Security report for polskieradio.pl

Polskie Radio · Media · Poland

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

Security score

57/100

Risk levelMedium

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

Polskie Radio is a major public media broadcaster in Poland offering a wide range of audio content including podcasts, radio shows, audiobooks, and reports. The website podcasty.polskieradio.pl serves as a portal for accessing these audio programs, targeting Polish-speaking audiences including children and general listeners. The platform is professionally designed with a modern tech stack leveraging Next.js, React, and analytics tools such as Gemius and Hotjar. Security posture is solid with HTTPS enforced and no visible vulnerabilities, though explicit security headers and privacy policies are missing. The absence of WHOIS data is typical for .pl domains but slightly reduces trust. Overall, the site is a credible and well-maintained digital asset of Polskie Radio.

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

10 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

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

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

Keep watching polskieradio.pl

This scan found 25 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
52
Security headers
15
Email security
82
DNS health
85
Network security
100
GDPR outside view
10
Average
57

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

Polskie Radio holds a strong market position as Poland's national public radio broadcaster. Its business model focuses on content creation and distribution via multiple channels including live radio and podcasts. The website reflects a mature digital presence with extensive branded content and multiple radio station domains linked. The use of advanced analytics and mobile optimization tools indicates a focus on audience engagement and digital growth. Lack of visible contact details and privacy documentation suggests room for improvement in transparency and compliance. The platform supports a broad audience base, including children, and offers diverse content genres.

Security posture

The website demonstrates a good security posture with HTTPS enabled and no exposed sensitive data in the HTML. Use of asynchronous script loading and modern JavaScript frameworks reduces attack surface. However, the absence of explicit security headers such as Content Security Policy, HSTS, and X-Frame-Options is a gap. No vulnerability disclosures or incident response information is published, limiting transparency. Privacy and cookie policies are not detected, which may impact GDPR compliance. Overall, the site is secure but could enhance its security maturity by publishing policies and implementing additional headers.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie consent mechanism to improve GDPR compliance.
  2. Add security headers including Content Security Policy, HSTS, and X-Frame-Options to strengthen security posture.
  3. Provide clear contact information including security incident response and data protection officer contacts.
  4. Publish vulnerability disclosure and incident response procedures to enhance transparency and trust.
  5. Regularly audit third-party scripts and analytics tools to minimize privacy risks and ensure compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Polskie Radio
Description
Podcasty, audycje, audiobooki, reportaże i słuchowiska Polskiego Radia i Teatru Polskiego Radia. Audycje i podcasty dla dzieci. Polskie Radio online.
Key services
Podcasts, Radio broadcasts, Audiobooks, Reportaże (reports), Słuchowiska (radio plays)
Content quality
excellent
Branding
consistent

Technology

Stack
React (Next.js), Toastify (for notifications), Hotjar (user behavior analytics), Gemius (analytics), Marfeel SDK (mobile optimization), SVG graphics, Modern CSS with variables and transitions
Frameworks
Next.js
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced (implied by URL)
  • No exposed sensitive data in HTML
  • Use of async and defer on scripts

Analytics and tracking

Services
Gemius, Hotjar
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Gemius, Hotjar
Marketing tools
Marfeel SDK
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content and professional design
  2. No explicit privacy, cookie, or terms of service pages found in provided HTML
  3. No contact emails or phone numbers explicitly found in the HTML content
  4. Strong use of modern web technologies and analytics tools
  5. No signs of security blocking or WAF challenges
  6. WHOIS data is unavailable, typical for .pl domains, but website branding is consistent with official entity
Technical notes

Notes

The website is built using Next.js, a React-based framework, indicating a modern and scalable architecture. It uses advanced CSS with variables and transitions for a polished UI. Analytics tools like Gemius and Hotjar are integrated for user behavior tracking. The site is mobile optimized and accessible with good SEO metadata including Open Graph and JSON-LD structured data. Performance is moderate, likely due to rich media content. No CMS or hosting provider details are explicitly found. The technical implementation is robust but could benefit from enhanced security headers and privacy features.
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 polskieradio.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 polskieradio.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.