Skip to main content

Security report for nzrl.co.nz

New Zealand Rugby League · Other · New Zealand

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

Security score

52/100

Risk levelMedium

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

New Zealand Rugby League operates as the national governing body for rugby league in New Zealand, providing comprehensive information on national teams, tournaments, player resources, and community engagement. The website serves a broad audience including players, coaches, referees, fans, and community members, positioning itself as an authoritative source for rugby league in the country. The business model focuses on sports promotion, community involvement, and membership services, supported by a medium-sized organizational structure founded in 2001. Technically, the website is built on WordPress with a modern tech stack including Bootstrap, jQuery, and various plugins for analytics and user engagement such as Google Analytics, Hotjar, and YouTube Embed Plus. Hosting and DNS services are provided by Freeparking Limited and Cloudflare respectively, ensuring reliable performance and security. The site demonstrates good mobile optimization and SEO practices, though accessibility features are basic. From a security perspective, the site uses HTTPS with a valid SSL certificate, but lacks DNSSEC and explicit security headers, which are recommended for enhanced protection. No privacy or cookie policies were detected, indicating potential compliance gaps with GDPR and other privacy regulations. The site employs tracking and marketing tools, including Facebook Pixel and HubSpot, with moderate user tracking levels. Overall, the website is professional, content-rich, and trustworthy, with a strong brand presence and social media integration. However, improvements in privacy compliance and security hardening are advised to mitigate risks and enhance user trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 100 · Medium
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

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

  2. GDPR outside view

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

    • 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

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching nzrl.co.nz

This scan found 26 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
50
Security headers
15
Email security
75
DNS health
65
Network security
40
GDPR outside view
68
Average
52

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

The New Zealand Rugby League holds a strong market position as the official rugby league authority in New Zealand, leveraging its long-standing domain and established brand. Its competitive advantage lies in comprehensive coverage of national teams, tournaments, and community programs, supported by active social media channels. Revenue streams likely include memberships, sponsorships, and event promotions. The target customer segments encompass players, coaches, referees, fans, and community stakeholders. Growth indicators include recent news updates and digital engagement tools. The partnership ecosystem includes social media platforms and sports-related service providers, with strategic focus on community outreach and sport development.

Security posture

The current security maturity is moderate, with HTTPS enforced and no visible exposure of sensitive data. However, the absence of DNSSEC and security headers such as Content-Security-Policy and X-Frame-Options presents potential vulnerabilities. The lack of a published security policy or incident response contact limits transparency and preparedness. Compliance gaps exist due to missing privacy and cookie policies, which are critical under GDPR and similar regulations. The use of reCAPTCHA and security plugins suggests some security awareness, but further enhancements are necessary to elevate the security posture and reduce risk exposure.

Recommendations

  1. Enable DNSSEC on the domain to protect against DNS spoofing and improve DNS security.
  2. Implement standard security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web attacks.
  3. Publish comprehensive privacy and cookie policies with clear GDPR compliance statements and consent mechanisms.
  4. Develop and display a security policy and incident response contact information to improve transparency and user trust.
  5. Regularly audit and update WordPress core, themes, and plugins to address vulnerabilities and maintain security hygiene.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
New Zealand Rugby League
Description
Official New Zealand Rugby League website
Key services
National teams information, Tournaments and competitions, Player, coach, referee resources, Community engagement, Membership services
Content quality
good
Branding
consistent

Technology

Stack
WordPress, PHP, jQuery, Bootstrap 3.3.7, Font Awesome, Google Analytics, Hotjar, YouTube Embed Plus, Slider Revolution, WPBakery Page Builder, Cloudflare DNS
Frameworks
WordPress
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enabled
  • No exposed sensitive data in HTML
  • Use of Google reCAPTCHA
  • Use of security plugins (implied by WordPress plugins)

Analytics and tracking

Services
Google Analytics, MonsterInsights, Hotjar
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Facebook Pixel, Hotjar
Marketing tools
HubSpot WordPress plugin, MonsterInsights Google Analytics plugin
Transparency
basic

Site quality

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

Key observations

  1. Website is a professionally maintained WordPress site for New Zealand Rugby League.
  2. Content is rich with news, player info, tournaments, and community resources.
  3. No privacy or cookie policy pages explicitly found in provided content.
  4. Uses multiple analytics and tracking tools including Google Analytics and Hotjar.
  5. No security headers detected in provided data; DNSSEC not enabled.
  6. No signs of WAF or content blocking; site fully accessible.
  7. Social media presence is strong with official accounts linked.
  8. No contact emails explicitly found; phone number provided in structured data.
  9. Site uses HTTPS with valid SSL.
  10. No vulnerability disclosure or security policy pages found.
Technical notes

Notes

The website infrastructure is based on WordPress CMS, utilizing a combination of Bootstrap for responsive design, jQuery for interactivity, and several plugins for analytics and content management. Hosting is stable with Cloudflare DNS services, though DNSSEC is not enabled. Performance is moderate with room for optimization. The site is mobile-friendly and SEO-optimized with proper meta tags and structured data. Technical debt appears low, but the absence of security headers and privacy compliance features indicates areas for modernization and risk mitigation. Overall, the technical setup supports the business needs but requires security and privacy 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 nzrl.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 nzrl.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.