Skip to main content

Security report for ami.co.nz

AMI Insurance · Finance · New Zealand

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

Security score

65/100

Risk levelMedium

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

AMI Insurance is a well-established New Zealand insurance provider, operating as a division of IAG New Zealand Limited. The company offers a broad range of insurance products including car, home, contents, landlord, travel, and business insurance, complemented by value-added services such as roadside rescue. The website reflects a strong market position supported by industry awards and a robust financial strength rating. The target audience primarily consists of New Zealand residents seeking personal and business insurance solutions. The business model focuses on direct online engagement with customers, providing quotes, policy management, and claims services digitally. Technically, the website is built on Adobe Experience Manager CMS and leverages modern web technologies including Adobe Helix RUM for performance monitoring, Typekit for fonts, and Vidyard for video content. The site is hosted likely via Akamai CDN, ensuring fast performance and excellent mobile optimization. SEO and accessibility practices are well implemented, contributing to a positive user experience. From a security perspective, the site enforces HTTPS and uses secure login portals. However, explicit security headers are not evident, and no cookie consent mechanism was detected, which are areas for improvement. The absence of WHOIS data for the domain is noted but is consistent with the domain being a subdomain under a larger corporate domain. Overall, the security posture is strong with no visible vulnerabilities. The website is safe for general audiences, with no adult or explicit content. Social media presence and multiple trust indicators enhance credibility. Strategic recommendations include implementing cookie consent for privacy compliance, adding security headers, and publishing a vulnerability disclosure policy to further strengthen trust and security culture.

Scanned

NIS2 and GDPR posture

GDPR outside view
58/ 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

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

  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 ami.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
52
Security headers
25
Email security
85
DNS health
70
Network security
100
GDPR outside view
58
Average
65

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

AMI Insurance holds a significant position in the New Zealand insurance market, backed by its parent company IAG New Zealand Limited. The company benefits from a diversified product portfolio catering to both personal and business customers. Its digital-first approach with online quotes, claims, and policy management aligns with modern consumer expectations. The partnership ecosystem includes customer help portals and integration with IAG services. Growth indicators include recent awards and financial ratings. The company’s operations emphasize customer care and community involvement, as evidenced by partnerships like Habitat for Humanity. Revenue streams are primarily from insurance premiums and value-added services like roadside rescue.

Security posture

The security maturity level of the website is good, with HTTPS enforced and no exposed sensitive data. The use of secure external login portals indicates a separation of sensitive operations. However, the lack of explicit security headers such as Content-Security-Policy and absence of a cookie consent mechanism represent compliance gaps, particularly regarding GDPR and privacy regulations. No incident response or vulnerability disclosure information is publicly available, which could be improved to enhance transparency and readiness. Overall, the security culture appears professional but could benefit from formalized policies and disclosures.

Recommendations

  1. Implement a comprehensive cookie consent mechanism to comply with GDPR and privacy laws.
  2. Add security headers like Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  3. Publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting of security issues.
  4. Enhance incident response transparency by providing security contact channels or dedicated email addresses.
  5. Regularly audit and update third-party scripts and libraries to mitigate potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
AMI Insurance
Description
On your side, caring for New Zealanders since 1926. Get a quote and buy online, manage your insurance, or make a claim.
Key services
Car insurance, Home insurance, Contents insurance, Landlord insurance, Travel insurance, Business insurance, Roadside Rescue service
Content quality
excellent
Branding
consistent

Technology

Stack
Adobe Helix RUM, Typekit Fonts, Vidyard video embed, Boomerang performance monitoring, AEM (Adobe Experience Manager) CMS
Frameworks
Adobe Helix, AEM
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Secure login portals (external links to insurance.ami.co.nz)

Analytics and tracking

Services
Akamai Boomerang
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Akamai Boomerang
Marketing tools
Adobe Helix RUM, Vidyard
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 no blocking or WAF challenges.
  2. Content is professionally presented and relevant to insurance services.
  3. Strong branding and consistent design throughout the site.
  4. Multiple trust signals including awards and financial ratings.
  5. No direct contact emails or phone numbers found in HTML; contact via forms and dedicated pages.
  6. No explicit cookie consent mechanism detected.
  7. WHOIS data for the domain is missing, likely due to it being a subdomain.
  8. Use of modern technologies and performance monitoring tools.
  9. Social media presence on Facebook, Instagram, and YouTube.
Technical notes

Notes

The website leverages a modern and robust technical infrastructure based on Adobe Experience Manager CMS, ensuring scalability and content management efficiency. Performance monitoring via Akamai Boomerang and use of CDNs contribute to fast load times and good user experience. The site is mobile-optimized and accessible, with clear navigation and SEO best practices implemented. Technical risks are minimal, though the absence of some security headers and cookie consent mechanisms indicate areas for modernization. Overall, the technical implementation supports the business goals effectively with room for incremental 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 ami.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 ami.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.