Skip to main content

Security report for utrust.com

xMoney · Finance · Romania

Low risk. 3 critical or high findings in GDPR outside view and SSL/TLS.

Security score

78/100

Risk levelLow

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

xMoney is a financial technology company offering a comprehensive payment ecosystem that empowers businesses to accept global payments, manage finances, and issue branded cards. The platform targets merchants and enterprises across Europe and beyond, providing services such as payments, recurring billing, marketplaces, invoicing, and crypto payment acceptance. The company positions itself as a licensed and compliant entity with certifications including PCI DSS Level 1 and MiCA compliance, regulated by the Bank of Romania. The website reflects a mature digital presence with professional design, clear navigation, and extensive product information. Technically, xMoney leverages modern web technologies including Webflow CMS, Google Tag Manager, Microsoft Clarity, and Bing Ads for analytics and marketing. The site is well-optimized for performance, mobile responsiveness, and accessibility. Security practices are strong, with HTTPS enforced, advanced fraud prevention powered by AI, and compliance with payment security standards. However, explicit security headers and incident response disclosures could be improved. The security posture is robust but slightly diminished by the absence of WHOIS registration data, which raises questions about domain legitimacy. No WAF or blocking mechanisms were detected, and the site is fully accessible. Privacy compliance is well addressed with cookie consent mechanisms and a comprehensive privacy policy. Overall, xMoney presents a trustworthy and professional payment platform with strong technical and security foundations. Strategic recommendations include enhancing visible security headers, publishing vulnerability disclosure and incident response information, and clarifying domain registration details to improve trust and compliance transparency.

Scanned

NIS2 and GDPR posture

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

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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

  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
    • High

      SSL Certificate Expires Soon

      SSL certificate expires in 29 days

      What to do: Renew SSL certificate before expiration

      • NIS2 21(2)(h)
      • IR 2024/2690 9.2(c): Implementing Regulation (EU) 2024/2690, Annex point 9.2(c): Cryptography
      • NIST SC-17: NIST SP 800-53 Rev. 5 SC-17: Public Key Infrastructure Certificates

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

Keep watching utrust.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
62
Security headers
60
Email security
80
DNS health
85
Network security
100
GDPR outside view
80
Average
78

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

xMoney operates in the finance and technology sectors, focusing on payment processing and financial management solutions for businesses. Its business model is SaaS and API-driven, targeting startups, SMEs, and enterprises seeking to scale globally. The company demonstrates competitive advantages through licensing, regulatory compliance, and a broad product suite that includes crypto payments and marketplace solutions. Revenue streams likely include transaction fees, subscription billing, and card issuing services. The partnership ecosystem includes major payment networks like VISA and MasterCard, and government entities, indicating strong market credibility. Growth indicators include over 20,000 businesses using their platform and endorsements from notable clients. The company emphasizes innovation, security, and ease of integration to maintain market position.

Security posture

xMoney exhibits a mature security posture with PCI DSS Level 1 certification, AI-powered fraud prevention, and implementation of SCA and 3D Secure 2.0 for transaction security. The use of tokenized cards reduces liability risks. HTTPS is enforced site-wide, and no exposed sensitive data or vulnerable libraries were detected. However, the absence of explicit security headers such as Content-Security-Policy and a security.txt file limits transparency in vulnerability management. Incident response and security policy pages are not publicly available, which could impact readiness and trust. Privacy compliance is strong with GDPR-aligned cookie consent. Overall, the security culture appears robust but could benefit from enhanced public disclosures and header configurations.

Recommendations

  1. Implement and enforce Content-Security-Policy and other security headers to mitigate XSS and clickjacking risks.
  2. Publish a security.txt file and a dedicated vulnerability disclosure policy to facilitate responsible reporting.
  3. Create and maintain incident response and security policy pages to improve transparency and preparedness.
  4. Verify and update WHOIS domain registration information to ensure legitimacy and build trust.
  5. Continue enhancing privacy compliance measures and provide clear data retention policies.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
xMoney
Description
xMoney provides a unified financial ecosystem enabling businesses to accept global payments, split transactions, manage finances, and issue cards.
Key services
Payments, Recurring Billing, Marketplaces, Card Issuing, Invoices, Payment Links
Content quality
excellent
Branding
consistent

Technology

Stack
Webflow, Google Tag Manager, Microsoft Bing Ads, Microsoft Clarity, Finsweet Cookie Consent, jQuery 3.5.1
Frameworks
Webflow CMS
Platforms
Webflow Hosting
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • PCI DSS Level 1 Certified
  • Tokenized card data
  • SCA & 3D Secure 2.0 implemented
  • AI-powered fraud prevention

Analytics and tracking

Services
Google Analytics (via GTM implied), Microsoft Clarity
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Microsoft Bing Ads
Tracking pixels
Microsoft Clarity
Marketing tools
Microsoft Clarity
Transparency
good

Site quality

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

Key observations

  1. Website is professionally designed and fully functional.
  2. Strong focus on payment and financial services with clear product offerings.
  3. Comprehensive cookie consent and privacy policy present.
  4. No direct contact emails or phone numbers publicly listed; contact via forms.
  5. No visible security.txt or vulnerability disclosure policy.
  6. WHOIS data missing, which is unusual for an active financial services domain.
  7. Use of modern tracking and analytics tools with GDPR compliance.
  8. Multiple social media channels linked and active.
  9. No signs of WAF or content blocking.
Technical notes

Notes

The website is built on Webflow CMS, utilizing modern JavaScript libraries and analytics tools such as Google Tag Manager and Microsoft Clarity. The hosting is provided by Webflow, ensuring good performance and uptime. The site is mobile-optimized with responsive design and accessibility considerations. SEO is supported by comprehensive meta tags and Open Graph data. The technical implementation is clean with no broken elements detected. However, there is room for improvement in security header implementation and explicit documentation of security practices. The use of multiple tracking and marketing tools is balanced with GDPR-compliant cookie consent mechanisms.
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 utrust.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 utrust.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.