context safety score
A score of 44/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
cloaking
Page conditionally redirects based on referrer or user-agent
malicious redirect
Frame-busting script forces top-level navigation if the page is loaded in an iframe: `if (window!= top) top.location.href = location.href;`. This breaks sandboxed analysis environments and prevents AI agents or security tools from safely rendering the page in a frame, and can be used to forcibly redirect users out of embedded contexts. (location: page.html:171)
hidden content
A CSS rule `body {display:none !important;}` with id 'antiHomo' hides the entire page body on load. A subsequent inline script removes this style only when the page is NOT in an iframe (`if (self === top)`). This creates a cloaking mechanism: the page appears blank to crawlers/sandboxes that render it framed, but displays normally to direct visitors, enabling content cloaking and evasion of automated scanners. (location: page.html:173-181)
malicious redirect
Third-party script loaded from `//powderencouraged.com/58/bc/f7/58bcf7e4bb1c4fea22cce7fe0e1caa2d.js` — an unrecognized, suspicious domain with an obfuscated path. This type of script is commonly used for malvertising, drive-by redirects, or payload delivery. No legitimate ad network or analytics provider is associated with this domain. (location: page.html:195)
malicious redirect
Third-party script loaded from `//driverhugoverblown.com/on.js` with `data-cfasync=false` (bypasses Cloudflare's Rocket Loader to ensure immediate execution). The domain name is nonsensical and obfuscated, consistent with malvertising or redirect chain infrastructure. Loaded async to avoid blocking page render while still executing. (location: page.html:196)
obfuscated code
Ad dispatch configuration referencing `xml.srvqk.com` and `static.srvqk.com` with numeric identifiers (`f: 1151320`, `a: 'rrTSHc'`). The domain `srvqk.com` is not a well-known ad network and uses opaque identifiers. The `display.js` script loaded from this domain can execute arbitrary code in the page context. (location: page.html:184-193)
social engineering
JuicyAds popunder script loaded from `js.juicyads.com` targeting an adult content audience. JuicyAds is a known adult ad network that serves popunders — a technique that opens new browser windows/tabs without explicit user interaction, commonly used to expose users to scam pages, fake prize notifications, or phishing landers. (location: page.html:742 / page-text.txt:542-544)
hidden content
JavaScript in the page body silently captures and populates a hidden Contact Form 7 field (`input[name='previous-url']`) with `document.referrer`, exfiltrating the visitor's referring URL upon form submission. The script contains Bulgarian-language comments attempting to obscure its purpose, describing it as the 'safest method' to find the field. This is covert referrer tracking embedded in form submissions. (location: page.html:624-642)
brand impersonation
The site uses official logos and brand names of Brazzers, Hustler, Penthouse, Dorcel, and Redlight to present itself as providing streams of those premium paid channels for free. This constitutes brand impersonation of legitimate adult entertainment companies to attract traffic, likely funneling users through malicious ad networks and redirect chains. (location: page.html:248-549)
hidden content
Commented-out affiliate/gambling links (`freebitco.in` and `bc.game`) remain in the HTML source inside the `.banner-sticky` div. While currently inactive, these reference crypto gambling platforms and suggest the site has been or may again be used to promote such services to its adult audience. (location: page.html:697-699)
curl https://api.brin.sh/domain/adult-tv-channels.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
adult-tv-channels.com currently scores 44/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.