context safety score
A score of 36/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
The scanned URL is informz.net but the page served is the Higher Logic (higherlogic.com) website. The canonical URL, og:url, and all internal links point to higherlogic.com, not informz.net. This indicates informz.net silently redirects or proxies content from a different domain without disclosure, which is a classic domain-redirect/cloaking pattern used to obscure the true origin of content. (location: metadata.json domain=informz.net vs page.html canonical href=https://www.higherlogic.com/)
obfuscated code
A script block uses a custom character-rotation obfuscation routine (atob + arithmetic character shifting loop) to dynamically construct a global property name and a remote script URL at runtime, preventing static analysis of what property is being set and what external script is being loaded. The decoded script src resolves to a third-party analytics/tracking domain (ZoomInfo/zi script) but the obfuscation itself is a high-severity signal as it actively hides the script's destination and the window property being written. (location: page.html line 1329 (also reflected in page-text.txt line 914))
curl https://api.brin.sh/domain/informz.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
informz.net currently scores 36/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.