context safety score
A score of 41/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 loads content in transparent or zero-size iframe overlay
malicious redirect
A popunder script intercepts all page clicks and window blur/focus events (triggered by iframe interaction) to redirect the browser to https://go.tscprts.com/smartpop/895e33a7a01b8760f97a812fa57228ad3f2b53bd752e7ba0ebdf8d3314a10ccc — an obfuscated traffic-monetization URL. The script uses localStorage to throttle up to 3 redirects per hour, opens a duplicate window of the current page, then silently navigates the original tab to the popunder destination without user consent. (location: page.html:803-869 (also duplicated in page-text.txt:748-813))
social engineering
A fixed-position animated floating ad balloon (#balaoAdDireito) slides in from off-screen using CSS animations and bobs up and down to attract attention. It loads third-party ad iframes (webstats1.com or a-ads.com) and uses a close button with cookie gating to limit dismissals, designed to pressure users into interaction. The animation and persistence are crafted to maximise accidental clicks. (location: page.html:870-906)
malicious redirect
Ad iframes are dynamically injected based on browser language (pt-BR vs other). For pt-BR users, iframes point to https://webstats1.com/www/delivery/afr.php?zoneid=205 and zoneid=315 — an ad-delivery domain not affiliated with major ad networks, with a delivery path indicative of OpenX/Revive-style ad servers that have been historically abused for malvertising. For non-pt-BR users, scripts from https://poweredby.jads.co/js/jads.js (Juicy Ads adult ad network) are injected dynamically. (location: page.html:141-200)
social engineering
A native ad unit is embedded directly in the content grid styled identically to organic content posts, linking to https://a.logivanta42.com/f1d6fbcb-76ea-4093-bf34-fd58e912bfbd?creative=th_nat_3&spot=native&adg=0 with the title 'Create and Fuck your AI Slut'. The ad is only distinguishable by a small 'Ads' label and is designed to blend with editorial content to deceive users into clicking. (location: page.html:207-231)
malicious redirect
The native ad and date link both point to https://a.logivanta42.com — a third-party affiliate redirect domain. The domain 'logivanta42.com' has no established legitimate brand presence and uses a UUID-style path, consistent with affiliate traffic laundering or cloaked redirect chains leading to unknown destinations. (location: page.html:207,224,228)
hidden content
An ad container (#Ad_middle) is initialized with height:0px and overflow:hidden, only becoming visible via a CSS animation triggered by an IntersectionObserver when the element scrolls into view. While this is a common lazy-load pattern, the iframe loads content from https://candy.engine.adglare.net — a programmatic ad network — without any visible placeholder or user awareness until the animation fires. (location: page.html:428-461)
social engineering
The page embeds affiliate links to 'Undress AI' (https://www.cmonbae.com/?union_id=MTE1) and 'AI Sex Chat' (https://a.candyai.love/cb6237bf-87bb-4f12-84c1-22016a8485a2) in the top navigation bar styled as peer content categories. These are monetised affiliate redirects to third-party AI adult platforms, presented as site navigation rather than advertisements. (location: page.html:113-118)
curl https://api.brin.sh/domain/thehentai.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
thehentai.net currently scores 41/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.