Skip to main content

Security report for paysend.com

Paysend · Finance · N/a

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

69/100

Risk levelMedium

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

Paysend.com is a financial technology platform specializing in international money transfers and payment services. The domain is well-established since 2004 and uses Cloudflare for security and performance. However, the website content is currently inaccessible due to a Cloudflare security challenge page, which prevents a full analysis of the site's content, policies, and contact information. The business appears to be a mature fintech entity with a focus on cross-border payments, but no detailed business or security policies are visible in the provided content.

Scanned

NIS2 and GDPR posture

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

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

    • High

      Third-party services without privacy policy

      Detected services: Cloudflare

      What to do: Document all third-party data sharing in your privacy policy

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

Keep watching paysend.com

This scan found 23 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
52
Security headers
65
Email security
75
DNS health
85
Network security
100
GDPR outside view
35
Average
69

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

Paysend operates in the finance sector, targeting individuals and businesses requiring fast and cost-effective international money transfers. The business model is fintech-based, offering payment processing and remittance services. The domain age and registrar data support legitimacy and maturity. Due to content blocking, detailed insights into revenue streams, partnerships, or growth indicators are unavailable. No subsidiary or partner domains were identified from the content.

Security posture

The website employs Cloudflare as a security and performance provider, which is a positive indicator. However, the absence of visible security headers, privacy policies, cookie consent mechanisms, and incident response information limits the assessment of security maturity. The domain lacks DNSSEC, which is recommended for enhanced DNS security. No vulnerabilities or exposed sensitive data were detected, but the inability to access full content restricts comprehensive evaluation. The security score is low due to content blocking and missing policies.

Recommendations

  1. Implement and expose clear privacy and cookie policies with GDPR compliance indicators.
  2. Publish terms of service and incident response contact information including abuse and security contacts.
  3. Enable DNSSEC to improve domain name system security.
  4. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Ensure website content is accessible without WAF challenges for better user experience and analysis.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. The HTML content indicates a Cloudflare security challenge page with title 'Just a moment...' and embedded font data, typical of Cloudflare's anti-bot protection. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Company
Paysend
Description
Paysend is a financial technology company specializing in international money transfers and payment services.
Key services
International money transfers, Payment processing, Cross-border payments
Content quality
poor

Technology

Stack
Cloudflare, Custom fonts embedded via base64, JavaScript

Analytics and tracking

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is blocked by Cloudflare security challenge, preventing full content analysis.
  2. No visible privacy, cookie, or terms of service policies in the provided HTML.
  3. No contact information or forms detected in the provided content.
  4. WHOIS data indicates a well-established domain with no privacy protection.
  5. Technical content is minimal due to blocking; embedded fonts and Cloudflare usage detected.
  6. No security headers or policies visible in the provided content.
  7. No analytics or advertising scripts detected in the truncated HTML.
  8. Content safety is rated safe with no adult or explicit content.
Technical notes

Notes

The website uses Cloudflare for DNS and security, with embedded custom fonts via base64 encoding. No CMS or frameworks were detected in the limited content. The site appears to rely on JavaScript and custom code. Performance, mobile optimization, and SEO cannot be assessed due to content blocking. Hosting is via Cloudflare's infrastructure. Technical debt or modernization opportunities cannot be determined from the available data.
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 paysend.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 paysend.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.