Skip to main content

Security report for russellhobbs.co.nz

Russell Hobbs · Retail · New Zealand

Medium risk. 5 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

Russell Hobbs New Zealand operates an e-commerce website specializing in home and kitchen appliances such as kettles, toasters, irons, and cookware. The brand has a long-standing history of over 65 years and targets general consumers in New Zealand. The website demonstrates a moderate level of digital maturity with integration of modern JavaScript libraries, Google Tag Manager for analytics, and Google reCAPTCHA for bot protection. The technical infrastructure is sound with HTTPS enforced and CSRF tokens implemented for AJAX requests, indicating attention to security best practices. However, the absence of explicit privacy and cookie policies, as well as lack of security headers, suggests room for improvement in privacy compliance and security posture. Overall, the domain registration data aligns well with the business claims, supporting legitimacy and trustworthiness.

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 Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

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

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching russellhobbs.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. See sample alerts.

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
67
Security headers
15
Email security
85
DNS health
65
Network security
100
GDPR outside view
68
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

The company positions itself as a reputable retailer of affordable and high-quality home appliances in the New Zealand market. Its e-commerce business model focuses on direct online sales, leveraging brand recognition and product variety. The website content and metadata emphasize product categories and brand heritage, appealing to a broad consumer base. While no explicit partnership or subsidiary domains were identified, the use of Google services for analytics and security is evident. The business appears medium-sized with a stable online presence since 2010, indicating sustained market engagement.

Security posture

The website employs HTTPS with a valid SSL certificate and integrates Google reCAPTCHA to mitigate automated abuse. CSRF tokens are used in AJAX POST requests, enhancing protection against cross-site request forgery attacks. However, the lack of security headers such as Content-Security-Policy and X-Frame-Options reduces defense-in-depth. No security.txt or vulnerability disclosure mechanisms were found, limiting transparency for security researchers. Privacy compliance is weak due to missing privacy and cookie policies, which could expose the company to regulatory risks. Overall, the security posture is moderate but could benefit from enhanced policies and headers.

Recommendations

  1. Publish comprehensive privacy and cookie policies accessible from the website footer or dedicated pages.
  2. Implement standard security headers including Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  3. Enable DNSSEC for the domain to improve DNS security and integrity.
  4. Create and publish a security.txt file to facilitate responsible vulnerability disclosure.
  5. Enhance privacy compliance by including GDPR-related information and data retention policies.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Russell Hobbs
Description
For over 65 years Russell Hobbs has been providing high quality and affordable home & kitchen appliances - from kettles to irons, toasters to cookware.
Key services
Online sales of kettles, toasters, irons, cookware, home and kitchen appliances
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, Google Tag Manager, reCAPTCHA, Swiper.js, Open Sans font
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • CSRF token usage in AJAX requests
  • Google reCAPTCHA integration

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website uses HTTPS with valid SSL
  2. No explicit privacy or cookie policy found on the homepage
  3. CSRF tokens are implemented for AJAX POST requests
  4. Google reCAPTCHA is integrated for bot protection
  5. No contact emails or phone numbers explicitly found in the provided HTML snippet
  6. No security.txt or vulnerability disclosure page detected
  7. No data protection officer contact found
  8. WHOIS data shows domain is stable and consistent with business claims
Technical notes

Notes

The website uses a modern JavaScript stack with libraries such as Swiper.js for UI components and Google Tag Manager for analytics. Fonts are loaded from CDN sources, and reCAPTCHA is integrated for bot mitigation. The site is mobile optimized with responsive design and uses meta viewport tags appropriately. Performance is moderate, with potential improvements in loading speed by optimizing third-party scripts. The domain uses multiple Constellix name servers but lacks DNSSEC. No CMS or hosting provider was explicitly identified from the HTML content. Overall, the technical implementation is solid but could be enhanced with additional security 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 russellhobbs.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 russellhobbs.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.