Skip to main content

Security report for web.money

SIA Digimoney · Finance · Latvia

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

Security score

63/100

Risk levelMedium

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

WebMoney is a mature international online payment system operated by SIA Digimoney, based in Latvia. The platform offers a comprehensive suite of financial services including multi-currency digital wallets, payment acceptance, mass payouts, loans, crowdfunding, and cryptocurrency services. The website targets both individual users and businesses, providing a broad ecosystem of financial tools and business networking services. The domain is well-established with over 10 years of history, supporting the legitimacy and trustworthiness of the brand. Technically, the website employs modern web technologies such as JavaScript, CSS, and integrates analytics tools like Google Analytics and Microsoft SignalR for real-time features. However, the site suffers from slow load times and a large page size, which could impact user experience. Mobile optimization is good, with adaptive design elements ensuring usability across devices. From a security perspective, the website has critical deficiencies. It lacks a valid SSL certificate and does not support any TLS protocols, exposing users to potential risks. Security headers and best practices are absent, and no cookie consent mechanism is implemented, raising privacy compliance concerns. These issues significantly reduce the security posture and trustworthiness of the site. Overall, while WebMoney demonstrates strong business credibility and a rich service offering, urgent improvements in security infrastructure and privacy compliance are necessary to protect users and maintain trust. Strategic recommendations include implementing HTTPS with modern TLS, enabling security headers, and establishing clear privacy and cookie policies.

Scanned

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

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
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 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

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

Keep watching web.money

This scan found 22 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
75
Security headers
30
Email security
70
DNS health
80
Network security
100
GDPR outside view
25
Average
63

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

WebMoney holds a strong position in the online payment and financial services market, particularly in Russian-speaking and CIS regions. Its competitive advantage lies in a wide range of integrated services including cryptocurrency wallets, credit and debt services, crowdfunding, and business networking. The business model is based on transaction fees, financial product offerings, and ecosystem services. The target customers include individuals needing secure online payments and businesses requiring payment acceptance and mass payout solutions. The company shows growth through diversified services and partnerships with digital marketplaces and financial platforms. The partnership ecosystem includes services like CashBox, Digiseller, and Megastock, enhancing its market reach and service depth.

Security posture

The current security maturity level of WebMoney's website is low due to the absence of HTTPS and modern TLS protocols, which is a critical vulnerability. The lack of security headers and cookie consent mechanisms further weakens the security and privacy posture. No incident response or security policy information is publicly available, indicating potential gaps in security governance and transparency. While the domain registration is legitimate and consistent, the website's technical security controls require immediate enhancement to mitigate risks such as data interception, man-in-the-middle attacks, and privacy violations. Compliance with GDPR and other data protection regulations appears minimal, increasing regulatory risk.

Recommendations

  1. Implement a valid SSL/TLS certificate and enable HTTPS with TLS 1.2 or 1.3 protocols to secure data in transit.
  2. Add essential security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to protect against common web attacks.
  3. Develop and publish comprehensive privacy and cookie policies with explicit consent mechanisms to improve GDPR compliance.
  4. Establish and disclose an incident response policy and dedicated security contact channels to enhance transparency and trust.
  5. Optimize website performance by reducing page size and resource count to improve user experience and reduce attack surface.
Technical notes

Notes

The website uses a modern front-end stack with JavaScript, CSS, and HTML5, supported by external libraries such as Microsoft SignalR for real-time communication and Google Analytics for tracking. The hosting environment is distributed across multiple IPs and name servers, indicating a robust infrastructure. However, the site suffers from slow load times (over 11 seconds) and a large number of resources (273), which may degrade user experience. Mobile optimization is well-implemented with adaptive CSS. The absence of a CMS or framework identification suggests a custom-built or proprietary platform. Technical debt is evident in the lack of SSL and security best practices, posing 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. 75/100Medium15 findings · partial scanView report
Reviews of this site

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