context safety score
A score of 41/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
cloaking
Page conditionally redirects based on referrer or user-agent
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
The main ad-serving script is explicitly named '7.10.13.obfuscated.js' (referenced in UuR2wyuON variable) and loaded as '/afon/evgeno7.10.13.6077c10420228d95a294e0a24aa69a12.js'. The inline popunder/ad manager initialization code also contains minified/obfuscated logic designed to evade analysis. (location: page.html:101-103, page.html:105-107)
malicious redirect
Aggressive popunder/tabunder ad system configured to fire on user clicks across virtually all page elements (bind_to: '*' in isMz mode). Uses ExoClick zone 994366 and multiple SSP endpoints to redirect users to third-party destinations without clear consent. The 'subInterstitialSettings.directLink' points to 'https://online-hd.amazingcontent.site/?tag_id=93577&cl=3&click=1', an opaque redirect destination. (location: page.html:105 (subInterstitialSettings), page.html:486-488)
malicious redirect
Canonical tag points to 'https://hdzog.com/' while the page is served from 'hdzog.tube', indicating the .tube domain is a mirror/shadow domain routing traffic to the primary property. The page explicitly sets 'window.isMirror = location.host.includes("hdzog.tube")' and uses different push notification spot IDs for mirror vs primary domain. (location: page.html:43, page.html:314)
hidden content
'window._hidden_channels' array contains channel IDs ['875','11009','1955','10889','11625'] that are hidden from the page UI but used internally, suggesting content suppression or shadow-listing of specific content channels not shown to users. (location: page.html:137-138)
social engineering
Time-limited 'UNLOCK FULL' / 'FULL VIDEO HERE' button scheme uses date-gated JavaScript to swap affiliate tracking URLs based on current date (active until 2026/03/15), manipulating users into clicking premium affiliate links disguised as free content access buttons. (location: page.html:114-135)
social engineering
Animated 'LIVE SEX' tab link with a blinking green dot CSS animation is designed to create false urgency and simulate live activity indicators to manipulate users into clicking affiliate/cam site links (ctwmsg.com/jasmin). (location: page.html:178-212)
hidden content
Client Hint delegation header ('delegate-ch') sends detailed browser fingerprinting data (ua, bitness, arch, model, platform, platform-version, full-version-list, mobile) to 'tsyndicate.com' without user awareness, enabling cross-site user tracking and profiling. (location: page.html:96)
hidden content
Yandex Metrika tracking pixels are loaded via hidden 'position:absolute; left:-9999px' images in noscript tags, providing covert analytics collection for users without JavaScript enabled. (location: page.html:77-81)
obfuscated code
Ad tag loader at '/0x8loikbes/y6klz0qp2g.js' uses a hex-encoded path ('0x8loikbes') to obscure its identity. The inline wrapper code that loads it is also minified/obfuscated, making static analysis of its behavior difficult. (location: page.html:106)
social engineering
Age verification bypass: localStorage key '_agv' is set to 1 when traffic arrives via tracked affiliate/promo parameters, silently bypassing age-gating for affiliate-sourced traffic while maintaining the age gate for organic/direct visitors. This is used to improve affiliate conversion rates by removing friction. (location: page.html:296-303)
malicious redirect
Push notification subscription system with service worker at '/ps/8Jk2IA.js' and '/lWMX6R.js' is configured to enroll users in push notification campaigns via 'notification.tubecup.net', with a direct link fallback to 'https://online-hd.amazingcontent.site/' for users who decline, ensuring traffic monetization regardless of subscription outcome. (location: page.html:105 (push spot configs))
curl https://api.brin.sh/domain/hdzog.tubeCommon questions teams ask before deciding whether to use this domain in agent workflows.
hdzog.tube currently scores 41/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.