Skip to main content

Security report for native.inc

Native · Finance · N/a

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

Native is a specialized insurance brokerage focused on digital assets and the crypto-native ecosystem. They leverage decades of experience to provide bespoke insurance and risk management solutions tailored for onchain and offchain risks, integrating traditional insurance with blockchain technology. Their services include onchain capital insurance, smart contract-based policy execution, and crypto-denominated policies, positioning them as a niche player bridging legacy insurance and web3 innovation. Technically, the website is built on modern frameworks such as Next.js and React, with content managed likely via Contentful CMS. The site demonstrates good design and mobile optimization but lacks comprehensive SEO and accessibility features. Security posture is moderate with no visible security headers or explicit SSL details in the provided data, and privacy compliance is weak due to absence of privacy and cookie policies. No contact emails or phone numbers are visible, limiting direct communication channels. Overall, the site is professional and safe but would benefit from enhanced security practices and compliance transparency.

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

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

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

Keep watching native.inc

This scan found 23 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
75
Security headers
60
Email security
55
DNS health
75
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

Native operates in the finance and technology sectors, targeting crypto-native businesses requiring specialized insurance solutions. Their business model centers on brokerage and risk management services that combine traditional insurance expertise with blockchain technology. The company emphasizes partnerships with legacy insurers and blockchain innovators to deliver comprehensive risk coverage. Their market positioning is as a forward-looking broker for the web3 era, offering unique products such as crypto-denominated policies and onchain claims processing. The target audience includes crypto projects, blockchain companies, and digital asset holders. The company appears small in size with no public parent or subsidiary information. The use of HubSpot forms indicates a structured lead capture and marketing approach. However, lack of visible contact details and compliance documentation may impact trust and conversion.

Security posture

The website currently exhibits a moderate security posture. HTTPS is presumed but not explicitly confirmed in the data. No security headers such as Content-Security-Policy, X-Frame-Options, or Strict-Transport-Security were detected, which are important for mitigating common web attacks. There is no evidence of exposed sensitive data or vulnerable libraries in the provided scripts. The use of modern frameworks like Next.js is positive but requires proper configuration to ensure security. Absence of privacy and cookie policies indicates compliance gaps, and no incident response or security contact information is provided. Overall, the security maturity appears basic and would benefit from implementing standard security headers, publishing privacy and cookie policies, and establishing clear incident response channels.

Recommendations

  1. Implement and publish comprehensive privacy and cookie policies to improve GDPR compliance and user trust.
  2. Add standard security headers (Content-Security-Policy, X-Frame-Options, Strict-Transport-Security) to enhance protection against common web vulnerabilities.
  3. Provide clear and accessible contact information including emails and phone numbers for sales, support, and security incidents.
  4. Conduct a security audit to identify and remediate any potential vulnerabilities in the web application and infrastructure.
  5. Enhance SEO and accessibility features to improve discoverability and usability for a broader audience.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Native
Description
Native is a global broker dedicated to digital assets, focusing on addressing unique risks in the crypto-native and onchain ecosystem. They combine crypto and insurance expertise to build solutions for onchain, offchain, and beyond, leveraging technology such as smart contracts and crypto-denominated policies.
Key services
Onchain capital insurance, Risk management ecosystem bridging traditional and web3 insurance, Crypto-denominated insurance policies, Onchain claims processing
Content quality
good
Branding
consistent

Technology

Stack
Next.js, React, Normalize.css, JavaScript
Frameworks
Next.js
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
40/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Marketing tools
HubSpot forms (share-eu1.hsforms.com)
Transparency
poor

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
basic
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website uses modern JavaScript frameworks (Next.js, React).
  2. Content is focused on crypto-native insurance brokerage services.
  3. No visible privacy, cookie, or terms of service policies found.
  4. No explicit contact emails or phone numbers found in the HTML content.
  5. External links limited to CDN and HubSpot form service.
  6. No social media links detected in the provided HTML.
  7. No security headers or explicit SSL configuration details available.
  8. No signs of adult or questionable content.
  9. No WAF or blocking detected; content fully accessible.
Technical notes

Notes

The website is built using Next.js and React frameworks, leveraging Normalize.css for CSS normalization. Content appears to be managed via a headless CMS, likely Contentful, as inferred from JSON data structures. The site loads multiple JavaScript chunks asynchronously, indicating a modular and modern frontend architecture. Performance is moderate with deferred script loading, but no explicit performance metrics are available. Mobile optimization is good based on responsive meta tags and CSS variables. SEO optimization is basic with minimal meta tags and no Open Graph or JSON-LD structured data detected. No hosting provider information is available from the HTML content. The technical stack is modern but could be improved with enhanced SEO, accessibility, and security configurations.
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 native.inc. 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 native.inc.

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.