context safety score
A score of 49/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
social engineering
The page aggressively promotes setting 2345.com as the browser homepage ('把2345设为主页'), claiming '已有4000多万人' (40 million users) have done so, and encourages downloading the '2345加速浏览器' browser which auto-sets 2345 as the homepage. This is a classic browser hijacking social engineering tactic used by potentially unwanted programs (PUPs). (location: page.html:509-511, page-text.txt:58)
malicious redirect
Multiple outbound links use affiliate tracking redirectors (duomai.com tracker: 'https://c.duomai.com/track.php?site_id=1587692&aid=2352...') and referral URLs (s.click.taobao.com, ads.taobao.com with bc_fl_src params) to route users through third-party redirect chains before reaching the destination. This obscures the true destination and introduces third-party tracking intermediaries. (location: page.html:574, page.html:566, page.html:594)
hidden content
A covert tracking beacon is injected via document.write() using a 0x0 invisible image pointing to '//web.50bangzh.com/web/2345', transmitting the user's referrer URL, screen resolution, and current page URL. The image has display:none, height=0, width=0 — entirely invisible to users. (location: page.html:637, page-text.txt:184)
hidden content
An invisible zero-size input element ('width:0;height:0;position:fixed;top:0;left:-5px;z-index:-1') exists in the DOM — consistent with clickjacking-assist or focus-stealing techniques used to intercept keyboard input without user awareness. (location: page.html:479)
social engineering
A link labeled '装软件赚钱' (Install software to make money) at jifen.yl234.com entices users to install software for monetary rewards — a common tactic used to distribute adware, PUPs, or browser hijackers under the guise of earning incentives. (location: page.html:486)
malicious redirect
The search form submits to 'https://www.2345.com/bdsearch/index.htm' rather than directly to Baidu, inserting a 2345-controlled intermediary into all Baidu searches. The hidden input field injects a tracking parameter (tn=25017023_2_pg) into every search query, attributing search traffic to 2345 for revenue without user awareness. (location: page.html:514 (form action), page.html:512 (hidden tn input))
curl https://api.brin.sh/domain/2345.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
2345.com currently scores 49/100 with a suspicious verdict and medium 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.