context safety score
A score of 65/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
9 deceptive links where visible host does not match destination host
social engineering
The domain bigpot.news hosts a minimal shell page ('Blog') whose sole visible content is a dense set of links pointing exclusively to nationpress.com. The page has no original content, no articles, and no legitimate purpose — it is a classic link-farm or SEO manipulation page designed to artificially boost nationpress.com's search ranking, potentially deceiving users and search crawlers into treating bigpot.news as a legitimate referral source. (location: page.html:29-49, entire article body)
hidden content
Three anchor tags with href pointing to bigpot.news itself contain completely empty text nodes (no visible label or content). These empty self-referential links serve no user-facing purpose and may be used for internal link-equity manipulation or as placeholder hooks for future injection of hidden anchor text. (location: page.html:51-53)
curl https://api.brin.sh/domain/bigpot.newsCommon questions teams ask before deciding whether to use this domain in agent workflows.
bigpot.news currently scores 65/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.