context safety score
A score of 47/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 'comcastbusiness.net' impersonates Comcast Business, a legitimate brand operated at comcastbusiness.com. The '.net' TLD variant is a classic typosquatting/brand impersonation technique used to deceive users and AI agents into trusting a fraudulent domain as if it were the legitimate Comcast Business entity. (location: domain: comcastbusiness.net)
phishing
The domain closely mimics the legitimate Comcast Business domain (comcastbusiness.com) using a different TLD (.net). TLS connection failed (connected=false, cert_valid=false), meaning the site cannot establish a valid HTTPS connection, which is consistent with a phishing or parked malicious domain that has not properly configured SSL — further increasing risk to users who may be redirected here expecting the real Comcast Business site. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
malicious redirect
The TLS connection failure (connected=false) combined with a domain that impersonates a major brand suggests this domain may be used as a redirect waypoint or a parked phishing page. Users or agents following links to this domain expecting the legitimate Comcast Business site could be silently redirected to a credential-harvesting or malware-serving page. (location: metadata.json: tls block)
credential harvesting
A domain impersonating Comcast Business (a major ISP/enterprise services provider) with a failed TLS configuration is a high-risk vector for credential harvesting. Users who navigate here expecting to log into legitimate Comcast Business accounts may be presented with fake login forms designed to steal usernames and passwords. (location: domain: comcastbusiness.net)
curl https://api.brin.sh/domain/comcastbusiness.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
comcastbusiness.net currently scores 47/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.