Skip to main content

Security report for m0.org

M0 FOUNDATION · Finance · N/a

Low risk. 3 critical or high findings in Security headers and SSL/TLS.

Security score

76/100

Risk levelLow

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

M0 Foundation operates a universal stablecoin platform that provides programmable, interoperable stablecoin infrastructure for builders, integrators, and fintech companies. The platform enables customization of stablecoins with robust reserve backing and shared liquidity, positioning itself as a key infrastructure player in the digital dollar and decentralized finance space. The website reflects a mature and professional business with a clear focus on finance and technology sectors, supported by notable investors and a governance ecosystem. Technically, the website leverages modern web technologies including Webflow CMS, JavaScript frameworks, Google Tag Manager, Hotjar analytics, and Cloudflare security services. The site is well-optimized for performance, mobile responsiveness, and accessibility, with comprehensive privacy and cookie consent mechanisms in place. The use of Cloudflare Turnstile captcha and HTTPS ensures a secure user experience. Security posture is strong with HTTPS enforced and no visible vulnerabilities or exposed sensitive data. However, explicit security headers and a published security policy or incident response contacts are absent, representing areas for improvement. WHOIS data is privacy protected, which is typical for fintech projects, and no suspicious registration patterns were detected. Overall, M0 Foundation presents a trustworthy and professional digital presence with strong technical and security foundations. Strategic recommendations include enhancing security header implementation, publishing a security policy and incident response information, and considering a vulnerability disclosure program to further strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
83/ 100 · Low
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

3 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. 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 m0.org

This scan found 20 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
72
Security headers
30
Email security
85
DNS health
85
Network security
100
GDPR outside view
83
Average
76

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

M0 Foundation targets the growing market of stablecoin issuance and integration by offering a programmable, federated stablecoin infrastructure. Its business model centers on providing platform services to stablecoin builders, integrators, and fintechs, enabling them to customize digital dollars with compliance and risk controls. The presence of investor logos and governance portals indicates a well-supported ecosystem and community governance model. The platform's open issuer model and shared liquidity network provide competitive advantages in flexibility and interoperability. Growth indicators include active documentation, research portals, and a careers page, suggesting ongoing development and ecosystem expansion.

Security posture

The website demonstrates a mature security posture with enforced HTTPS, use of Cloudflare Turnstile captcha, and cookie consent mechanisms aligned with GDPR. No exposed sensitive data or vulnerable libraries were detected. However, the absence of explicit security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options is a gap. There is no published security policy or incident response contact information, which limits transparency and readiness for security incidents. No vulnerability disclosure program or security.txt file was found, which could enhance community trust and coordinated vulnerability management. Overall, the security posture is good but can be improved with formal policies and header implementations.

Recommendations

  1. Implement and verify comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  2. Publish a clear security policy and incident response contact information on the website.
  3. Establish a vulnerability disclosure program and consider adding a security.txt file to facilitate responsible reporting.
  4. Maintain and regularly update privacy and cookie policies to ensure ongoing GDPR compliance.
  5. Enhance contact information availability, including direct support emails or phone numbers, to improve business credibility and user trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
M0 FOUNDATION
Description
M0 is the infrastructure powering builders of safe, programmable, interoperable stablecoins. It enables building application-specific digital dollars with customizable access, risk, and compliance rules, and supports a federated issuer model.
Key services
Stablecoin issuance infrastructure, Programmable stablecoin customization, Shared liquidity network, Governance portal, Ecosystem dashboard
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, jQuery, Google Tag Manager, Google Analytics, Hotjar, Cloudflare Turnstile Captcha, Spline (3D web graphics), Webflow CMS
Frameworks
Webflow
Platforms
Cloudflare (likely for CDN and security), Google Cloud (implied by Google services)
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Captcha (Cloudflare Turnstile) used
  • Cookie consent with opt-in mechanism
  • No exposed sensitive data in HTML
  • Use of security-focused third-party services (Cloudflare, Hotjar)

Analytics and tracking

Services
Google Analytics, Hotjar
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Twitter Ads
Tracking pixels
Hotjar
Marketing tools
Hotjar
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 interactive elements.
  2. Strong focus on stablecoin infrastructure and programmable digital dollars.
  3. Comprehensive privacy and cookie consent mechanisms implemented.
  4. No direct contact emails or phone numbers publicly listed; contact via form only.
  5. Use of modern web technologies and analytics tools.
  6. Investor logos and governance portals indicate established ecosystem.
  7. No security.txt or explicit security policy found.
  8. WHOIS data is privacy protected with no registrar or registrant details available.
Technical notes

Notes

The website is built on a modern technology stack with Webflow CMS, JavaScript, and integration of analytics and marketing tools such as Google Tag Manager and Hotjar. It uses Cloudflare services for CDN and security, including Turnstile captcha for bot protection. The site is well-optimized for performance and mobile responsiveness, with good accessibility features. The presence of 3D graphics via Spline adds to the user experience. No technical debt or outdated libraries were detected. The site uses canonical URLs and proper meta tags for SEO. Overall, the technical infrastructure is robust, scalable, and aligned with best practices for fintech platforms.
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 m0.org. 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 m0.org.

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.