Scanned on 23 September 2026 at 00:47 UTC
As of , xn--b1aecn0aafbh.xn--p1ai has a GDPR compliance score of 0/100 with 24 pre-consent tracking violations detected.
Only Privacy Score 100 means full compliance. These violations mean that before you could even click the Cookie Consent banner, this website already collected your personal data and shared it with third parties. Learn why this matters (our blog) →
Who is responsible? The website owner is solely responsible for these violations and in general often benefits monetarily (directly or indirectly) from collecting and sharing your data without your consent.
No consent platform recognised
The site may use a custom or unrecognised banner. This is informational and does not affect the score.
Records mouse movements, keystrokes, and clicks to capture your exact behaviour on the page.
Tracking cookies are used to identify and follow users across websites. Under GDPR, these require explicit consent before being set, but on this website they are active immediately.
Low-severity concerns: external fonts, empty tag containers, WebSocket connections, and third-party storage.
Services and cookies that comply with GDPR requirements. No consent needed.
Most findings on this page are configuration problems, not catastrophes. These plain-language guides explain what each one means and how to fix it, written for website owners rather than lawyers.
All guides live at gdprscanner.eu/guides.
xn--b1aecn0aafbh.xn--p1ai has a GDPR compliance score of 0/100.
A score below 50 indicates serious GDPR compliance failures. Multiple high-severity trackers or advertising scripts load before consent, exposing the website to potential fines of up to €20 million or 4% of annual global turnover under GDPR Article 83.
20 trackers detected loading before user consent:
Legal basis: This violates GDPR Article 6(1)(a), Article 9 (where sensitive data is captured), and EDPB Guidelines 2/2019. Session recording captures detailed user interactions including keystrokes, mouse movements, and form inputs. The EDPB has clarified that such invasive processing cannot rely on legitimate interest and requires explicit, informed consent. If health or financial data is inadvertently captured, Article 9 special category protections apply.
Legal basis: This violates ePrivacy Directive Article 5(3) and GDPR Article 6(1)(a). WebSocket connections to third-party servers transmit visitor data (including IP addresses) in real time without explicit consent. Persistent WebSocket connections are particularly invasive as they maintain continuous data channels to external servers.
This GDPR compliance scan of xn--b1aecn0aafbh.xn--p1ai was performed by GDPR Scanner, a pre-consent privacy scanning tool. The scan captures all trackers, cookies, and third-party scripts that load before a user clicks any consent button.
Under GDPR (General Data Protection Regulation), websites must obtain explicit consent before processing personal data. Any tracker or cookie that fires before consent is a potential violation of EU privacy law.
A privacy score of 100/100 means the website loads zero trackers and zero tracking cookies before the user gives consent. This is the standard required by GDPR Article 5(1)(a) and Article 7.
Essential cookies (session management, security tokens) and first-party functional cookies do not incur penalties, as they are covered by the legitimate interest legal basis. See an example: playhth.com scores 100/100.
Legal basis: This violates GDPR Article 6(1)(a), Article 9 (where sensitive data is captured), and EDPB Guidelines 2/2019. Session recording captures detailed user interactions including keystrokes, mouse movements, and form inputs. The EDPB has clarified that such invasive processing cannot rely on legitimate interest and requires explicit, informed consent. If health or financial data is inadvertently captured, Article 9 special category protections apply.
| Cookie Name | Domain | Type | Service | Duration |
|---|---|---|---|---|
| _ym_visorc | .xn--b1aecn0aafbh.xn--p1ai | 1st party | Yandex Metrica - Yandex Metrica webvisor session recording | Session |
| _ym_uid | .xn--b1aecn0aafbh.xn--p1ai | 1st party | Yandex.Metrica - Used for identifying site users | Session |
| _ym_d | .xn--b1aecn0aafbh.xn--p1ai | 1st party | Yandex.Metrica - Saves the date of the user's first site session | Session |
| _ym_isad | .xn--b1aecn0aafbh.xn--p1ai | 1st party | Yandex.Metrica - Determines whether a user has ad blockers | Session |
xn--b1aecn0aafbh.xn--p1ai has serious GDPR compliance deficiencies with a score of 0/100 and 24 violations detected. Multiple trackers and cookies are loading before user consent, which constitutes a clear breach of the ePrivacy Directive Article 5(3).
This level of non-compliance exposes the website operator to significant regulatory risk. Under GDPR Article 83(5), infringements of the basic principles for processing — including conditions for consent — are subject to administrative fines of up to €20 million or 4% of annual global turnover. Recent enforcement trends show increasing DPA activity across the EU.
Immediate action is recommended: audit all third-party scripts, implement a Consent Management Platform (CMP) that blocks non-essential trackers before consent, and verify compliance through re-scanning.
xn--b1aecn0aafbh.xn--p1ai scores 0/100 with 24 violation(s) detected. Trackers or cookies were found loading before user consent.
Our scan detected 20 tracker(s) loading before consent, including Yandex Metrica, Yandex Metrica (WebSocket), Yandex Metrica (storage).
Yes, 5 cookie(s) were detected before the user interacted with any consent banner.
xn--b1aecn0aafbh.xn--p1ai has a GDPR compliance score of 0/100 as of 23 September 2026. A score of 100 means no trackers or cookies load before consent. xn--b1aecn0aafbh.xn--p1ai currently has 24 violation(s) affecting its score.
xn--b1aecn0aafbh.xn--p1ai should implement a Consent Management Platform (CMP) that blocks all non-essential trackers and cookies until the visitor gives explicit consent. This includes configuring tag managers like Google Tag Manager to use consent-aware triggers, self-hosting external fonts, and auditing all third-party scripts. After making changes, re-scan with GDPR Scanner to verify compliance.