context safety score
A score of 25/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
malicious redirect
script/meta redirect patterns detected in page source
obfuscated code
Heavily obfuscated JavaScript using a string-array rotation cipher with numeric index lookups (function b(n,t) pattern). The obfuscated bundle is loaded inline and decodes strings at runtime to hide its true behavior, including pop-under ad delivery via novel-inevitable.com. This technique is commonly used to conceal malicious payloads from static scanners. (location: page.html:169-172)
malicious redirect
The onbeforeunload handler intercepts navigation attempts and forcibly opens '/o' in a new tab AND redirects the current page to '/o' simultaneously, trapping the user. This is a classic exit-redirect / tab-trap technique used to force unwanted ad or affiliate pages on users trying to leave. (location: page.html:176-184)
malicious redirect
Obfuscated script at page load decodes a Caesar-cipher shifted URL ('iuuqt;00jg3.deo.upt/czufdeoupq/dpn...' shifted by -1 yields 'https://if2-cdn.top.bytecdn.com/cdn/expire-1-M/jquery.lazyload/1.9.7/jquery.min.js') and conditionally injects it as a script element targeting mobile devices only (Android/iOS/BlackBerry). The device fingerprinting via WebGL renderer detection and the obfuscated CDN domain suggest a malicious script injection targeting mobile browsers. (location: page.html:18)
malicious redirect
Pop-under ad network script from novel-inevitable.com configured with scriptSrc and window.url parameters pointing to that domain. The obfuscated wrapper orchestrates pop-under windows (newTab:true, under:true in d object) with frequency capping (qty:3 per 3600s). novel-inevitable.com is a known aggressive ad/redirect network associated with malvertising chains. (location: page.html:168-172)
obfuscated code
Outbound affiliate/traffic links in the thumb-top section use base64-encoded destination URLs in the 'member' query parameter (e.g., b64YmFiZXNwaXJhdGUuY29t decodes to 'babespirate.com'). All 30 outbound partner links obfuscate their destinations via base64 encoding, preventing users and scanners from seeing where clicks lead. (location: page.html:130-159)
social engineering
The onbeforeunload dialog presents a browser confirmation prompt 'Are you sure you want to leave?' to manipulate users into staying on the page, a well-known dark pattern that exploits browser UI trust to re-engage or redirect departing visitors. (location: page.html:177-183)
malicious redirect
All gallery thumbnail links route through a local redirect script '/out.php?link=...&url=...' rather than linking directly. This redirect layer can modify or substitute the final destination dynamically, enabling tracking, affiliate fraud, or forwarding to malicious sites without the destination being visible in the HTML. (location: page.html:43)
hidden content
The page uses <base target='_blank'> globally, causing all links (except those with explicit target='_self') to open in new tabs by default. Combined with the exit redirect and pop-under scripts, this creates a multi-vector tab-proliferation attack that overwhelms the user's browser session. (location: page.html:11)
curl https://api.brin.sh/domain/french-girls.tvCommon questions teams ask before deciding whether to use this domain in agent workflows.
french-girls.tv currently scores 25/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.