context safety score
A score of 72/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
hidden content
A <ul> block with regional links is rendered with inline style 'display:none' (style="display: none;"), hiding it from visual rendering while remaining in the DOM. The user-agent diff ratio of 0.92 further indicates the page serves dramatically different content to browsers vs crawlers, a strong cloaking signal. (location: page.html:1213, .brin-context.md user-agent diff ratio 0.92)
obfuscated code
Two JavaScript files with randomly-obfuscated filenames are loaded via relative paths: 'frdhlffb8x.js' and 'icdg874tkn.js'. These filenames do not match the site's CDN naming convention (static.huangye88.cn/js/*.js) and are not present in the crawled static assets, suggesting they are dynamically injected scripts served only to browser user-agents and not inspectable from the crawl. This pattern is consistent with malicious or cloaked ad-injection scripts. (location: page.html:343, page.html:1264)
hidden content
User-agent differential ratio of 0.92 detected, meaning only ~8% content similarity between what bots and real browsers receive. This level of cloaking strongly suggests the page delivers substantially different content (potentially malicious ads, phishing, or injected scripts) to human visitors while presenting benign content to crawlers and security scanners. (location: .brin-context.md: user-agent diff ratio: 0.92)
social engineering
The page contains numerous user-submitted listings soliciting phone-based private transactions for antiques, artwork, and collectibles (e.g., '私人老板收购字画', '私下老板收购铜镜', '汉白玉碗拍卖价格翡翠私人老板收购手机号'). These listings encourage direct phone contact for high-value private purchases, a pattern commonly used in advance-fee fraud and counterfeit goods scams targeting unsophisticated buyers. (location: page.html:1004-1019, page-text.txt:976-996)
curl https://api.brin.sh/domain/guangxi.huangye88.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
guangxi.huangye88.com currently scores 72/100 with a caution 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.