Skip to main content

Security report for webeye.eu

W.A.G. payment solutions, a.s. · Transportation · Czech Republic

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

Security score

69/100

Risk levelMedium

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

W.A.G. payment solutions, a.s., operating under the brand Eurowag, is a leading provider of integrated mobility and payment solutions tailored for the European transportation sector. The company offers a comprehensive suite of services including fleet management, toll payment solutions, fuel cards, tax refunds, and financial services, targeting commercial fleet operators and logistics companies. Their market position is strong, supported by a large-scale operation and a broad geographic presence across multiple European countries. Technically, the website is built on modern web technologies including Webflow CMS, jQuery, and Google Tag Manager, hosted on a performant CDN infrastructure. The site is well-optimized for mobile devices, accessibility, and SEO, reflecting a mature digital presence. The integration of multiple login portals and partner platforms indicates a complex and well-managed technical ecosystem. From a security perspective, the website enforces HTTPS and implements cookie consent mechanisms, demonstrating compliance with privacy regulations such as GDPR. However, explicit security headers are not visibly configured, and there is no public incident response or vulnerability disclosure policy, which are areas for improvement. No critical vulnerabilities or exposed sensitive data were detected. Overall, the website presents a professional and trustworthy front for a large enterprise in the transportation and payment services industry. The lack of WHOIS data reduces transparency but does not detract significantly from the site's legitimacy. Strategic recommendations include enhancing security headers, publishing incident response contacts, and formalizing vulnerability disclosure policies to strengthen trust and compliance.

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

      GDPR requires explicit consent for non-essential cookies

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

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics, Facebook, LinkedIn, YouTube

      What to do: Document all third-party data sharing in your privacy policy

  3. 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 webeye.eu

This scan found 22 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
47
Security headers
45
Email security
85
DNS health
85
Network security
100
GDPR outside view
50
Average
69

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 webeye.eu, from OffSeq Breach.

Total records
2,921
Employees
0
Customers
2,920
Third parties
1
Weak passwords
48%

47 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 webeye.eu.

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

Eurowag operates in a competitive European market providing integrated payment and fleet management solutions. Their business model leverages technology to streamline transport operations, reduce costs, and improve compliance for fleet operators. Revenue streams likely include service subscriptions, transaction fees, and value-added services such as tax refunds and insurance. The company targets transport companies, fleet managers, and logistics providers, emphasizing efficiency and regulatory compliance. Partnerships with platforms like OCRK, GBox, and FireTMS expand their ecosystem and service offerings. The presence of investor relations and sustainability pages indicates a publicly accountable and growth-oriented organization.

Security posture

The website demonstrates a moderate to high security maturity level with HTTPS enforced and cookie consent implemented, aligning with GDPR requirements. The absence of explicit security headers such as Content-Security-Policy and X-Frame-Options is a gap that could expose the site to certain web-based attacks. No incident response or vulnerability disclosure information is publicly available, which limits transparency and readiness perception. No signs of exposed credentials, malware, or phishing were found. The site uses third-party analytics and marketing tools responsibly with user consent. Overall, the security posture is solid but could be enhanced by adopting additional best practices and transparency measures.

Recommendations

  1. Implement and configure security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web vulnerabilities.
  2. Publish an incident response contact or security.txt file to improve transparency and facilitate vulnerability reporting.
  3. Develop and communicate a formal vulnerability disclosure policy to encourage responsible security research and reporting.
  4. Regularly audit third-party scripts and dependencies to ensure no vulnerable libraries are in use.
  5. Enhance user trust by providing more detailed privacy and data protection information, including data retention policies.

Contact details published on the site

Addresses
Legal name
W.A.G. payment solutions, a.s.
Registration number
26415623
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
W.A.G. payment solutions, a.s.
Description
Eurowag combines telematics and tolling to optimize fleet operations with tracking, automation, and real-time insights across Europe. It offers advanced fleet management, toll solutions, payment services, and financial services to commercial road transportation businesses.
Key services
Fleet management, Toll services, Payment services, Tax refund, Financial services, eMobility, Partner services
Content quality
excellent
Branding
consistent

Technology

Stack
jQuery 3.5.1, intl-tel-input, Google Tag Manager, Webflow CMS, Custom JavaScript
Platforms
Webflow
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism implemented
  • No exposed sensitive data in HTML
  • Secure external links with rel='noopener' or target='_blank'

Analytics and tracking

Services
Google Analytics (via GTM)
Tracking level
moderate
Privacy practices
good

Advertising

Transparency
good

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is fully accessible with rich content and no blocking detected
  2. Strong focus on fleet management and payment solutions for European transport sector
  3. Comprehensive cookie and privacy policies with consent mechanisms implemented
  4. Multiple login portals for different services indicating a mature service ecosystem
  5. Use of modern web technologies and CDN for performance
  6. No visible security vulnerabilities or exposed sensitive data
  7. WHOIS data unavailable, which reduces transparency but does not negate legitimacy
Technical notes

Notes

The website is built on Webflow CMS with custom JavaScript and jQuery 3.5.1, leveraging intl-tel-input for phone input formatting. Google Tag Manager is used for analytics and marketing tracking. Hosting is via AWS Cloudfront CDN, ensuring fast content delivery. The site is mobile-optimized with responsive design and accessibility features such as keyboard navigation and ARIA attributes. SEO is supported by comprehensive meta tags and Open Graph data. No major technical debt or performance bottlenecks were detected. Opportunities exist to improve security headers and formalize security policies.
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 webeye.eu. 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 webeye.eu.

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.