context safety score
A score of 33/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
The page serves content under the domain rezka-ua.tv but loads a favicon from static.hdrezka.ac and uses the HDRezka branding (logo, color scheme, footer links). The domain rezka-ua.tv is distinct from the legitimate hdrezka.ac, indicating this is an impersonation or unofficial clone of the HDRezka streaming service. (location: page.html:9 — favicon href points to static.hdrezka.ac; domain is rezka-ua.tv)
social engineering
The access-blocked error page (error 105) pressures users into emailing support@hdrezka.org with their VPN name, public IP address, and device information. This is a classic social engineering pretext — using a fake block notice to harvest sensitive user environment details under the guise of resolving an access issue. (location: page.html:31-41 — email solicitation requiring VPN details, public IP, and device info)
credential harvesting
The page contains a prominent 'Войти на сайт' (Log in to site) link redirecting to https://rhs.to/, an external third-party domain entirely different from rezka-ua.tv or hdrezka.ac. Users believing they are on the legitimate HDRezka site may submit credentials to this external site. (location: page.html:28 — <a href="https://rhs.to/">Войти на сайт</a>)
malicious redirect
The login call-to-action redirects to https://rhs.to/, a domain unrelated to the page's apparent brand identity. This redirect on a brand-impersonating page is a strong indicator of credential harvesting or malicious redirection to a third-party phishing endpoint. (location: page.html:28 — signin-holder link to https://rhs.to/)
phishing
The combination of HDRezka brand impersonation, a fabricated access-error pretext, a login redirect to an unrelated domain (rhs.to), and solicitation of user IP/VPN/device data constitutes a phishing operation targeting users of the legitimate HDRezka streaming platform. (location: page.html — overall page structure and content)
curl https://api.brin.sh/domain/rezka-ua.tvCommon questions teams ask before deciding whether to use this domain in agent workflows.
rezka-ua.tv currently scores 33/100 with a suspicious verdict and low confidence. The goal is to protect agents from high-risk context before they act on it. Treat this as a decision signal: higher scores suggest lower observed risk, while lower scores mean you should add review or block this domain.
Use the score as a policy threshold: 80–100 is safe, 50–79 is caution, 20–49 is suspicious, and 0–19 is dangerous. Teams often auto-allow safe, require human review for caution/suspicious, and block dangerous.
brin evaluates four dimensions: identity (source trust), behavior (runtime patterns), content (malicious instructions), and graph (relationship risk). Analysis runs in tiers: static signals, deterministic pattern checks, then AI semantic analysis when needed.
Identity checks source trust, behavior checks unusual runtime patterns, content checks for malicious instructions, and graph checks risky relationships to other entities. Looking at sub-scores helps you understand why an entity passed or failed.
brin performs risk assessments on external context before it reaches an AI agent. It scores that context for threats like prompt injection, hijacking, credential harvesting, and supply chain attacks, so teams can decide whether to block, review, or proceed safely.
No. A safe verdict means no significant risk signals were detected in this scan. It is not a formal guarantee; assessments are automated and point-in-time, so combine scores with your own controls and periodic re-checks.
Re-check before high-impact actions such as installs, upgrades, connecting MCP servers, executing remote code, or granting secrets. Use the API in CI or runtime gates so decisions are based on the latest scan.
Learn more in threat detection docs, how scoring works, and the API overview.
Assessments are automated and may contain errors. Findings are risk indicators, not confirmed threats. This is a point-in-time assessment; security posture can change.
integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.