Skip to main content

Security report for mapprotocol.io

MAP Protocol · Technology · Finland

Medium risk. 8 critical or high findings in Email security, Security headers and 2 other checks.

Security score

60/100

Risk levelMedium

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

MAP Protocol is a blockchain infrastructure company focused on enabling omnichain interoperability for Bitcoin, stablecoins, and tokenized assets. It provides a peer-to-peer cross-chain network leveraging advanced cryptographic technologies such as light clients and MPC-based threshold signature schemes. The company targets developers, enterprises, and blockchain users seeking seamless cross-chain asset swaps and decentralized finance applications. MAP Protocol positions itself as a Bitcoin Layer-2 solution and a gateway to the broader interoperable blockchain ecosystem. Technically, the website is built on a modern React and Next.js stack with Material-UI components, hosted on AWS infrastructure. The site is well-optimized for performance and mobile devices, with good SEO and accessibility basics. However, it lacks some advanced security headers and explicit privacy and security policies. The domain is registered in Finland with a reasonable registration age, indicating a legitimate and professional operation. From a security perspective, the site uses HTTPS and has domain transfer protections but does not publish detailed security policies or incident response contacts. No vulnerabilities or exposed sensitive data were detected in the provided content. Cookie consent is implemented, but privacy policy and terms of service are missing or not easily found. Overall, MAP Protocol presents a credible and professional blockchain infrastructure business with a strong technical foundation and community focus. To improve trust and compliance, it should publish comprehensive privacy and security policies, implement security headers, and provide vulnerability disclosure information.

Scanned

NIS2 and GDPR posture

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

8 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. 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';…

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

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

Keep watching mapprotocol.io

This scan found 25 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
20
Email security
40
DNS health
70
Network security
100
GDPR outside view
65
Average
60

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention mapprotocol.io, from OffSeq Breach.

Total records
7
Employees
0
Customers
7
Third parties
0
Weak passwords
0%

1 subdomain affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for mapprotocol.io.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

MAP Protocol operates in the blockchain interoperability sector, focusing on Bitcoin Layer-2 solutions and omnichain asset swaps. Its competitive advantage lies in peer-to-peer cross-chain technology without reliance on trusted third parties, leveraging light client and MPC-based cryptography. The business model includes providing infrastructure, developer tools, and community governance via MAPDAO. Revenue streams likely include network fees, staking incentives, and enterprise services. The target customers are blockchain developers, DeFi projects, and enterprises seeking cross-chain capabilities. The company shows growth indicators such as active node participation and a growing user base. Partnerships with major blockchain ecosystems and open-source transparency strengthen its market position.

Security posture

The security maturity level is moderate. The use of HTTPS and domain transfer lock are positive indicators. However, the absence of security headers, vulnerability disclosure policies, and incident response contacts represent gaps. No exposed sensitive data or vulnerable libraries were detected. The cookie consent mechanism supports privacy compliance but lacks a linked privacy policy. The company should enhance its security posture by implementing recommended headers, publishing security policies, and establishing formal incident response channels. Overall, the security culture appears emerging but not fully mature.

Recommendations

  1. Publish a comprehensive privacy policy and terms of service accessible from the website footer.
  2. Implement and configure security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Enable DNSSEC for the domain to improve DNS security.
  4. Create and publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  5. Provide explicit incident response contact channels such as security@ or abuse@ email addresses.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
MAP Protocol
Description
MAP Protocol is an omnichain infrastructure enabling efficient, secure, and seamless cross-chain swaps between BTC, stablecoins, and tokenized assets. It leverages light client technology and MPC-based threshold signature schemes to build an interoperable bridge connecting Bitcoin mainnet with multi-chain stablecoin ecosystems including Ethereum, BNB, Tron, Solana, and more.
Key services
Omnichain swap network for BTC, stablecoins, and tokenized assets, Developer toolkit including SDK and documentation, MAP Relay Chain network operated by nodes, Community governance via MAPDAO
Content quality
good
Branding
consistent

Technology

Stack
React, Next.js, Material-UI, JavaScript
Frameworks
Next.js, Material-UI
Platforms
Web
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • Domain status clientTransferProhibited to prevent unauthorized transfers

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is fully accessible with rich content and no blocking detected.
  2. No explicit privacy policy or terms of service found on the homepage content.
  3. Cookie consent popup is present and functional.
  4. Contact email cooperation@maplabs.io is provided in footer.
  5. No phone numbers or physical addresses explicitly listed on the site.
  6. No forms detected on the homepage for data collection.
  7. Modern React/Next.js tech stack with Material-UI for UI components.
  8. No analytics or tracking scripts explicitly detected in provided HTML.
  9. No security.txt or vulnerability disclosure information found.
  10. No certifications or security frameworks mentioned.
Technical notes

Notes

The website uses a modern and performant technology stack including React, Next.js, and Material-UI, hosted on AWS infrastructure. The site is mobile optimized and SEO friendly with proper meta tags and structured content. No CMS detected, indicating a custom or framework-based build. Performance is fast with deferred script loading. Accessibility is basic but present. Technical risks include lack of security headers and incomplete privacy compliance documentation. There is an opportunity to improve technical maturity by adding security best practices and formalizing privacy and security documentation.
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 mapprotocol.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 mapprotocol.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.