context safety score
A score of 47/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
5 deceptive links where visible host does not match destination host
social engineering
The page displays grossly inflated and fabricated traffic statistics for bakkar-poteaux.com (846,499 daily visitors, $20,276,540.29 estimated worth), presenting false legitimacy metrics to deceive users into trusting the site or its valuations. The description also incorrectly aliases bakkar-poteaux.com as 'erothots', suggesting data mixing or deliberate mislabeling. (location: page.html:393, page.html:296-310)
brand impersonation
The subdomain bakkar-poteaux.com.prostats.org uses a deceptive hostname structure that makes it appear to be an official page of bakkar-poteaux.com when it is actually hosted on prostats.org. This subdomain-based impersonation technique is a classic brand hijacking pattern, serving fabricated statistics under the target domain's apparent authority. (location: metadata.json:1, page.html:50-55)
malicious redirect
The search form's get_sell_sheet() JavaScript function constructs a URL that redirects users to prostats.org with the user-supplied domain as a parameter, including an open redirect parameter '&redirect=https://<user-input>.prostats.org'. This open redirect can be abused to send users to arbitrary prostats.org subdomains, and uses window.open(url, '_self') to replace the current page with the redirect destination. (location: page.html:221-226)
social engineering
The 'Recently Viewed Websites' section displays fake real-time activity ('2 Sec ago', '6 Sec ago') to create a false sense of legitimacy and urgency, a common dark pattern used to manipulate user behavior and trust. (location: page.html:817)
brand impersonation
The page uses Google's favicon service (https://www.google.com/s2/favicons?domain_url=bakkar-poteaux.com) and pagepeeker thumbnail (https://free.pagepeeker.com/v2/thumbs.php?url=bakkar-poteaux.com) to render the target site's visual identity, presenting the analysis page as if it represents or is affiliated with bakkar-poteaux.com itself. (location: page.html:86-91, page.html:56)
social engineering
The page body text incorrectly identifies bakkar-poteaux.com as 'simply erothots', potentially linking an unrelated domain to adult content to manipulate search indexing or reputation perception of the target domain. (location: page.html:393)
curl https://api.brin.sh/domain/bakkar-poteaux.com.prostats.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
bakkar-poteaux.com.prostats.org currently scores 47/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.