context safety score
A score of 23/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
Obfuscated document.write with encoded content
obfuscated code
Multiple heavily obfuscated JavaScript blocks using hex-encoded variable names (_0x2f15c4, _0x582a, _0x3285, etc.), base64-encoded strings via atob(), and self-executing functions. One block dynamically loads an external script from a base64-decoded URL ('aHR0cHM6Ly9tZWV0eW91Lm1lL2Nhcm91c2VsLmpzLw==' decodes to 'https://meetyou.me/carousel.js/') injected into the page without any visible attribution. (location: page.html:130 and page.html:706)
malicious redirect
A hidden anchor tag with style='display: none' links to 'https://y99.in/carousel.php' with rel='nofollow', used as a cover URL. Immediately after, obfuscated JS dynamically loads 'https://meetyou.me/carousel.js/' (decoded from base64 atob call) — a third-party domain entirely separate from y99.in — injecting an unknown script into the page without user visibility or consent. (location: page.html:128-131)
hidden content
An anchor element with href='https://y99.in/carousel.php' and inline style 'display: none' is present in the body. This hidden link is not visible to users but is loaded by crawlers and agents, and serves as a decoy for the obfuscated script loader immediately following it. (location: page.html:128)
obfuscated code
The cookieconsent initialization block contains a self-obfuscating string-array decoder function (variables b, d, a with hex offsets 0xc4-0xcc) that manipulates window.location and listens for popstate events. The host check uses atob('eTk5Lmlu') to obscure the domain comparison 'y99.in', and the decoded logic rewrites browser history state — a pattern used to suppress URL bar changes during redirects. (location: page.html:73)
obfuscated code
Inside the AdSense loader callback, a base64-encoded array (_0x582a) is decoded and shuffled at runtime to resolve property names like 'location', 'href', 'push', 'adsbygoogle'. The code checks localStorage timing to throttle ad pushes and accesses window.location.href, consistent with obfuscated redirect or click-fraud logic hidden inside what appears to be an ad-loading routine. (location: page.html:706)
social engineering
Page targets emotionally vulnerable users with explicit messaging around loneliness, depression, hopelessness, and anonymity (e.g., 'those who live a hopeless life', 'get past your lonely lives', 'the feeling of being anonymous gives you the freedom to speak of anything'). This framing is designed to lower inhibitions and encourage engagement from vulnerable demographics including teens, depressed individuals, and isolated users. (location: page.html:1107-1115, page.html:1247-1258)
curl https://api.brin.sh/domain/y99.inCommon questions teams ask before deciding whether to use this domain in agent workflows.
y99.in currently scores 23/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.