context safety score
A score of 41/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
phishing
Domain 'portal-bia.protecao-cliente.click' uses a deceptive structure mimicking a legitimate customer protection portal ('protecao-cliente' means 'client protection' in Portuguese). The subdomain 'portal-bia' combined with a .click TLD and a Portuguese-language trust-baiting domain name is a classic phishing pattern designed to impersonate a financial or government institution's client portal. (location: domain: portal-bia.protecao-cliente.click)
brand impersonation
The domain 'protecao-cliente.click' translates to 'client-protection.click' in Portuguese and the subdomain 'portal-bia' likely impersonates BIA (Banco Inter or another Brazilian financial/government entity). This pattern is consistent with Brazilian financial brand impersonation campaigns targeting users through fake customer protection portals. (location: domain: portal-bia.protecao-cliente.click)
credential harvesting
The combination of a fake customer protection portal domain, .click TLD, and failed TLS connection (connected=false, cert_valid=false) is strongly indicative of a credential harvesting site. Fake 'portal' and 'protecao-cliente' branding is commonly used to trick victims into submitting login credentials or personal data. (location: domain: portal-bia.protecao-cliente.click; TLS: connected=false, cert_valid=false)
malicious redirect
The .click TLD is frequently abused in redirect chains and malvertising campaigns. The site could serve as a redirect node routing victims to downstream credential harvesting or malware delivery pages. The failed TLS connection may indicate the page content was not retrievable, potentially because it fingerprints visitors before serving malicious content. (location: domain: portal-bia.protecao-cliente.click; metadata.json tls.connected=false)
social engineering
The domain name pattern 'protecao-cliente' (client protection) is a social engineering construct designed to instill false trust and urgency. Users searching for account protection or fraud resolution services may be deceived into believing this is a legitimate institutional portal, lowering their guard before submitting sensitive information. (location: domain: portal-bia.protecao-cliente.click)
curl https://api.brin.sh/domain/portal-bia.protecao-cliente.clickCommon questions teams ask before deciding whether to use this domain in agent workflows.
portal-bia.protecao-cliente.click currently scores 41/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.