context safety score
A score of 41/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page loads content in transparent or zero-size iframe overlay
malicious redirect
The page uses a JSONP callback (onCheqResponse) loaded from an external script at ob.sd559908.js.rsocdomains.com to immediately redirect the user to '/expired/result' with encoded parameters. This is a classic traffic distribution system (TDS) pattern used to redirect visitors based on bot/human detection, commonly employed in malvertising and phishing campaigns. (location: page.html:54-56, page.html:69-71)
hidden content
A zero-dimension hidden iframe (width='0' height='0' style='display:none') is loaded from obs.sd559908.js.rsocdomains.com as a noscript fallback, ensuring redirect/tracking behavior occurs even without JavaScript. This iframe is invisible to users and designed to operate covertly. (location: page.html:59-62)
obfuscated code
External JavaScript is loaded from a suspicious third-party domain (rsocdomains.com) using a hashed filename (58518ef7cff0c8433a35a3a4a06ac5dd.js) with custom data attributes (data-ch, data-jsonp, class='ct_clicktrue_93106'). This pattern is consistent with cloaking infrastructure that serves different content to bots vs. humans, obscuring the true payload from automated scanners. (location: page.html:53-56)
social engineering
The page displays a full-screen loading spinner (z-index: 9999) that covers all content and keeps users waiting while the bot-detection script runs and determines the redirect target. This creates a deceptive user experience designed to hold the visitor in place while traffic routing decisions are made server-side. (location: page.html:16-41, page.html:64-66, page.html:80-82)
curl https://api.brin.sh/domain/bactrimqwx.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
bactrimqwx.com currently scores 41/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.