context safety score
A score of 35/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
Third-party redirect engine 'trustpielote.com' loaded via renderer.js script with async execution. Navigation menu links (zones=300, 301, 302) all route through this domain. The hpRdrConfig sets ignoreIfNotVisible: false enabling unconditional redirect triggering. This is a known adult ad/redirect network that can deliver popunders and forced redirects to arbitrary destinations. (location: page.html:9071, page.html:190-198, page.html:9070)
malicious redirect
Tab-under (popunder) attack explicitly configured: window.hpPpConfig sets tabUnder: true with triggerMethod: 2 and a 24-hour cooldown period. This silently opens a new tab to an advertiser-controlled URL when users click gallery or category links, redirecting behind the current tab without clear user consent. (location: page.html:9060-9067)
malicious redirect
External advertisement script loaded from 'stats.hprofits.com/advertisement.min.js' — an opaque, minified third-party ad script over which the site has no control. This domain is associated with adult traffic monetization networks and can serve dynamic redirect payloads. (location: page.html:22, page.html:9053)
malicious redirect
Navigation link labeled 'VOD' routes to 'fhgte.com/gay' with UTM parameter utm_campaign=ai.CxY, an externally controlled domain unrelated to icegay.tv. The destination domain is opaque and could redirect users to arbitrary content or harvesting pages. (location: page.html:202)
hidden content
Meta referrer policy set to 'unsafe-url', which causes the full URL (including any query parameters containing tokens, session IDs, or sensitive data) to be sent as the Referer header to all third-party domains contacted by the page, including ad networks and analytics endpoints. (location: page.html:5)
social engineering
Navigation menu items labeled 'AI JERK OFF', 'Live Sex', 'HD Porn', and 'VOD' are styled identically to legitimate site navigation links but route to external third-party ad/redirect networks (trustpielote.com, fhgte.com). This disguises outbound commercial redirect links as first-party site navigation, deceiving users about their destination. (location: page.html:190-204)
curl https://api.brin.sh/domain/icegay.tvCommon questions teams ask before deciding whether to use this domain in agent workflows.
icegay.tv currently scores 35/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.