context safety score
A score of 43/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
Aggressive popunder/tabunder ad system fires on nearly every user click. Multiple force_url targets (directsle.com, porn03.com, kts.bartcons.com, s.pemsrv.com) redirect users without consent, with capping intentionally bypassed via reset_cappings logic and country-specific targeting (Ukraine gets a unique hardcoded redirect URL with an obfuscated token). (location: page.html:lines 69-925, popOptions.config.options.popunder_type, directPop() function)
malicious redirect
The site uses a canonical tag pointing to hclips.com while serving content on privatehomeclips.com, explicitly self-identifying as a mirror site (window.isMirror). The domain privatehomeclips.com impersonates the hclips.com brand to capture traffic under a deceptive domain name. (location: page.html:line 12 (rel=canonical href=https://hclips.com/), line 158 (window.isMirror))
brand impersonation
privatehomeclips.com is explicitly coded as a mirror of hclips.com. The codebase shares the same ad network keys, CDN (hcjs.nv7s.com), project infrastructure, and push notification service worker. The domain name misleads users into believing they are visiting a legitimate 'private home clips' site when it is a traffic-arbitrage mirror of hclips.com. (location: page.html:lines 56, 140-143, 158, 688)
hidden content
window._hidden_channels = ['1477', '1479'] defines hidden channel IDs that are not visible in any rendered UI element. These channels are loaded/referenced programmatically without user awareness, likely used for hidden ad inventory or content suppression. (location: page.html:line 1107, page-text.txt:line 1041)
hidden content
The app root div contains only a near-invisible character: <div id="app"><i style="font-size:0.1px">...</i></div>. All actual page content is injected dynamically via JavaScript, making static crawlers and safety scanners blind to the real rendered content. (location: page.html:line 1129)
social engineering
Time-gated link overlays with urgency-inducing labels ('UNLOCK FULL', 'FULL VIDEO HERE', 'TikTok Porn', 'AI Sex Chat' with a blinking green dot animation) are used to drive clicks to affiliate/pay sites. The blinking dot CSS animation (.green-blink-dot) is a manipulative UI pattern designed to draw attention and deceive users into clicking. (location: page.html:lines 82-105, 1026-1066, 1069-1089)
malicious redirect
Push notification subscription interstitial (subInterstitialSettings.directLink) points to https://online-hd.amazingcontent.site/?tag_id=93577 — an unrelated third-party site. Users who interact with the push subscription prompt may be redirected to this site without understanding the destination. (location: page.html:line 73 (subInterstitialSettings.directLink in push spot configs))
hidden content
Client Hints delegation header (delegate-ch) silently forwards detailed browser fingerprint attributes (architecture, platform, full UA version, mobile status) to tsyndicate.com without user knowledge or disclosure. This enables covert cross-site user profiling. (location: page.html:line 63 (meta http-equiv=delegate-ch))
obfuscated code
A large obfuscated JavaScript blob is loaded from hcjs.nv7s.com with a hash-keyed filename: siksik7.10.13.55bb3b3d064c96ff78fe8ff1017d70a4.js. The filename structure (hash in the name) and the randomized variable names (XNEwTDKq, VisvkxDc, _3bv8lhpo9z) indicate intentional obfuscation of the ad/tracking payload to evade analysis. (location: page.html:lines 68-75)
social engineering
Age verification is silently bypassed via a promo parameter: if promo=47201, the age gate cookie (_agev) and localStorage flag (_agv) are set to 1 without any actual age confirmation. This circumvents age-gating controls programmatically. (location: page.html:lines 179-190)
malicious redirect
A traffic distribution system (TDS) endpoint at https://tds.bestsafefast.com/tds/in is embedded as window.ext_url, used for programmatic redirect routing. The domain 'bestsafefast.com' is a known TDS operator used to route traffic to malvertising and affiliate networks. (location: page.html:line 153)
curl https://api.brin.sh/domain/privatehomeclips.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
privatehomeclips.com currently scores 43/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.