context safety score
A score of 39/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
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
A pop-under/pop-up ad script (popMagic) is embedded directly in the page, configured with 'popup_fallback: true', 'trigger_method: 2', and connecting to external ad hosts 'a.pemsrv.com' and syndication host 's.dss29f.com'. This script programmatically opens new browser windows/tabs on user interaction, a common vector for redirecting users to malicious or unwanted sites. (location: page.html:35-56, page-text.txt:5-20)
malicious redirect
Third-party ad provider script loaded from 'https://a.magsrv.com/ad-provider.js' with an ad insertion tag (data-zoneid: 2591175). External ad networks on adult content sites are frequently used to serve malvertising and redirect users to phishing or malware pages. (location: page.html:34)
obfuscated code
The popMagic script uses heavily minified and obfuscated JavaScript with single-character variable names throughout (e.g., 'function o(e,i,t,n,r)'), making its full behavior difficult to audit. It overrides native DOM methods (document.querySelectorAll) and dynamically loads hosted content via 'loadHosted()', obscuring what resources are ultimately fetched and executed. (location: page.html:36-56, page-text.txt:22)
social engineering
The page solicits cryptocurrency donations with a Bitcoin address ('Donate BTC: 14ko11NvcemFm2q5NpjpGiTbPhmB8pfnpC'), which is a common tactic on ad-heavy or piracy-adjacent sites to collect funds with no accountability or recourse for users. (location: page-text.txt:1)
hidden content
Script raw source code (JavaScript function bodies and ad configuration objects) is rendered as visible text in the page's text content, suggesting portions of script are either not properly enclosed or are being injected into the DOM as text nodes, which can obscure malicious payloads from casual inspection. (location: page-text.txt:1-23)
curl https://api.brin.sh/domain/hitomi.laCommon questions teams ask before deciding whether to use this domain in agent workflows.
hitomi.la currently scores 39/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.