context safety score
A score of 48/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
The domain 'trafficmanager.cn' closely mimics 'trafficmanager.net', which is the legitimate Azure Traffic Manager service domain owned by Microsoft. The .cn TLD combined with a well-known Microsoft Azure service name is a classic brand impersonation pattern used to deceive users or automated agents into trusting the domain. (location: domain: trafficmanager.cn)
malicious redirect
The domain name 'trafficmanager' implies traffic routing/redirection capabilities. A lookalike domain for Azure Traffic Manager could be used to intercept or redirect network traffic, particularly targeting cloud-aware agents or infrastructure automation that recognizes the legitimate 'trafficmanager.net' pattern. (location: domain: trafficmanager.cn)
phishing
TLS connection failed (connected=false, cert_valid=false) indicating the site either does not serve HTTPS properly or is unreachable, yet the domain exists and was registered. This is consistent with a parked or dormant phishing domain held for future deployment or already used in non-browser (email link, API call) phishing campaigns. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
social engineering
The combination of a Microsoft Azure service name ('trafficmanager') under a .cn TLD could be used in social engineering scenarios targeting cloud engineers or DevOps professionals, convincing them the domain is a legitimate regional Azure endpoint for China, thereby tricking them into configuring infrastructure to route through an attacker-controlled host. (location: domain: trafficmanager.cn)
curl https://api.brin.sh/domain/trafficmanager.cnCommon questions teams ask before deciding whether to use this domain in agent workflows.
trafficmanager.cn currently scores 48/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.