context safety score
A score of 69/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
brand impersonation
The domain 'calabasase911.bbcportal.com' impersonates Blackboard (an Anthology/education technology brand) by using 'bbcportal' in the subdomain while serving content cloned from the legitimate Blackboard website (www.blackboard.com). The page renders Blackboard's 404 page with canonical URLs pointing to www.blackboard.com, suggesting the domain is set up to exploit Blackboard's brand identity under a deceptive third-party domain. (location: domain: calabasase911.bbcportal.com, page title: '404: Page Not Found | Blackboard')
phishing
The domain 'calabasase911.bbcportal.com' contains '911' in its name, a common urgency tactic used in phishing campaigns. Combined with brand impersonation of Blackboard (an educational LMS used by universities), this domain pattern is consistent with credential-phishing infrastructure targeting students and educators, even though the current page render is a 404. The domain may be in a staging/dormant state or rotating content. (location: domain: calabasase911.bbcportal.com)
malicious redirect
The pre-scan context notes 3 redirects occurred before the final page was served. The final destination renders a Blackboard 404 page with canonical pointing to www.blackboard.com, indicating the redirect chain may be used to evade detection or proxy legitimate content while maintaining a malicious domain for future use or selective targeting. (location: metadata.json: redirect chain (3 redirects), canonical URL: https://www.blackboard.com/404)
curl https://api.brin.sh/domain/calabasase911.bbcportal.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
calabasase911.bbcportal.com currently scores 69/100 with a caution 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.