context safety score
A score of 43/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
js obfuscation
Obfuscated document.write with encoded content
malicious redirect
A script is loaded from the opaque third-party domain 'zf.ferruleloimic.com' (protocol-relative URL //zf.ferruleloimic.com/rJf2cxPpfLRoZDw/nQRBa) with no sri integrity check and data-cfasync=false to bypass Cloudflare screening. The domain name is nonsensical/random-looking, consistent with ad-fraud, malvertising, or traffic-redirect networks. The obfuscated path (rJf2cxPpfLRoZDw/nQRBa) provides no transparency about the script's function. (location: page.html line 124)
obfuscated code
A Cloudflare challenge script injected inline via a hidden iframe creates and appends a secondary script from '/cdn-cgi/challenge-platform/scripts/jsd/main.js', using self-executing anonymous function obfuscation and base64-encoded parameter 't':'MTc3MjYyNzQxMA==' (decodes to a timestamp). While this pattern is typical of Cloudflare Bot Management, the technique of dynamically injecting scripts via hidden iframes is also a known malware delivery mechanism and warrants flagging. (location: page.html line 4781)
social engineering
A navigation menu item labelled 'AI Jerk Off' links externally via rel=nofollow to 'https://juicyads.in/tab.php?id=2101969', an adult advertising network redirect. The label is designed to exploit curiosity/arousal to drive clicks to a third-party ad network, which may serve malicious or deceptive advertisements. (location: page.html line 224)
malicious redirect
A popup banner modal is dynamically populated from 'hencover.xyz' (a separate domain from hentairead.com) and redirects users to 'manhwaread.com'. The popup fires automatically on page load unless suppressed by localStorage, and opens the destination in a new tab via window.open(). The cross-domain popup-to-redirect pattern is commonly used for forced traffic monetization and can deliver malvertising payloads. (location: page.html lines 4726-4761)
credential harvesting
Login, signup, and password-reset forms collect email addresses and passwords via modal dialogs. Credentials are submitted to 'https://hentairead.com/auth/register' and 'https://hentairead.com/wp-admin/admin-ajax.php'. While these appear to be standard site authentication forms, the site hosts third-party ad scripts (including the suspicious zf.ferruleloimic.com script) that execute in the same page context and could intercept form field values. (location: page.html lines 4642-4666, 4580-4600)
curl https://api.brin.sh/domain/hentairead.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
hentairead.com currently scores 43/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.