Skip to main content

Security report for paysafecard.com

PaysafeCard.com Wertkarten GmbH · Finance · Finland

High risk. 8 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

44/100

Risk levelHigh

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

PaysafeCard.com Wertkarten GmbH operates a global prepaid online payment service, enabling consumers to pay online securely without bank accounts or credit cards. The company offers prepaid codes, a prepaid Mastercard, and account management services, targeting consumers seeking alternative payment methods. The website is multilingual and professionally designed, reflecting an enterprise-level business with a strong market position under the Paysafe Group umbrella. Technically, the site uses TYPO3 CMS, hosted on AWS CloudFront, and integrates Google reCAPTCHA Enterprise and Optimizely for security and marketing. However, the absence of a valid SSL certificate and HTTPS severely impacts the security posture. Privacy and cookie policies are comprehensive and GDPR compliant, but no direct contact information or explicit security policies are found. Overall, the site is trustworthy but requires urgent security improvements.

Scanned

This is an earlier scan of paysafecard.com. View the latest report

NIS2 and GDPR posture

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

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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • 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

  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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. 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';…

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

Keep watching paysafecard.com

This scan found 18 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
0
Security headers
30
Email security
50
DNS health
85
Network security
100
GDPR outside view
0
Average
44

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.

Brand lookalikes

Add-on

Domains that imitate paysafecard.com and could be used for phishing or spoofed email, tracked in OffSeq Breach.

Tracked
17
Registered
17
Resolving
17
High or critical
0

Last checked 2026-07-03

Masked preview

  • pa••••••••.comMediumomission
  • pa•••••••••.comMediumbitsquatting
  • ra•••••••••.comMediumbitsquatting

See the full lookalike list

A one-off add-on that lists up to 20 of the highest-risk lookalikes of paysafecard.com with registration, mail-server, certificate and DNS signals.

Select it in the checkout above.

Lookalike data refreshes continuously. Monitoring on Breach alerts you when a variant is registered, gains a mail server or starts serving HTTPS.

Open in Breach(opens in a new tab)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

PaysafeCard holds a strong position in the prepaid payment market, leveraging extensive retail distribution and digital services. Its business model focuses on prepaid online payments and prepaid Mastercard offerings, appealing to users without traditional banking access. The company benefits from regulatory oversight by the Central Bank of Ireland and Mastercard licensing, enhancing credibility. The website supports multiple languages and regions, indicating a broad international reach. Marketing and analytics tools like Google Tag Manager and Optimizely are used to optimize user engagement. The lack of direct contact details on the site suggests a focus on digital self-service and support through other channels.

Security posture

The website's security posture is weak due to the lack of a valid SSL certificate and absence of HTTPS, exposing users to potential interception risks. While some security best practices are observed, such as HSTS header presence and use of reCAPTCHA Enterprise, critical gaps remain in TLS protocol support, cipher suite configuration, and session management. No explicit security policy or incident response contacts are published, limiting transparency. The site does not provide vulnerability disclosure mechanisms or security.txt files. These deficiencies pose significant risks to user data confidentiality and trust.

Recommendations

  1. Immediately install and maintain a valid SSL/TLS certificate to enable HTTPS across all pages.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and configure strong cipher suites to secure communications.
  3. Enhance HSTS policy to include subdomains and preload directives for improved security.
  4. Publish a clear security policy and incident response contact information to improve transparency and trust.
  5. Implement a vulnerability disclosure program and publish a security.txt file to facilitate responsible reporting.
  6. Add visible company contact information including support emails and phone numbers to improve user confidence.
  7. Conduct regular security audits and penetration testing to identify and remediate vulnerabilities.
  8. Improve accessibility features and performance metrics to enhance user experience and SEO.
Technical notes

Notes

The website is built on TYPO3 CMS, a mature open-source content management system, and hosted on Amazon CloudFront CDN, ensuring global content delivery. It integrates Google Maps API for store locator functionality and Google reCAPTCHA Enterprise for form security. Marketing and A/B testing are supported by Optimizely and Google Tag Manager. Despite a modern tech stack, the site lacks HTTPS due to an invalid SSL certificate, which is a critical technical flaw. Performance data is unavailable, but mobile optimization appears good based on responsive design and preloading of fonts. The site uses multiple language versions and regional targeting, indicating a well-structured international deployment. Technical debt is moderate, with urgent need to fix SSL and security configurations to avoid 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. 83/100Low22 findingsView report
Reviews of this site

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