Skip to main content

Security report for pays.cz

pays.cz s.r.o. · Finance · Czech Republic

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

Security score

67/100

Risk levelMedium

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

Pays.cz s.r.o. operates a payment gateway platform primarily serving merchants and buyers in the Czech Republic. Founded in 2011, the company offers a variety of payment methods including card payments, QR payments, bank transfers, and PayPal, positioning itself as a reliable and flexible payment solution with no monthly fees and transparent pricing. The website reflects a professional and consistent brand image with clear navigation and relevant content tailored to its target audience of e-commerce merchants and consumers. Technically, the website employs a mature technology stack including jQuery, Bootstrap, and Google reCAPTCHA for security. Hosting appears to be managed by Active24, a known Czech hosting provider. The site is mobile optimized and SEO friendly, though some technologies like jQuery are outdated. Performance is moderate, and accessibility is basic but functional. From a security perspective, the site enforces HTTPS and uses CAPTCHA to protect forms, but lacks explicit security headers and a published security policy. No vulnerabilities or exposed sensitive data were detected. Privacy compliance is partial, with cookie and privacy policies present but no explicit consent mechanism. WHOIS data is consistent and supports the legitimacy of the domain and business. Overall, Pays.cz demonstrates a solid business and technical foundation with room for improvement in security best practices and privacy compliance. The risk profile is low, but enhancing security headers and formalizing incident response and data protection policies would strengthen trust and resilience.

Scanned

NIS2 and GDPR posture

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

6 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

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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 Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  2. 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 pays.cz

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
77
Security headers
30
Email security
85
DNS health
70
Network security
100
GDPR outside view
40
Average
67

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

Total records
112
Employees
0
Customers
112
Third parties
0
Weak passwords
4%

2 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 pays.cz.

Select it in the checkout above.

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

Technical appendix

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

Business context

Business profile

Pays.cz holds a competitive position in the Czech payment gateway market by offering a no-monthly-fee model and multiple payment options, appealing to small and medium-sized merchants. Its business model relies on transaction fees with flexible fee payer options, supporting diverse merchant needs. The company maintains partnerships with local service providers for website realization, indicating a collaborative ecosystem. The clear focus on ease of integration and technical support suggests a customer-centric approach. Growth potential exists through expanding payment methods and improving digital maturity. The company targets e-commerce merchants, ticket sellers, and parking services, indicating a diversified client base within the finance and retail sectors. The website content and structure support lead generation and customer onboarding through registration and demo forms. No direct contact emails or phone numbers are publicly displayed, possibly to reduce spam or funnel inquiries through forms.

Security posture

The security posture of Pays.cz is moderate to strong. HTTPS is enforced site-wide, and Google reCAPTCHA protects key forms against automated abuse. The absence of explicit security headers such as Content Security Policy or HSTS is a notable gap. The use of an older jQuery version could expose the site to known vulnerabilities if not properly patched. No sensitive data leakage or insecure form handling was observed. The lack of a published security policy or incident response contact reduces transparency and preparedness perception. GDPR compliance is partially addressed via privacy and cookie policies, but no explicit consent mechanism is implemented. Recommendations include implementing security headers, updating JavaScript libraries, publishing security and incident response policies, and enhancing cookie consent mechanisms to improve compliance and trust.

Recommendations

  1. Implement HTTP security headers including Content Security Policy, HSTS, X-Frame-Options, and X-XSS-Protection.
  2. Upgrade jQuery and other JavaScript libraries to latest secure versions to mitigate known vulnerabilities.
  3. Publish a dedicated security policy and provide clear incident response contact information.
  4. Introduce a cookie consent banner/mechanism to comply with GDPR and ePrivacy Directive requirements.
  5. Enhance accessibility features and conduct regular security audits to maintain a strong security posture.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
pays.cz s.r.o.
Description
Pays provides a payment gateway service offering multiple payment methods including card payments, QR payments, bank transfers, and PayPal. It targets merchants and buyers with easy integration and no monthly fees.
Key services
Payment gateway, Payment links generation, Mobile payments, Payment pre-invoices, Technical support
Content quality
good
Branding
consistent

Technology

Stack
jQuery 1.11.1, jQuery UI 1.11.3, ResponsiveSlides, Bootstrap, Magnific Popup, Google reCAPTCHA v2, Zendesk Widget
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Google reCAPTCHA on forms
  • No exposed sensitive data in HTML
  • Use of secure form submission endpoints

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
Google reCAPTCHA
Marketing tools
Zendesk Widget
Transparency
basic

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 multiple interactive forms.
  2. No explicit privacy or security policy pages found, but terms and cookie policy are present.
  3. Use of older jQuery version may pose minor security risk.
  4. No direct company contact emails or phone numbers visible in HTML content.
  5. Strong branding and clear business focus on payment gateway services.
  6. No signs of suspicious or malicious content.
Technical notes

Notes

The website uses a combination of legacy and modern web technologies including jQuery 1.11.1, Bootstrap, and Magnific Popup. Google reCAPTCHA v2 is integrated for bot protection. Hosting is managed by Active24, a reputable Czech provider. The site is mobile responsive and SEO optimized with proper meta tags and Open Graph data. Performance is moderate, with room for improvement by updating libraries and optimizing assets. Accessibility is basic but functional. No CMS was detected, suggesting a custom or static site architecture. The technical stack supports the business model effectively but requires modernization to reduce technical debt and security 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. 65/100Medium32 findingsView report
Reviews of this site

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