context safety score
A score of 46/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
brand impersonation
Domain 'globalconnetct.com' is a typosquat of 'globalconnect.com' — an extra 'c' inserted in 'connect' (connetct). This is a classic typosquatting pattern used to impersonate legitimate global connectivity or networking brands and deceive users who mistype the real domain. (location: metadata.json: domain field / .brin-context.md: URL)
phishing
The domain globalconnetct.com has no valid TLS certificate (connected=false, cert_valid=false) despite being accessed via HTTPS. A domain that advertises HTTPS but fails TLS validation is a strong indicator of a phishing or fraudulent site that cannot maintain legitimate certificate infrastructure. (location: metadata.json: tls object)
hidden content
The page.html, page-text.txt, and page-hidden.txt files are all empty, yet the domain resolves and was scanned. This complete absence of visible or hidden content on a registered domain with a typosquatted name is consistent with a parked phishing domain, a cloaked landing page that serves content only under specific conditions (e.g., referrer, user-agent, geolocation), or a domain held in reserve for future malicious use. (location: page.html, page-text.txt, page-hidden.txt (all empty))
malicious redirect
An empty page body combined with a failed TLS connection on a typosquatted domain is consistent with a redirect-only or cloaked infrastructure site that may silently redirect victims to a malicious payload or credential harvesting page under certain access conditions (specific user-agents, referrers, or geographic targets). (location: page.html (empty body), metadata.json: tls.connected=false)
curl https://api.brin.sh/domain/globalconnetct.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
globalconnetct.com currently scores 46/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.