Skip to main content

Security report for moonpay.com

MoonPay · Finance · N/a

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

Security score

75/100

Risk levelMedium

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

MoonPay operates as a leading fiat-to-cryptocurrency payment gateway, facilitating instant purchases of cryptocurrencies such as Bitcoin and Ethereum. The company positions itself as a marketplace bridging crypto exchanges and users, offering multiple payment methods including credit cards, bank transfers, Apple Pay, and PayPal. The website reflects a mature digital presence with professional branding and comprehensive content aimed at cryptocurrency users and investors. Technically, the site leverages modern frameworks like Next.js and React, integrates advanced analytics and marketing tools, and implements strong privacy and cookie consent mechanisms. Security posture is solid with HTTPS enforcement and security headers, though the absence of a published security policy and incident response details is a gap. The WHOIS data is notably missing, which raises concerns about domain transparency and legitimacy despite the professional front-end and business model. Overall, MoonPay presents a trustworthy and well-structured platform in the crypto finance sector but should improve domain registration transparency and security communication to enhance trust further.

Scanned

NIS2 and GDPR posture

GDPR outside view
88/ 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 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 moonpay.com

This scan found 19 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
82
DNS health
80
Network security
100
GDPR outside view
88
Average
75

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

MoonPay's market positioning as a fiat-to-crypto gateway places it in a competitive niche within the finance and technology sectors. Its business model focuses on facilitating seamless crypto purchases for retail users, leveraging partnerships with crypto exchanges. The company targets a broad audience of crypto investors and users seeking easy access to digital assets. Revenue streams likely include transaction fees and payment processing charges. The website's integration with multiple analytics and marketing platforms indicates a data-driven growth strategy. Social media presence and job board links suggest ongoing expansion and talent acquisition. However, the lack of visible physical addresses or direct contact details may limit some user trust. The missing WHOIS data is a notable anomaly that could impact perceived legitimacy. Strategic partnerships and certifications are not explicitly highlighted, representing an opportunity for MoonPay to strengthen its ecosystem and credibility.

Security posture

MoonPay demonstrates a good security baseline with HTTPS, security headers, and cookie consent compliance. The use of OneTrust for consent management and multiple analytics tools is balanced with privacy considerations. However, the absence of a dedicated security policy, incident response plan, or vulnerability disclosure program reduces transparency and preparedness perception. No direct security contact emails were found, which could hinder incident reporting and response. The missing WHOIS data is a significant concern from a trust and legitimacy perspective. No obvious vulnerabilities or exposed sensitive data were detected in the site content or scripts. To elevate security maturity, MoonPay should publish clear security policies, establish a vulnerability disclosure channel, and consider recognized security certifications. These steps would enhance user confidence and regulatory compliance.

Recommendations

  1. Publish a comprehensive security policy and incident response page accessible from the website footer.
  2. Implement and publicize a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  3. Provide explicit security contact information such as security@moonpay.com or abuse@moonpay.com.
  4. Investigate and resolve the missing WHOIS domain registration data to improve domain transparency and trust.
  5. Regularly audit and update third-party scripts and analytics tools to minimize security risks.

Contact details published on the site

Legal name
Moon Pay Limited
Registration number
company number 12055543
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
MoonPay
Description
MoonPay is the new standard for fiat to crypto. We are a marketplace between crypto exchanges and users, facilitating instant purchases of cryptocurrencies.
Key services
Instant cryptocurrency purchases, Payment processing via credit card, bank transfers, Apple Pay, PayPal
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, Google Tag Manager, AppsFlyer, OneTrust, Segment Analytics, Swiper.js
Frameworks
Next.js
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of security headers
  • Cookie consent mechanism implemented
  • No exposed sensitive data detected

Analytics and tracking

Services
Google Analytics (via GTM), Segment Analytics, AppsFlyer, Ahrefs Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
AppsFlyer, Ahrefs Analytics
Marketing tools
Segment Analytics, AppsFlyer
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 cryptocurrency fiat-to-crypto transactions.
  3. Comprehensive privacy and cookie policies with consent management.
  4. No direct contact emails or phone numbers found on main pages; contact via form only.
  5. Use of multiple analytics and marketing tools with consent mechanisms.
  6. No explicit security policy or incident response information published.
  7. WHOIS data missing, which reduces domain transparency and trust.
  8. No adult or questionable content detected; content is safe for general audiences.
Technical notes

Notes

The website is built on a modern technology stack including React and Next.js, ensuring server-side rendering and good performance. Integration with Google Tag Manager, AppsFlyer, Segment Analytics, and OneTrust indicates a sophisticated approach to analytics, marketing, and privacy compliance. The site is mobile-optimized with responsive design and accessibility considerations. Performance appears fast with efficient resource loading and minimal blocking scripts. No CMS was explicitly detected, suggesting a custom or headless architecture. Hosting provider details are not explicit but likely cloud-based. Technical debt appears low, but the site could benefit from enhanced security documentation and domain registration transparency. Overall, the technical infrastructure 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

Earlier scans of this domain

  1. 75/100 +2Medium26 findingsView report
  2. 73/100Medium25 findingsView report
Reviews of this site

Share your experience with moonpay.com. 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 moonpay.com.

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.