Skip to main content

Security report for zalapay.com

Finance · Latvia

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

Security score

55/100

Risk levelMedium

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

Zalapay is a Latvian-based company providing virtual payment terminal and digital cash register solutions, enabling merchants to accept payments via Android phones without changing banks. The website is built on WordPress and integrates modern tracking tools such as Google Analytics and Facebook Pixel. The technical infrastructure is moderate in performance with good mobile optimization and basic accessibility features. Security posture is adequate with HTTPS enforced and domain protection flags set, but lacks advanced security headers and DNSSEC. Privacy compliance is limited due to absence of a visible privacy policy and terms of service, though cookie consent is implemented. Overall, the website presents a professional image with consistent branding and relevant content for its target audience.

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

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

This scan found 25 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
62
Security headers
15
Email security
85
DNS health
65
Network security
40
GDPR outside view
65
Average
55

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

Zalapay operates in the finance sector focusing on payment processing and digital POS solutions. The business model revolves around providing virtual payment terminals and digital cash registers to small and medium-sized businesses. The company appears to be relatively new, founded in 2022, with a niche market position in Latvia. The website targets merchants seeking modern payment acceptance methods. Integration with Google and Facebook marketing tools suggests active digital marketing efforts. No explicit partnerships or subsidiaries were identified from the website content.

Security posture

The website enforces HTTPS and uses domain status protections to prevent unauthorized changes. However, it lacks several important security headers such as Content-Security-Policy and X-Frame-Options, which could mitigate common web attacks. DNSSEC is not enabled, representing a minor risk in DNS spoofing. No published security policy or incident response contacts were found, limiting transparency in security management. The presence of cookie consent indicates some compliance with privacy regulations, but absence of privacy and terms policies is a compliance gap. Overall, security maturity is moderate but could be improved with additional controls and documentation.

Recommendations

  1. Publish a comprehensive privacy policy and terms of service pages to improve compliance and user trust.
  2. Implement key security headers including Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy.
  3. Enable DNSSEC for the domain to enhance DNS security.
  4. Add a security policy and incident response contact information to improve transparency and readiness.
  5. Regularly audit third-party scripts and tracking tools to minimize privacy risks and ensure compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Zalapay offers virtual payment terminal solutions including digital cash registers and payment acceptance via Android phones without changing banks.
Key services
Virtual payment terminal, Digital cash register, Android phone payment acceptance
Content quality
good
Branding
consistent

Technology

Stack
WordPress 6.8.1, PHP, jQuery 3.7.1, Google Tag Manager, Facebook Pixel, WP Rocket, TranslatePress Multilingual, Ninja Forms, EWWW Image Optimizer
Frameworks
WordPress
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
65/100
Good practices seen
  • HTTPS enforced
  • Use of clientDeleteProhibited and other domain status flags
  • Cookie consent implemented

Analytics and tracking

Services
Google Analytics, Google Tag Manager, Facebook Pixel
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Facebook Pixel, Google Analytics (via MonsterInsights plugin)
Marketing tools
MonsterInsights
Transparency
basic

Site quality

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

Key observations

  1. Website is a WordPress-based site offering virtual payment terminal and digital POS solutions.
  2. Content is primarily in Latvian with English language option available.
  3. No explicit privacy policy or terms of service pages found.
  4. Cookie consent is implemented via CookieYes script.
  5. No contact emails or phone numbers explicitly found in the HTML content.
  6. Google Analytics and Facebook Pixel are integrated for tracking.
  7. No security.txt or vulnerability disclosure information found.
  8. Domain is registered with GoDaddy and is relatively new but consistent with business claims.
Technical notes

Notes

The website uses WordPress CMS with a modern theme and plugins including WP Rocket for performance optimization, TranslatePress for multilingual support, and Ninja Forms for form handling. JavaScript libraries such as jQuery are used. The site loads fonts from Google Fonts and images optimized with EWWW Image Optimizer. Google Tag Manager and Facebook Pixel are integrated for analytics and marketing. Hosting is via GoDaddy as per WHOIS data. Performance is moderate with lazy loading and caching techniques applied. Mobile optimization is good, but accessibility features are basic. SEO is supported with proper meta tags and structured data. Technical debt appears low but security enhancements are recommended.
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 zalapay.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 zalapay.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.