context safety score
A score of 42/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
script/meta redirect patterns detected in page source
brand impersonation
The page title is '天使动漫-樱花动漫在线观看_AGE天使动漫下载' and meta keywords include '樱花动漫' and 'AGE动漫', falsely claiming association with or impersonating the well-known '樱花动漫' (Sakura Anime) brand. The actual domain is acg2day.com, which has no legitimate affiliation with Sakura Anime. (location: page.html: <title> tag and <meta name='keywords'> tag)
brand impersonation
The site's friend-links section labels 'https://www.166dm.com' as '樱花动漫' (Sakura Anime). 166dm.com is a distinct third-party domain, not the actual Sakura Anime site. This misrepresents external destinations to deceive users about where they are navigating. (location: page.html: domainList JS variable and friend-links section)
social engineering
A persistent popup notice (noticeContent) employs urgency language — '🔔重要公示🔔', '屏蔽严重，记住以下网址回家' (Severe blocking, remember this URL to come home) — to pressure users into bookmarking omoo.app and fb.omoo.tv as alternate access domains. This is a retention tactic designed to keep users connected to the site's ecosystem through fear of losing access. (location: page.html: <div class='noticeContent'> popup)
malicious redirect
Multiple JavaScript window.location redirects are present (3 JS redirect patterns per Tier 2 scan). Two are benign navigation (user profile page, search form submission). The third dynamically redirects search queries to on-domain URLs. No evidence of off-domain forced redirects at page load, but the redirect infrastructure warrants monitoring. (location: page.html: inline JavaScript search and navigation handlers)
hidden content
A <div class='hide'> element contains the label '统计代码' (statistics/tracking code). While the visible content of the div is only a label, it marks a section boundary for analytics/tracking code that follows, potentially obscuring the scope of user tracking from casual inspection. (location: page.html: <div class='hide'>统计代码</div> at position ~94868)
curl https://api.brin.sh/domain/acg2day.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
acg2day.com 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.