Skip to main content

Security report for payphone.cz

KB SmartPay · Finance · Czech Republic

Medium risk. 4 critical or high findings in Email security, Security headers and 1 other check.

Security score

61/100

Risk levelMedium

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

KB SmartPay operates the PayPhone service, a mobile payment terminal application that transforms smartphones into card payment terminals, targeting merchants and businesses primarily in the Czech Republic. The website presents a professional and consistent brand image, emphasizing ease of use and a free one-year offer to attract users. The business model centers on providing mobile payment solutions leveraging smartphone technology, positioning itself in the finance sector with a focus on digital payment innovation. Technically, the website is built on WordPress 6.8.1 and integrates multiple modern technologies including Google Analytics, Google Tag Manager, Cookiebot for cookie consent management, and advertising/tracking services such as Adform and Facebook Pixel. The site is mobile-optimized and uses structured data (JSON-LD) to enhance SEO and provide clear business information. Performance is moderate with good mobile responsiveness and basic accessibility features. From a security perspective, the site enforces HTTPS and implements a comprehensive cookie consent mechanism, demonstrating awareness of privacy regulations. However, the absence of visible security headers and lack of explicit privacy policy or incident response information are notable gaps. The WHOIS data is unavailable, which reduces domain trustworthiness and raises questions about domain registration transparency. Overall, the website is functional, professional, and compliant with basic privacy requirements but would benefit from enhanced transparency in privacy policies, improved security headers, and clearer contact information to strengthen trust and compliance posture.

Scanned

NIS2 and GDPR posture

GDPR outside view
88/ 100 · Low
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

4 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • 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';…
  3. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • High

      High-Risk Service Exposed: FTP

      Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer

      What to do: Consider restricting access to FTP or implementing strong authentication

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

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

Keep watching payphone.cz

This scan found 20 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
95
Security headers
30
Email security
60
DNS health
75
Network security
20
GDPR outside view
88
Average
61

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

Total records
6
Employees
0
Customers
6
Third parties
0
Weak passwords
0%

1 subdomain 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 payphone.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

KB SmartPay's PayPhone service targets the growing market for mobile payment solutions in the Czech Republic, leveraging smartphone ubiquity to offer a convenient card payment terminal alternative. The company appears to focus on SMEs and merchants seeking cost-effective payment acceptance. The business model likely includes revenue from transaction fees or subscription services post the free trial period. The presence of multiple advertising and tracking technologies indicates an active marketing strategy to acquire and retain customers. The Facebook page suggests engagement with customers and brand building. The lack of detailed company registration data online may be a strategic choice or an oversight, but the brand presence and app availability on Google Play support legitimacy. Partnerships with major ad networks and analytics providers indicate a mature digital marketing ecosystem.

Security posture

The website demonstrates a baseline security posture with enforced HTTPS and a robust cookie consent mechanism compliant with GDPR principles. The use of Cookiebot ensures user consent management and transparency about cookie usage. However, the absence of explicit security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security reduces defense-in-depth. No security.txt or vulnerability disclosure policy is present, limiting transparency for security researchers. The WHOIS data absence is a concern for domain legitimacy verification. No exposed sensitive data or vulnerable libraries were detected in the HTML content. Overall, the security posture is moderate but could be improved with additional headers, documented policies, and enhanced domain transparency.

Recommendations

  1. Implement and publish a comprehensive privacy policy page linked prominently on the website.
  2. Add security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to enhance protection.
  3. Publish a security.txt file to facilitate vulnerability disclosure and improve security transparency.
  4. Provide clear and verified company contact information including emails and phone numbers for customer and security incident reporting.
  5. Investigate and resolve the missing WHOIS data issue to improve domain trustworthiness and legitimacy.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
KB SmartPay
Description
S platební aplikací „Payphone“ proměňte svůj smartphone v platební terminal v mobilu a začněte přijímat platby kartou.
Key services
Mobile payment terminal app, Card payment acceptance via smartphone
Content quality
good
Branding
consistent

Technology

Stack
WordPress 6.8.1, Google Analytics, Google Tag Manager, Cookiebot, Adform tracking, Tobii lightbox library
Frameworks
WordPress
Platforms
Android (app)
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism implemented
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics, Facebook Pixel, Adform
Tracking level
extensive
Privacy practices
basic

Advertising

Ad networks
Adform, Google DoubleClick, Facebook Ads
Tracking pixels
Facebook Pixel, Adform tracking
Marketing tools
Cookiebot
Transparency
good

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website is fully accessible with no blocking or WAF challenge.
  2. WHOIS data is unavailable, which is unusual and reduces domain trust.
  3. Cookie consent is implemented with detailed cookie categorization.
  4. No explicit privacy policy or terms of service pages found in the HTML content.
  5. Multiple external tracking and advertising services are used.
  6. No direct contact emails or phone numbers found in the visible content.
  7. Business identity is clear from structured data and branding as KB SmartPay.
  8. Website uses WordPress CMS with modern scripts and libraries.
  9. Mobile app presence indicated via Google Play Store link.
  10. Security headers are not explicitly visible in the HTML content.
Technical notes

Notes

The website is built on a modern WordPress CMS platform version 6.8.1, utilizing popular JavaScript libraries and services such as Google Analytics, Google Tag Manager, Cookiebot, and Adform for tracking and marketing. The site uses JSON-LD structured data to enhance SEO and provide machine-readable business information. The presence of multiple asynchronous scripts and CDN-hosted libraries indicates a modern approach to performance optimization. Mobile optimization is good, with responsive design and viewport meta tags. Accessibility is basic but present. The site lacks visible advanced security headers and detailed technical documentation. Hosting provider details are not explicitly found in the HTML content. Overall, the technical infrastructure is solid but could benefit from enhanced security configurations and more transparent hosting information.
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

Reviews of this site

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