Skip to main content

Security report for payu.cz

Other · N/a

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

Security score

72/100

Risk levelMedium

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

The website at czech.payu.com is currently inaccessible due to a 403 error served by AWS CloudFront, indicating either a Web Application Firewall (WAF) block or a configuration issue. This prevents retrieval of any meaningful content, metadata, or business information. The domain appears to be a subdomain of payu.com, a known payment service provider, but no WHOIS data is available for this subdomain, limiting verification of ownership or legitimacy. The lack of accessible content and metadata means no privacy, cookie, or security policies can be evaluated, and no contact or incident response information is present. From a technical perspective, the site is hosted behind Amazon CloudFront, which is a reputable CDN and security provider, but the current configuration blocks access, resulting in a poor user experience and zero content availability. No scripts, forms, or external links are detectable in the provided HTML. Security posture cannot be assessed beyond the presence of CloudFront, and no SSL or security headers data is available. Overall, the risk assessment is high due to the inability to verify the site’s content, policies, or security measures. The site’s legitimacy is uncertain, and the lack of WHOIS data for the subdomain further complicates trust evaluation. Strategic recommendations include resolving the CloudFront access issues, publishing clear business and security information, and ensuring compliance with privacy regulations to improve trust and transparency.

Scanned

NIS2 and GDPR posture

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

6 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 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';…

  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

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

Keep watching payu.cz

This scan found 19 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
82
Security headers
30
Email security
83
DNS health
85
Network security
100
GDPR outside view
50
Average
72

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

Due to the blocked content and lack of accessible data, detailed business intelligence cannot be derived. The domain is a subdomain of payu.com, which is a payment service provider operating globally. The czech.payu.com subdomain likely targets the Czech market for payment processing services. However, no direct information about market positioning, revenue streams, or partnerships is available from the provided data. The absence of contact or policy information limits insights into customer engagement or compliance maturity.

Security posture

The security posture cannot be fully assessed due to the blocked content. The presence of AWS CloudFront suggests use of a robust CDN and potential WAF protection, but the 403 error indicates either a misconfiguration or active blocking of requests. No security headers or SSL configuration details are available. No evidence of vulnerabilities or exposed sensitive data is found, but this is due to lack of accessible content rather than confirmed security. Incident response and vulnerability disclosure information are absent, indicating low transparency.

Recommendations

  1. Resolve AWS CloudFront configuration to allow legitimate user access and avoid 403 errors.
  2. Publish comprehensive privacy, cookie, and terms of service policies accessible to users.
  3. Provide clear contact information including support and incident response channels.
  4. Implement and verify security headers and HTTPS configuration to enhance security posture.
  5. Regularly audit WHOIS and domain registration data to ensure consistency and transparency.
Site observations

Automated reading of the public site. Ratings are indicative.

CloudFront detected. Request blocked by AWS CloudFront with 403 ERROR indicating possible WAF or configuration issue. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website content is inaccessible due to CloudFront 403 error.
  2. No metadata, forms, scripts, or external links found in the HTML content.
  3. No contact or policy information available on the page.
  4. WHOIS data for the domain is unavailable or not separately registered.
  5. Site likely protected by AWS CloudFront WAF or misconfigured, blocking access.
  6. No evidence of adult or unsafe content.
  7. Analysis limited by lack of accessible content.
Technical notes

Notes

The website is hosted behind Amazon CloudFront CDN, which provides performance and security benefits. However, the current configuration results in a 403 error blocking access to all content. No metadata, scripts, or forms are present in the HTML, indicating either a placeholder or error page. No CMS or frameworks can be detected. The lack of accessible content prevents evaluation of performance, mobile optimization, accessibility, or SEO. Technical debt or modernization opportunities cannot be assessed without further access.
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. 73/100Medium28 findingsView report
Reviews of this site

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