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 'gov-img.site' uses the substring 'gov' to impersonate or suggest affiliation with a government entity while using a non-governmental TLD (.site). This is a classic pattern for deceiving users into trusting the site as an official government resource. (location: domain: gov-img.site)
phishing
The domain 'gov-img.site' combines a government-trust keyword ('gov') with a generic TLD ('.site') — a pattern commonly used in phishing infrastructure targeting users who expect government domains (e.g., .gov TLD). The site also failed TLS connection (connected=false, cert_valid=false), which is consistent with newly stood-up or abandoned phishing infrastructure. (location: domain: gov-img.site, metadata.json TLS fields)
hidden content
The context file references a 'page-hidden.txt' for extracted hidden content, indicating the scan pipeline detected or anticipated hidden elements. The page.html and page-text.txt are both empty, suggesting the page may have served no content at scan time — consistent with cloaking behavior where content is only served to real user agents or specific IP ranges, hiding malicious content from automated scanners. (location: page.html (empty), page-text.txt (empty), page-hidden.txt (empty), .brin-context.md line 16)
malicious redirect
The page returned no HTML content despite the domain being reachable enough for metadata to be collected. Empty page bodies with active domains are a common indicator of redirect-only infrastructure or conditional redirection (serving content only to targeted victims while appearing empty to scanners). (location: page.html (empty body), metadata.json url: https://gov-img.site)
curl https://api.brin.sh/domain/gov-img.siteCommon questions teams ask before deciding whether to use this domain in agent workflows.
gov-img.site 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.