context safety score
A score of 42/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
The 'stripchat-popunder' click handler on the play/info buttons performs a dual-destination redirect: it opens the intended video in a new tab while simultaneously redirecting the current page to an obfuscated affiliate/popunder URL at go.bluetrafficstream.com. This pattern exploits user intent to silently redirect the main window to a third-party ad network without disclosure. (location: page.html:5036-5039)
malicious redirect
A Stripchat affiliate link using a long obfuscated tracking URL (go.mavrtracktor.com/smartpop/...) is embedded in the footer as a sponsor link. The URL contains hashed user-tracking parameters and routes through a third-party ad broker before reaching the destination, masking the final endpoint. (location: page.html:4988)
hidden content
A third-party script from cdn.impactserving.com is injected dynamically at page load using an obfuscated self-executing IIFE that dynamically creates a script element and inserts it before the first existing script. This pattern is commonly used to load tracking/malvertising payloads in a way that bypasses static analysis. (location: page.html:5066)
obfuscated code
A Cloudflare challenge-platform script is injected via a hidden 1x1 invisible iframe that writes inline script content to the iframe's document, then appends a script tag loading '/cdn-cgi/challenge-platform/scripts/jsd/main.js'. The use of a hidden iframe to inject script context is an obfuscation technique that obscures what code is being executed and in what origin context. (location: page.html:5067)
malicious redirect
Two distinct domain variants are used for the same affiliate link: 'l.erodalabs.com/s/0ZIRw4' (in the mobile nav, line 83) and 'l.erodatalabs.com/s/0ZIRw4' (in the desktop nav and footer, lines 130, 177, 4987). One of these domains may be a typosquat of the other, creating a risk that one domain resolves to a different destination than intended. (location: page.html:83, 130, 177, 4987)
curl https://api.brin.sh/domain/hanime1.meCommon questions teams ask before deciding whether to use this domain in agent workflows.
hanime1.me currently scores 42/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.