context safety score
A score of 38/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
obfuscated code
Large heavily obfuscated JavaScript block in <head> using character-code shifting, string splitting, array indexing, and self-executing IIFE to conceal its true behavior. The encoded string 'cmeccZYhfZb^W^TR^...]' is decoded at runtime via a Caesar-cipher-like rotation on ASCII values. The decoded logic dynamically constructs URLs, sets cookies, and likely performs ad injection, fingerprinting, or redirect logic that is not visible in static analysis. (location: page.html:33 (inline <script> tag, line 33))
obfuscated code
Second obfuscated JavaScript block in the footer using the same character-rotation obfuscation pattern ('cmeccZYhfZb^W^[_`PURNLXWMYIQXJKEDNK...'). Dynamically constructs ad network URLs and injects ad spots into the DOM via data-cl-spot attributes. Pattern is consistent with ad-fraud or drive-by redirect infrastructure. (location: page.html:2903 (inline <script> in footer .box.bottom-adv))
malicious redirect
External script loaded from 'astronautlividlyreformer.com/on.js' — a randomized-word domain pattern (three dictionary words concatenated) typical of ad-fraud, malvertising, and drive-by-download delivery networks. The script is loaded async with data-cfasync=false (bypasses Cloudflare rocket-loader) and registers callbacks hkbpibp() on both onload and onerror, allowing it to execute regardless of load status. (location: page.html:34 (<script src='//astronautlividlyreformer.com/on.js'>))
malicious redirect
External script loaded from 'deductgreedyheadroom.com/bn.js' — another randomized three-word domain consistent with malvertising infrastructure. Also uses data-cfasync=false bypass and registers itkernkx() callbacks on both load and error events. Two separate such domains across the same page indicates an organized ad-fraud or malware delivery network. (location: page.html:2904 (<script src='//deductgreedyheadroom.com/bn.js'>))
malicious redirect
Multiple outbound affiliate tracking links routed through 'go.mavrtracktor.com' with embedded userId hash (233a384a86a454bbecf8edf93e82eaffc7df6676f1b240344cfa9777cdb203fb) and action parameters including 'sbSignupWithModel' and 'showTokensGiveawayModalDirectLink'. These links redirect users to Stripchat live-cam signups without clearly disclosing the affiliate/redirect relationship. The tracker domain 'mavrtracktor' is designed to obscure the true destination. (location: page.html:48,52 (header 'Live Girls!' and 'Sex Cams' links))
social engineering
Embedded iframe from 'creative.rmhfrtnd.com' widget with parameters 'buttonText=Online Girls', 'titleText=Chat Now', and 'autoplay=onHover' designed to lure users into clicking through to live-cam/adult subscription services. The widget is embedded in the video grid as a native-looking content tile, making it indistinguishable from regular video thumbnails to casual users and automated agents. (location: page.html:321 (<iframe src='https://creative.rmhfrtnd.com/widgets/v4/Universal?...'))
hidden content
Three ad injection placeholder divs using 'data-cl-spot' attributes (IDs: 1988009, 1979635, 1979634) that are populated at runtime by the obfuscated footer script. The actual ad content served into these slots is indeterminate from static analysis and could include malvertising, redirectors, or phishing overlays depending on the ad network's current payload. (location: page.html:2906-2913 (footer div.block-img data-cl-spot elements))
curl https://api.brin.sh/domain/mzansipornvideos.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
mzansipornvideos.com currently scores 38/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.