Skip to main content

Security report for gopay.com

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 robust payment gateway and personal account service primarily targeting merchants and businesses in the finance and e-commerce sectors. The company boasts over 18,000 merchants and a decade of experience processing more than 100 million payments, positioning itself as a trusted payment solution provider in the Czech Republic. Their offerings include a wide range of payment methods such as credit/debit cards, Apple Pay, Google Pay, recurring payments, refunds, and pre-authorized payments, supported by dedicated customer support and fast integration capabilities. Technically, the website demonstrates a modern infrastructure leveraging Amazon Web Services hosting, JavaScript frameworks, Google Tag Manager for analytics, and a comprehensive cookie consent mechanism. The site is mobile optimized with good SEO practices and multimedia content enhancing user engagement. However, accessibility features are basic and could be improved. From a security perspective, the site enforces HTTPS and PCI DSS certification, indicating adherence to industry standards for payment security. Cookie consent and privacy policies are well implemented, reflecting GDPR compliance. Nonetheless, the absence of explicit security headers and a vulnerability disclosure program suggests room for improvement in security posture. The lack of WHOIS data for the domain is a notable anomaly that impacts trust and credibility. Overall, GoPay presents a professional and trustworthy online presence with strong business and technical foundations. The primary risk lies in the missing WHOIS registration data, which should be investigated further to confirm domain legitimacy. Strategic enhancements in security policies, accessibility, and transparency would further strengthen their market position and customer trust.

Scanned

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

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

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

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

GoPay holds a strong market position as a payment gateway provider with a decade-long operational history and a large merchant base. Their competitive advantage lies in offering a comprehensive suite of payment options and seamless integration, appealing to diverse merchants across Europe. The business model focuses on transaction-based revenue streams supported by value-added services like recurring payments and refunds. The partnership ecosystem includes well-known brands and platforms, enhancing credibility and reach. Growth indicators include a high volume of processed payments and continuous feature expansion. Strategic observations highlight the importance of maintaining compliance, enhancing security transparency, and expanding internationalization to sustain competitive advantage.

Security posture

The security maturity level of GoPay is moderate to high, evidenced by HTTPS enforcement, PCI DSS certification, and GDPR-compliant privacy and cookie policies. The site avoids exposing sensitive data and uses secure forms. However, the absence of explicit security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options reduces defense-in-depth. No public incident response or vulnerability disclosure mechanisms were found, which could delay response to emerging threats. Data protection practices appear sound, but formal documentation and contact channels for security incidents are lacking. Overall, the security culture is professional but could benefit from enhanced transparency and proactive vulnerability management.

Recommendations

  1. Implement and publish comprehensive security headers including CSP, HSTS, and X-Frame-Options to strengthen browser security.
  2. Establish and publicize a vulnerability disclosure program and security.txt file to facilitate responsible reporting and improve incident response.
  3. Enhance accessibility compliance to meet WCAG standards, improving usability for all users.
  4. Investigate and resolve the missing WHOIS registration data to improve domain legitimacy and trustworthiness.
  5. Increase transparency by publishing a dedicated security policy and incident response contact information.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
GoPay s.r.o.
Description
GoPay provides a powerful payments solution with access to over 80 features including Apple Pay, Google Pay, and multiple payment methods. It supports merchants with fast integration, dedicated support, and a high success rate of payments.
Key services
Payment gateway, Personal account, Multiple payment methods including cards, Apple Pay, Google Pay, Recurring payments, Refunds, Pre-authorized payments
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, Google Tag Manager, Video HTML5, Lazy loading images, Cookie Consent scripts
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism implemented
  • No exposed sensitive data in HTML
  • Use of PCI DSS certification

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Transparency
good

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
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. No phone numbers or physical addresses explicitly listed on main page
  5. Contact email is provided in footer
  6. No explicit security.txt or vulnerability disclosure found
  7. WHOIS data missing, which is a significant anomaly
  8. Use of modern web technologies and CDN hosting
  9. Good SEO and social media integration
Technical notes

Notes

The website is built on a modern JavaScript-based front end with lazy loading for images and videos, improving performance and user experience. Hosting on Amazon Web Services provides scalability and reliability. Google Tag Manager is used for analytics and marketing tracking, integrated with a cookie consent management system ensuring privacy compliance. The site is mobile optimized with responsive design and clear navigation. However, no CMS or backend platform was explicitly detected, suggesting a custom or proprietary solution. Performance is moderate with room for optimization, especially in accessibility and security header implementation. Technical debt appears low, but improvements in security and accessibility standards are recommended to mitigate 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. 79/100Low26 findingsView report
Reviews of this site

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