Skip to main content

Security report for payhowyudrive.pl

YU! - Pay How YU Drive · Transportation · Poland

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

Security score

63/100

Risk levelMedium

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

YU! - Pay How YU Drive is a Polish insurance service offering usage-based car insurance that adjusts premiums based on the user's driving style, monitored via the Yanosik mobile application. The website presents a clear business model targeting safe drivers who use mobile devices, emphasizing personalized insurance offers and rewarding good driving behavior. The site is professionally designed with consistent branding and partner endorsements from ERGO Hestia and Yanosik, positioning it as an innovative player in the transportation and insurance sectors. Technically, the website uses modern frontend frameworks like Bootstrap and jQuery, integrates Google Tag Manager and Facebook Pixel for analytics and marketing, and employs a comprehensive cookie consent mechanism compliant with GDPR. Security posture is good with HTTPS enforced and no exposed sensitive data, though some security headers are missing and no explicit security policy or incident response information is provided. Overall, the site is accessible, trustworthy, and well-structured, with room for improvement in security best practices and direct contact information availability.

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

7 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

  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 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 payhowyudrive.pl

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. 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
72
Security headers
15
Email security
70
DNS health
80
Network security
100
GDPR outside view
40
Average
63

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

The business operates in the niche of telematics-based insurance, leveraging mobile app data to tailor insurance pricing. Its competitive advantage lies in personalized pricing based on driving behavior rather than traditional factors like car type or registration location. The partnership ecosystem includes major players like ERGO Hestia and Yanosik, enhancing credibility and market reach. The business model focuses on mobile-first delivery, targeting tech-savvy drivers in Poland. Growth indicators include integration with a large user base of Yanosik app users and a clear value proposition promoting safer driving. The company appears medium-sized with a founding date consistent with domain registration. Strategic observations suggest potential for expansion into broader telematics insurance markets and enhanced digital engagement.

Security posture

The website demonstrates a moderate to good security maturity level with HTTPS enforced and a detailed cookie consent mechanism supporting GDPR compliance. No critical vulnerabilities or exposed sensitive data were detected in the HTML content. However, the absence of key security headers such as Content-Security-Policy and X-Frame-Options reduces defense-in-depth. There is no published security policy or incident response contact, which limits transparency and readiness for security incidents. The use of third-party scripts like Google Analytics and Facebook Pixel is managed with user consent, but continuous monitoring for vulnerabilities in these libraries is recommended. Overall, the security posture is adequate for the business type but could be improved with enhanced headers, explicit policies, and vulnerability disclosure mechanisms.

Recommendations

  1. Implement security headers including Content-Security-Policy, X-Frame-Options, and X-XSS-Protection to strengthen browser security.
  2. Publish a dedicated security policy page and provide incident response contact information to improve transparency and readiness.
  3. Introduce a security.txt file to facilitate responsible vulnerability disclosure.
  4. Enhance accessibility features to meet WCAG standards for broader user inclusivity.
  5. Regularly audit and update third-party scripts and libraries to mitigate potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
YU! - Pay How YU Drive
Description
YU! offers a mobile-based insurance product that adjusts pricing based on the user's driving style, leveraging the Yanosik app to monitor driving behavior. The service targets safe drivers and rewards them with personalized insurance offers.
Key services
Usage-based car insurance, Driving style monitoring, Personalized insurance offers
Content quality
good
Branding
consistent

Technology

Stack
Bootstrap 4.3.1, jQuery 3.4.1, Google Tag Manager, CookieYes consent management, Facebook Pixel
Frameworks
Bootstrap
Platforms
Web, Mobile (targeted via app integration)
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • Cookie consent with granular controls
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Facebook Ads
Tracking pixels
Facebook Pixel
Marketing tools
CookieYes
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Comprehensive cookie consent mechanism with detailed categories and user controls.
  3. No explicit terms of service page found.
  4. Contact information only via contact form; no direct emails or phone numbers publicly listed.
  5. Use of modern frontend technologies and third-party analytics and marketing tools.
  6. Strong branding with partner logos and consistent design.
  7. No security.txt or explicit security policy found.
  8. No exposed sensitive data or obvious vulnerabilities detected in HTML content.
Technical notes

Notes

The website uses a modern and widely adopted frontend stack including Bootstrap 4.3.1 and jQuery 3.4.1, ensuring responsive design and good mobile optimization. Google Tag Manager and Facebook Pixel are integrated for analytics and marketing purposes, with a comprehensive cookie consent mechanism powered by CookieYes. Hosting is provided by OVH SAS, a reputable provider. Performance is moderate with no major issues detected, though some optimization opportunities exist. The site lacks a CMS, indicating a custom or static site approach. SEO and accessibility are basic but functional. Technical risks include missing security headers and reliance on multiple third-party scripts which require ongoing security management.
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 payhowyudrive.pl. 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 payhowyudrive.pl.

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.