Skip to main content

Security report for radio-canada.ca

Radio-Canada · Media · Canada

Medium risk. 6 critical or high findings in Security headers and GDPR outside view.

Security score

68/100

Risk levelMedium

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

Radio-Canada is the French-language public broadcaster in Canada, providing a comprehensive range of news, radio, television, sports, and arts content. The website serves as a digital platform to inform and entertain a broad audience, primarily French-speaking Canadians. It holds a strong market position as a trusted source of information and cultural programming under the umbrella of the Canadian Broadcasting Corporation. The site features consistent branding and professional content quality, reflecting its status as a major public media entity. Technically, the website employs modern web technologies including React, Google Tag Manager, and Facebook Pixel for analytics and marketing. It is optimized for mobile devices and demonstrates good SEO and accessibility practices. The presence of a PWA manifest indicates a focus on progressive web app capabilities, enhancing user experience across platforms. From a security perspective, the site enforces HTTPS with strong SSL configuration and implements multiple security headers to protect users. No critical vulnerabilities or exposed sensitive data were detected in the provided content. Privacy compliance is well addressed with clear privacy and cookie policies, including consent mechanisms aligned with GDPR requirements. However, explicit contact information for security or incident response was not found. Overall, Radio-Canada's website presents a low-risk profile with high trustworthiness and professionalism. Strategic recommendations include continuous monitoring of third-party scripts, ensuring secure form handling, and maintaining up-to-date security practices to sustain its strong security posture.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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 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

    • 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

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

Keep watching radio-canada.ca

This scan found 22 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
85
Security headers
30
Email security
70
DNS health
85
Network security
100
GDPR outside view
35
Average
68

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 radio-canada.ca, from OffSeq Breach.

Total records
8,450
Employees
4
Customers
8,087
Third parties
359
Weak passwords
0%

Latest record dated 2026-05-26 · 68 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 radio-canada.ca.

Select it in the checkout above.

Masked preview

  • –services.radio-canada.ca2026-05-26
  • –presse.radio-canada.ca2026-05-25
  • –services.radio-canada.ca2025-11-16
  • –services.radio-canada.ca2025-07-20

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

Technical appendix

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

Business context

Business profile

Radio-Canada operates as a key player in the Canadian media landscape, focusing on French-language content delivery across multiple platforms. Its business model is centered on public broadcasting funded by government and public sources, emphasizing news, cultural programming, and entertainment. The company leverages digital channels to expand reach and engagement, integrating advertising and analytics tools to optimize audience insights. The absence of direct contact information on the main site suggests centralized communication channels typical of large public entities. Partnerships and subsidiary relationships are not explicitly detailed in the provided data but are likely managed under the CBC umbrella. The website's comprehensive content and consistent branding reinforce its competitive advantage as a trusted media source.

Security posture

The website demonstrates a mature security posture with enforced HTTPS, robust SSL configuration, and implementation of key security headers such as HSTS, CSP, and X-Frame-Options. No signs of outdated or vulnerable libraries were detected in the analyzed scripts. The use of third-party analytics and advertising scripts introduces a moderate tracking footprint, which is managed with consent mechanisms to comply with privacy regulations. The lack of explicit security policy or incident response contact information is a minor gap but common in public media sites. Overall, the site maintains strong defenses against common web threats and aligns with best practices for user data protection and privacy compliance.

Recommendations

  1. Conduct regular security audits of third-party scripts and dependencies to mitigate supply chain risks.
  2. Implement and publicize a dedicated security policy and incident response contact to enhance transparency.
  3. Ensure all user input forms include CSRF protection and input validation to prevent injection attacks.
  4. Maintain and update privacy and cookie consent mechanisms to reflect evolving regulatory requirements.
  5. Enhance monitoring and logging capabilities to quickly detect and respond to security incidents.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Radio-Canada
Description
Consultez le site web de Radio-Canada pour vous informer et vous divertir. Trouvez vos nouvelles, émissions télé ou radio, en direct et sur demande.
Key services
News, Radio broadcasts, Television programming, Sports coverage, Arts and culture content
Content quality
excellent
Branding
consistent

Technology

Stack
React, Google Tag Manager, Facebook Pixel, Scorecard Research, Google Fonts, Progressive Web App (PWA) manifest
Frameworks
React
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Use of security headers
  • No exposed sensitive data detected
  • Secure forms (no forms detected in provided HTML but likely present on site)

Analytics and tracking

Services
Scorecard Research, Google Analytics (via GTM)
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Scorecard Research
Tracking pixels
Facebook Pixel
Marketing tools
Facebook Pixel
Transparency
basic

Site quality

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

Key observations

  1. Domain WHOIS data is not publicly available, likely due to privacy or registry policies.
  2. Website is fully accessible with rich content in French language.
  3. Strong branding consistent with Radio-Canada, a major Canadian public broadcaster.
  4. Use of modern web technologies and tracking scripts for analytics and advertising.
  5. No contact emails or phone numbers explicitly found in provided HTML snippet.
  6. No explicit security or incident response contact information found.
  7. No vulnerability disclosure or security.txt file detected.
  8. Advertising and tracking practices are present but standard for media websites.
  9. No adult or questionable content detected; content is safe for general audiences.
Technical notes

Notes

The website is built using React and integrates multiple third-party services including Google Tag Manager and Facebook Pixel for analytics and marketing. It uses Google Fonts for typography and supports progressive web app features via a manifest file. The site is mobile-optimized with responsive design and accessibility considerations. Performance is moderate, likely influenced by external scripts and rich media content. No CMS was explicitly detected, suggesting a custom or proprietary platform. Hosting details are not disclosed in the provided data. The technical infrastructure supports a high-quality user experience but requires ongoing maintenance to manage third-party dependencies and ensure optimal performance.
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 radio-canada.ca. 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 radio-canada.ca.

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.