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
malicious redirect
TLS connection failed entirely (connected=false, cert_valid=false, san_match=false) for epolice.ir. A site impersonating a government police authority that cannot establish a valid TLS session is a strong indicator of a deceptive or infrastructure-compromised site that may redirect users through insecure channels or intercept traffic. (location: metadata.json: tls fields)
brand impersonation
The domain epolice.ir uses the 'epolice' name, directly mimicking official government/law enforcement branding ('e-police' / electronic police). Combined with failed TLS and empty page content, this pattern is consistent with a brand impersonation site targeting users seeking official police services in Iran. (location: metadata.json: domain=epolice.ir)
social engineering
A domain presenting itself as an official government law enforcement portal (epolice.ir) while serving no verifiable content and having invalid TLS creates conditions for social engineering: users trusting the name may submit sensitive information or follow instructions from a non-authenticated source. (location: metadata.json: domain=epolice.ir, tls.connected=false)
credential harvesting
Government/police-themed domains with broken TLS and no retrievable content are a known credential harvesting pattern — the live site may present login forms or ID/document submission forms that are not captured in the static snapshot, while the domain name lends false authority to solicit credentials. (location: metadata.json: domain=epolice.ir, tls fields)
curl https://api.brin.sh/domain/epolice.irCommon questions teams ask before deciding whether to use this domain in agent workflows.
epolice.ir 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.