context safety score
A score of 30/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
Highly obfuscated JavaScript inline script using character-shuffling string reconstruction, split/reduce array manipulation, and dynamic property access to hide its true behavior. The code reconstructs function names and API calls at runtime to evade static analysis, indicative of fingerprinting, anti-debugging, or malicious payload delivery logic. (location: page.html:40 (inline <script data-cfasync="false" type="text/javascript" data-verify="1">))
hidden content
A hidden iframe pointing to 'https://sysmeasuring.net' is embedded at the bottom of the page body with 'display:none' styling. This loads a third-party domain invisibly, enabling drive-by tracking, fingerprinting, or silent redirection without user awareness. (location: page.html:186 (<iframe style="display: none" src="https://sysmeasuring.net">))
malicious redirect
The hidden iframe to 'sysmeasuring.net' silently loads an external domain in a non-visible context. This pattern is commonly used for silent redirect chains, ad fraud, or traffic hijacking without the user's knowledge or consent. (location: page.html:186 (<iframe style="display: none" src="https://sysmeasuring.net">))
hidden content
An <h1> element containing the site title is wrapped in a <div style="display: none">, hiding it from users while keeping it visible to crawlers and AI agents. This is a classic SEO cloaking and content deception technique. (location: page.html:45-50 (<div style="display: none"><h1>Watch Movies Online Free | Watch Series HD Free</h1>))
social engineering
The site claims 'NO ADS', 'No Account Required', and 'Safe site' in both meta description and page body to build false trust and lower user defenses, a common deception pattern used by piracy and malware-distribution sites to encourage engagement and repeat visits. (location: page.html:11-12 (meta description/keywords), page.html:112-122 (body text))
brand impersonation
The site presents itself as 'HDToday' (hdtodayz.to) which closely mimics the well-known piracy streaming brand 'HDToday.tv'. The domain uses a typosquat-style variation (.to TLD, 'z' suffix) to impersonate or piggyback on the established brand's reputation while operating independently. (location: page.html:55,92 (logo/site name references to 'HDToday'), metadata.json (domain: hdtodayz.to))
curl https://api.brin.sh/domain/hdtodayz.toCommon questions teams ask before deciding whether to use this domain in agent workflows.
hdtodayz.to currently scores 30/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.