context safety score
A score of 41/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
1 deceptive links where visible host does not match destination host
brand impersonation
The site runs a MediaWiki instance branded as 'WikiName' on bbarlock.com, a domain unrelated to any known wiki platform. The entire wiki shell appears to be a thin facade whose sole published content redirects visitors to an external commercial site (manovam.com), indicating the wiki brand/infrastructure is being impersonated or misused to lend legitimacy to the redirect. (location: page.html:5, page.html:33 — <title>WikiName</title> and 'From WikiName' subtitle)
malicious redirect
The only substantive content on the Main Page is a Turkish-language promotional blurb for 'Manovam' followed by a hard external link to https://www.manovam.com/en/category/jeanler. A legitimate wiki main page would not consist solely of an outbound commercial redirect. This pattern is consistent with a hijacked or spam-injected wiki page used to funnel traffic to an external e-commerce destination, potentially for SEO manipulation or affiliate fraud. (location: page.html:41-43 — the sole body paragraph and external link)
social engineering
The Turkish text translates to: 'As Manovam, we carefully design all our products and offer you the highest quality shopping experience. Images and descriptions belong to our brand; you can only reach our products through our official online store.' This phrasing is a social-engineering nudge urging users to trust and visit only the linked external store, reinforcing the redirect with a false exclusivity and authenticity claim embedded inside a trusted-looking wiki page. (location: page-text.txt:21-22 — visible body text)
hidden content
The page title and wiki branding ('WikiName', 'From WikiName') present a generic wiki identity with no real content, effectively hiding the true commercial/redirect purpose of the page behind a familiar MediaWiki UI shell. The wiki chrome (navigation, toolbars, footer) occupies the vast majority of the rendered page, visually obscuring the fact that the only real content is a single outbound commercial link. (location: page.html:30-68 — mw-content-text contains only the redirect paragraph; all other content is MediaWiki scaffolding)
curl https://api.brin.sh/domain/bbarlock.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
bbarlock.com 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.