Skip to main content

Security report for gopay.cz

GoPay s.r.o. · Finance · Czech Republic

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

Security score

81/100

Risk levelLow

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

GoPay s.r.o. operates a well-established online payment gateway service primarily targeting merchants in the Czech Republic and surrounding European markets. The company offers a comprehensive suite of payment solutions including card payments, Apple Pay, Google Pay, online bank transfers, financing options, and payment terminals. With over 18,000 merchants and a decade of market presence, GoPay positions itself as a reliable and scalable payment partner for businesses of all sizes. The website reflects a professional and user-friendly design with strong branding and clear navigation, supporting multiple languages and currencies to cater to a broad audience. Technically, the website leverages modern web technologies such as Google Tag Manager, AWS hosting, and Typekit fonts, ensuring fast performance and mobile optimization. The presence of cookie consent mechanisms and privacy policies indicates a mature approach to privacy compliance. However, explicit security headers and a dedicated security policy are not clearly published, suggesting room for improvement in transparency and security communication. From a security perspective, the site enforces HTTPS and implements secure forms, but lacks publicly available incident response contacts or vulnerability disclosure programs. The absence of WHOIS registration data raises questions about domain registration transparency, although the overall business legitimacy is supported by certifications like PCI DSS and Ministry of Finance affiliation. The site shows no signs of malicious content or vulnerabilities in the visible code. Overall, GoPay demonstrates a strong market position with a professional digital presence and good security hygiene, but should enhance transparency around security policies and domain registration details to further build trust and compliance assurance.

Scanned

NIS2 and GDPR posture

GDPR outside view
65/ 100 · Medium
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 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

      Third-party services without privacy policy

      Detected services: Google Analytics, Facebook, Twitter, LinkedIn

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

  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

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

Keep watching gopay.cz

This scan found 16 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
77
Security headers
95
Email security
70
DNS health
80
Network security
100
GDPR outside view
65
Average
81

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 gopay.cz, from OffSeq Breach.

Total records
518
Employees
12
Customers
360
Third parties
146
Weak passwords
26%

Latest record dated 2026-01-12 · 26 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for gopay.cz.

Select it in the checkout above.

Masked preview

  • –alpha.dev.gopay.cz2026-01-12
  • –gopay.cz2026-01-12
  • –alpha.dev.gopay.cz2026-01-12
  • –account.alpha.dev.gopay.cz2025-11-13
  • –jenkins.gopay.cz2025-08-26

Breach keeps ingesting new leaks, so these numbers can grow between scans.

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

GoPay operates in the competitive payment gateway sector, serving a large base of merchants with a diverse portfolio of payment methods and financial services. Their business model focuses on transaction fees and value-added services such as financing and payment terminals. The company leverages partnerships and integrations to expand its reach, supported by a robust online presence and customer testimonials. Growth indicators include a decade-long market presence, over 18,000 active merchants, and continuous product innovation such as saved card features and multi-currency support. The ecosystem includes related domains for authentication, registration, help, and status monitoring, indicating a well-structured service architecture. Strategic observations highlight GoPay's focus on ease of integration, customer support, and compliance with European payment standards.

Security posture

GoPay's security posture is solid with mandatory HTTPS, PCI DSS certification, and cookie consent compliance. The website does not expose sensitive data and uses secure POST forms for data submission. However, the lack of explicit security headers like Content-Security-Policy and absence of a published security policy or incident response contact reduces transparency. No vulnerability disclosure or security.txt file was found, which is a gap in proactive security communication. The domain WHOIS data is missing, which could be a concern for domain ownership verification. Overall, the security maturity is good but could be improved by publishing detailed security policies, incident response procedures, and vulnerability disclosure mechanisms.

Recommendations

  1. Publish a dedicated security policy page detailing security controls and compliance certifications.
  2. Implement and publicize an incident response contact email and vulnerability disclosure program.
  3. Ensure all recommended security headers (CSP, X-Frame-Options, X-Content-Type-Options) are configured and documented.
  4. Clarify domain registration details or use WHOIS privacy protection with transparent business registration information.
  5. Maintain and regularly update cookie and privacy policies to reflect evolving regulations and user expectations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
GoPay s.r.o.
Description
GoPay poskytuje bezpečné a rychlé online platební řešení pro vaše podnikání. Více dokončených plateb, rychlá podpora a výhodné ceny.
Key services
Payment gateway, Financing, Payment terminals, Personal accounts
Content quality
excellent
Branding
consistent

Technology

Stack
Google Tag Manager, Google Analytics, CookieConsent.js, Amazon Web Services, Typekit fonts, HTML5 video, JavaScript
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism implemented
  • No exposed sensitive data in HTML
  • Secure forms with POST method

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Google Ads (AW- IDs)
Marketing tools
CookieConsent.js
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with rich content and multimedia
  2. Strong branding and consistent design
  3. Comprehensive cookie consent and privacy mechanisms implemented
  4. Multiple customer testimonials and case studies enhance trust
  5. No explicit security policy or incident response info publicly available
  6. WHOIS data missing or unavailable, which is unusual for a payment service domain
  7. Use of modern web technologies and AWS hosting
  8. Good SEO and accessibility practices observed
Technical notes

Notes

The website uses a modern technology stack including AWS hosting, Google Tag Manager, and Typekit fonts, ensuring good performance and scalability. The site is mobile-optimized with responsive design and uses HTML5 video for rich media content. SEO is supported by proper meta tags, Open Graph, and JSON-LD structured data. Cookie consent is managed via a popular JavaScript library with multi-language support. No CMS was explicitly detected, suggesting a custom or proprietary platform. The site loads quickly and provides a smooth user experience. Technical risks are minimal, but the absence of explicit security headers and WHOIS transparency could be addressed to reduce potential attack vectors and improve trust.
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. 79/100Low26 findingsView report
Reviews of this site

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

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.