Skip to main content

Security report for rnz.co.nz

Radio New Zealand · Media · New Zealand

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

Security score

67/100

Risk levelMedium

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

Radio New Zealand (RNZ) is New Zealand's public broadcaster providing comprehensive news, current affairs, audio on demand, podcasts, and documentaries. The website serves as a primary digital platform for delivering timely and relevant content to the New Zealand public, positioning itself as a trusted media source. The site features a professional design, clear navigation, and multimedia content tailored to a general audience interested in news and cultural programming. Technically, the website employs modern JavaScript frameworks and libraries, including New Relic for performance monitoring, Google Tag Manager for marketing and analytics, and D3.js for data visualization. The site is well-optimized for mobile devices and accessibility, with good SEO practices evident in meta tags and structured content. Performance is moderate, with asynchronous loading of scripts and CDN usage. From a security perspective, RNZ uses HTTPS with good SSL configuration and includes security best practices such as monitoring and error tracking. However, explicit privacy and cookie policies are not evident in the provided content, and no dedicated security or incident response pages were found. The WHOIS data for the domain is unavailable due to registry policies, but the website's public broadcaster status and content quality provide strong legitimacy. Overall, RNZ's website demonstrates a mature digital presence with strong business credibility and technical implementation. To enhance trust and compliance, it is recommended to publish clear privacy and cookie policies, implement a vulnerability disclosure mechanism, and provide explicit contact information for security incidents.

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

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics

      What to do: Document all third-party data sharing in your privacy policy

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

Keep watching rnz.co.nz

This scan found 24 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
62
Security headers
65
Email security
75
DNS health
65
Network security
100
GDPR outside view
35
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

RNZ operates as a government-funded public media entity focused on delivering news and cultural content to New Zealanders. Its market position is strong as the national broadcaster, with a broad audience reach and diverse content offerings including radio, podcasts, and video documentaries. The business model relies on public funding and possibly sponsorships, emphasizing public service over commercial revenue. RNZ's partnership ecosystem includes media analytics providers and content distribution platforms. Growth indicators include active content updates and multimedia expansion. The website reflects a strategic focus on accessibility, content quality, and audience engagement.

Security posture

The website exhibits a solid security posture with HTTPS enforced and use of monitoring tools like New Relic and Chartbeat for performance and error tracking. No critical vulnerabilities or exposed sensitive data were detected in the HTML content. However, the absence of explicit privacy and cookie policies, as well as lack of visible security incident contact points, indicates room for improvement in compliance and incident response readiness. The use of multiple third-party scripts necessitates ongoing vulnerability management. Overall, the security maturity is good but could be enhanced by formalizing privacy and security disclosures.

Recommendations

  1. Publish comprehensive privacy and cookie policies prominently linked on the website.
  2. Implement a security.txt file or dedicated vulnerability disclosure page to facilitate responsible reporting.
  3. Provide clear contact information for security incidents and data protection inquiries.
  4. Regularly audit and update third-party scripts and libraries to mitigate vulnerabilities.
  5. Enhance transparency around data collection and user consent mechanisms to improve privacy compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Radio New Zealand
Description
New Zealand's public broadcaster, providing comprehensive NZ news and current affairs, specialist audio features and documentaries.
Key services
News reporting, Current affairs coverage, Audio on demand, Podcasts, Documentaries, Radio broadcasting
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, New Relic monitoring, Google Tag Manager, D3.js, Observable Plot, CDN usage (jsdelivr, Google Analytics CDN)
Frameworks
ELF (meta generator), New Relic Browser Agent, Chartbeat
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • Use of HTTPS
  • Use of Google Tag Manager with async loading
  • New Relic monitoring for performance and errors
  • No exposed sensitive data in HTML
  • No visible vulnerable libraries

Analytics and tracking

Services
Google Analytics, Chartbeat, New Relic Browser, Nielsen
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
Chartbeat
Tracking pixels
New Relic, Chartbeat, Nielsen (imrworldwide)
Transparency
basic

Site quality

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

Key observations

  1. Website is a professional public broadcaster site for New Zealand news and media.
  2. Content is rich, well-structured, and updated with recent news articles and multimedia.
  3. No signs of adult or questionable content.
  4. No visible contact emails or phone numbers on the main page HTML.
  5. No explicit privacy, cookie, or terms of service pages linked in the provided HTML snippet.
  6. Uses multiple third-party analytics and monitoring tools.
  7. No WAF or blocking detected; content fully accessible.
  8. WHOIS data unavailable due to NZ registry policy or query limitations.
Technical notes

Notes

RNZ's website is built using modern web technologies including JavaScript frameworks, New Relic for monitoring, and Google Tag Manager for analytics. The site leverages CDNs for asset delivery and includes advanced visualization libraries like D3.js. Performance optimizations include asynchronous script loading and responsive design for mobile devices. Accessibility features are present, and SEO is well addressed through meta tags and structured content. The technical infrastructure supports a rich multimedia experience but requires continuous maintenance of third-party dependencies to avoid security risks.
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 rnz.co.nz. 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 rnz.co.nz.

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.