Skip to main content

Security report for exchanger.money

exchanger.money · Finance · N/a

Medium risk. 6 critical or high findings in Security headers and GDPR outside view.

Security score

68/100

Risk levelMedium

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

Exchanger.Money operates as a specialized online platform facilitating the exchange of various currencies and WebMoney title units among participants of the WebMoney Transfer system. The service emphasizes direct peer-to-peer transactions without intermediaries, offering a wide array of payment methods including bank cards, electronic wallets, money transfer systems, and cryptocurrencies. The platform targets users within the WebMoney ecosystem and those seeking flexible currency exchange options. Technically, the website is built using modern JavaScript frameworks such as Vue.js, indicating a moderate level of digital maturity. However, performance is hindered by slow load times and a lack of optimization. Security posture is weak due to the absence of a valid SSL certificate and HTTPS support, exposing users to potential risks during transactions. Privacy compliance is minimal, with no cookie consent mechanisms or GDPR indicators present. Overall, while the business model and market positioning are clear and relevant, significant improvements in security and privacy practices are necessary to enhance trust and protect users.

Scanned

This is an earlier scan of exchanger.money. View the latest report

NIS2 and GDPR posture

GDPR outside view
40/ 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 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';…

  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

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

Keep watching exchanger.money

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
85
Security headers
15
Email security
85
DNS health
80
Network security
100
GDPR outside view
40
Average
68

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 exchanger.money, from OffSeq Breach.

No leaked records found

Breach holds no records for exchanger.money right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

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

The platform occupies a niche in the financial technology sector, focusing on currency exchange within the WebMoney ecosystem. Its competitive advantage lies in the absence of intermediary commissions and a broad selection of payment methods, appealing to a diverse user base. Revenue likely derives from transaction facilitation, although explicit monetization details are not provided. The partnership ecosystem includes other exchanges such as INDX, WM Exchanger, and Cryptex, which may enhance liquidity and service offerings. Growth indicators include an 8-year domain age and consistent branding. However, the lack of explicit contact information and limited privacy policies may hinder user confidence and regulatory compliance.

Security posture

The current security maturity level is low, primarily due to the lack of HTTPS encryption and absence of security headers. This exposes users to risks such as data interception and man-in-the-middle attacks. No incident response or vulnerability disclosure information is available, indicating limited preparedness for security incidents. Compliance gaps with GDPR and other data protection regulations are evident, given the missing cookie consent and privacy policy details. The platform does not demonstrate a strong security culture or proactive risk management, which could impact user trust and regulatory standing.

Recommendations

  1. Implement a valid SSL/TLS certificate to enable HTTPS across the entire site immediately.
  2. Introduce comprehensive privacy and cookie policies with explicit consent mechanisms to comply with GDPR.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to harden the site.
  4. Publish an incident response plan and vulnerability disclosure policy to improve transparency and readiness.
  5. Enhance website performance through optimization techniques to improve user experience and SEO.
Technical notes

Notes

The website leverages Vue.js for frontend development, indicating a modern approach to UI/UX. However, the absence of HTTPS and security best practices represents a critical technical debt. Performance metrics show slow load times and a high number of resources, suggesting optimization opportunities. The lack of structured data and advanced SEO features limits discoverability. Hosting details are unclear, but DNS records and domain registration are consistent and mature. Overall, the technical infrastructure supports the business model but requires urgent security and performance enhancements to mitigate operational risks.
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. 63/100Medium33 findingsView report
Reviews of this site

Share your experience with exchanger.money. 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 exchanger.money.

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.