context safety score
A score of 32/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 loads content in transparent or zero-size iframe overlay
brand impersonation
The page title and meta tags display '中国tyc5997太阳集团(Macau)有限公司-Official website' and keyword '太阳tyc集团5997', which impersonate a legitimate Chinese industrial company (Boyang Machinery / 博阳机械, aqbyjx.com). The site presents itself as an official website of a Macau-registered group while the actual domain bdx360.com is only 58 days old and the content references an unrelated industrial machinery company. (location: page.html:24-26, <title> and <meta> tags)
hidden content
A script tag with an obfuscated HTML-entity-encoded src attribute is loaded inside a display:none div at the bottom of the page: <div style="display:none"><script src="/@public/js.js"></script></div>. Decoded, the src is '/@public/js.js'. This hidden script load is concealed from casual inspection and likely serves tracking, SEO manipulation, or malicious payload delivery purposes. (location: page.html:795)
obfuscated code
Two script tags use HTML entity encoding to obfuscate their src attributes. First instance in <head>: src="/@public/base.js" decodes to '/@public/base.js'. Second instance in hidden div: src="/@public/js.js" decodes to '/@public/js.js'. Obfuscation is used to hide the true script paths from security scanners. (location: page.html:28, page.html:795)
hidden content
JavaScript at the top of the body disables right-click context menu, text selection, drag, copy, and mouseup events (oncontextmenu, ondragstart, onselectstart, onbeforecopy, oncopy all return false). This is a classic anti-forensics technique to prevent users and security tools from easily inspecting or copying page content. (location: page.html:33-34)
brand impersonation
The page's visible branding references '太阳tyc集团5997' (Sun TYC Group 5997), which resembles naming conventions used by Chinese gambling/casino affiliate spam networks (tyc = 太阳城 Sun City Group, a known Macau casino brand). The meta description explicitly mentions sports betting, esports, football wagering, and live casino services ('体育资讯、电子竞技、足球竞猜、真人视讯'), while the visible page content shows industrial machinery — indicating a cloaking/SEO spam operation impersonating a legitimate manufacturer. (location: page.html:25-26, <meta name=keywords> and <meta name=description>)
social engineering
The meta description (hidden from visitors but visible to crawlers and AI agents) promotes an online gambling platform with '注册登录送不停' (register and login for non-stop bonuses) and '24小时提供在线为您服务' (24-hour online service), using the guise of a legitimate industrial manufacturer website. This is a cloaking technique designed to deceive both users and automated systems. (location: page.html:26, <meta name=description>)
malicious redirect
Banner images are dynamically wrapped with links to an external domain 'http://www.aqbyjx.com' (non-HTTPS) via inline JavaScript. This redirects users clicking on banner images to an external site without clear indication, and uses plain HTTP which exposes users to potential MITM attacks. (location: page.html:290-292)
hidden content
A script tag with path '/css/mooncode.js' is loaded from an unconventional location (CSS directory). The filename 'mooncode' is non-standard and the placement in /css/ is anomalous, suggesting a hidden or obfuscated script loader disguised to blend in with stylesheet references. (location: page.html:15)
curl https://api.brin.sh/domain/bdx360.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
bdx360.com currently scores 32/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.