context safety score
A score of 40/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
phishing
1 deceptive links where visible host does not match destination host
obfuscated code
Multiple instances of an ExoLoader ad script (magsrv.com) use runtime obfuscation: Object.defineProperty overrides document.currentScript.innerHTML and textContent getters to return randomly generated strings, and dispatches a custom 'getexoloader' DOM event to bootstrap an external ad loader. This pattern is designed to evade static analysis and content-security inspection by tools and AI agents reading the page source. (location: page.html lines 483-488, 1661-1665, 1719-1723)
malicious redirect
A script loaded from the opaque path https://thisvid.com/enblk/envbcdldr.php is invoked via ExoLoader.serve(). The path 'enblk/envbcdldr' (likely 'ad-block' / 'env-block-loader') suggests an anti-adblock or redirect payload loader that fetches and executes remote code dynamically, enabling arbitrary redirects or payload delivery without the destination being visible in static HTML. (location: page.html lines 1722, 66 (envblk.js))
hidden content
All video thumbnail images are loaded using a 1x1 transparent GIF data URI as the src attribute (data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7) with the real URL stored in a 'data-original' attribute and swapped by JavaScript. While this is a common lazy-load pattern, it means an agent or scraper reading raw HTML sees no actual image content and the true loaded resources are obscured until JS executes. (location: page.html lines 324, 337, 350, etc. (all thumbnail img tags))
hidden content
The page body is initially rendered invisible (opacity:0) and only made visible after DOMContentLoaded fires via JavaScript. An agent or renderer that does not execute JavaScript will see a blank page, masking the true page content from static analysis tools. (location: page.html line 64 (body style='opacity: 0') and lines 49-51)
malicious redirect
A meta http-equiv='delegate-ch' header delegates multiple Client Hints headers (sec-ch-ua, sec-ch-ua-platform, sec-ch-ua-full-version-list, sec-ch-ua-mobile, etc.) to https://tsyndicate.com — a third-party ad network. This causes the browser to automatically send detailed user agent and device fingerprinting data to tsyndicate.com on every request, without any user consent indication beyond the generic cookie notice. (location: page.html line 62)
social engineering
The site prominently advertises 'Submit your homemade porn video for free' and features a 'Sign up / Upload' flow that requires account registration. The signup and upload links redirect unauthenticated users to login-gated pages, which is a common funnel to harvest user registrations and personal data under the premise of free content submission. (location: page.html lines 77-87, 293-298, meta description line 7)
hidden content
The LIVE CAMS navigation link points to https://tsyndicate.com/api/v1/direct/0a9ecc1a46184108baa26bab9dcf7666 — a direct third-party ad-network API URL — rather than an on-site page. This is presented to users as a site navigation item but actually routes to an external ad/affiliate redirect endpoint, obscuring its true destination. (location: page.html lines 221-224)
curl https://api.brin.sh/domain/thisvid.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
thisvid.com currently scores 40/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.