Skip to main content

Security report for nexusmutual.io

Collective Risk Services CIC · Finance · United Kingdom

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

Security score

69/100

Risk levelMedium

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

Nexus Mutual is a pioneering decentralized crypto insurance platform leveraging blockchain and Ethereum technology to provide risk coverage without traditional insurance companies. Established in 2017 and operated by Collective Risk Services CIC in the UK, it serves both individual and institutional clients, protecting over $5.75 billion in crypto assets. The platform offers tailored cover plans, transparent claims processing, and a substantial capital pool, positioning itself as a market leader in crypto insurance. The website reflects a professional and trustworthy brand with strong client testimonials and media recognition. Technically, the site is built on Webflow CMS, integrates Google Analytics and Tag Manager for tracking, and uses Cookiebot for cookie consent management. It is hosted with Cloudflare DNS and uses Amazon Registrar for domain management. The site is mobile-optimized, accessible, and SEO-friendly, with modern web technologies and blockchain API integrations enhancing its digital maturity. Security-wise, the site enforces HTTPS with domain registration locks and cookie consent, but lacks explicit security policies, incident response contacts, and security headers. DNSSEC is not enabled, representing an area for improvement. No vulnerabilities or exposed sensitive data were detected. Privacy compliance is strong with comprehensive privacy and terms documents and GDPR-aligned cookie consent. Overall, Nexus Mutual presents a high-quality, secure, and credible online presence suitable for its fintech audience. Strategic recommendations include enabling DNSSEC, publishing security policies and incident response contacts, and implementing security headers to further strengthen its security posture.

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 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 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
    • 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 nexusmutual.io

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. 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
47
Security headers
30
Email security
85
DNS health
85
Network security
100
GDPR outside view
68
Average
69

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

Nexus Mutual occupies a leading position in the decentralized crypto insurance market, offering innovative risk-sharing solutions via blockchain. Its business model focuses on providing bespoke insurance covers for crypto assets and DeFi protocols, targeting both retail and institutional investors. The company benefits from a robust partnership ecosystem including developer communities, analytics providers, and governance forums. Revenue streams likely include cover premiums and capital pool management. The presence of high-profile clients and media coverage indicates strong market trust and growth potential. The use of privacy protection in domain registration is justified given the financial nature of the business. The company demonstrates a mature digital presence with clear branding and comprehensive content supporting its market leadership.

Security posture

The website demonstrates a good security maturity level with enforced HTTPS, domain registration locks, and cookie consent mechanisms. However, it lacks published security policies, incident response contacts, and vulnerability disclosure programs, which are important for transparency and trust in the fintech sector. DNSSEC is not enabled, which could expose DNS spoofing risks. No security headers such as CSP or HSTS were detected, representing a potential area for enhancement. No exposed sensitive data or vulnerable libraries were found. Overall, the security posture is solid but could be improved by adopting additional best practices and publishing relevant security documentation.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Publish a dedicated security policy page outlining security practices and controls.
  3. Provide clear incident response contact channels such as security@ or abuse@ emails.
  4. Implement security headers including Content Security Policy (CSP), HSTS, and X-Frame-Options.
  5. Establish a vulnerability disclosure program or publish a security.txt file to encourage responsible reporting.

Contact details published on the site

Addresses
Legal name
Collective Risk Services CIC
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Collective Risk Services CIC
Description
Nexus Mutual uses blockchain technology and Ethereum to allow people worldwide to share risk together without the need for an insurance company.
Key services
Crypto insurance covers, Claims processing, Tailored cover plans, Risk pooling
Content quality
excellent
Branding
consistent

Technology

Stack
Ethereum blockchain, Google Analytics, Google Tag Manager, Cookiebot, Webflow CMS, jQuery, Dune Analytics API
Frameworks
Webflow
Platforms
Cloudflare DNS, Amazon Registrar
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • ClientDeleteProhibited, clientTransferProhibited, clientUpdateProhibited domain statuses
  • Cookie consent mechanism implemented

Analytics and tracking

Services
Google Analytics, Google Tag Manager, Dune Analytics API
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Cookiebot
Marketing tools
Cookiebot
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with rich content and professional design.
  2. Strong focus on crypto insurance and blockchain technology.
  3. Multiple trusted client testimonials and media mentions.
  4. Comprehensive privacy and terms documents available.
  5. Cookie consent implemented via Cookiebot.
  6. No direct company emails or phone numbers found; contact via form and physical address only.
  7. No explicit security policy or incident response info published.
  8. No security.txt or vulnerability disclosure found.
  9. Modern tech stack with Webflow CMS and blockchain integration.
  10. Good SEO and accessibility practices observed.
Technical notes

Notes

The website is built using Webflow CMS, leveraging modern web technologies including jQuery and Google Analytics integrations. It uses Cloudflare for DNS and Amazon Registrar for domain management. Performance is fast with good mobile optimization and accessibility features. The site includes dynamic data fetching from Dune Analytics API for real-time metrics. SEO is well implemented with comprehensive meta tags and Open Graph data. The technical infrastructure is modern and well-maintained, though enabling DNSSEC and adding security headers would further enhance robustness. The use of cookie consent tools aligns with privacy regulations. Overall, the technical implementation supports a professional and scalable online presence.
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 nexusmutual.io. 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 nexusmutual.io.

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.