context safety score
A score of 61/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
brand impersonation
The domain clientrewardsgpo.com serves a full replica of the Foodbuy (www.foodbuy.com) website, including Foodbuy logos, navigation, branding, footer, copyright notice, and all assets loaded from foodbuy.com. The scanned domain has no affiliation with Foodbuy but presents entirely as Foodbuy to visitors. (location: page.html - entire page; <title>Page not found - Foodbuy</title>, logo src='https://www.foodbuy.com/...foodbuy-logo.png', og:site_name='Foodbuy')
malicious redirect
The domain clientrewardsgpo.com performed 2 redirects before serving the Foodbuy-branded 404 page. This redirect chain from an unrelated domain to Foodbuy content is consistent with a typosquatting or affiliate-fraud redirect scheme. (location: .brin-context.md - Redirects: 2; page.html - all content originates from www.foodbuy.com assets)
social engineering
The page presents a 404 error under the Foodbuy brand with a search form whose action submits to https://www.foodbuy.com/. A visitor arriving at clientrewardsgpo.com (e.g., from a 'client rewards' phishing lure) would see a trusted Foodbuy interface, potentially encouraging them to interact with the search form or click login/partner links. (location: page.html line 393: <form ... action='https://www.foodbuy.com/' ...>; page.html line 383: <h1>Oops! That page can't be found.</h1>)
hidden content
The page contains a robots meta tag 'noindex, follow' which suppresses the page from search engine indexing while still allowing crawlers to follow links. This is atypical for a legitimate landing page and may indicate intentional concealment from security crawlers or search visibility. (location: page.html line 9: <meta name='robots' content='noindex, follow' />)
social engineering
A Microsoft SafeLinks-wrapped URL in the footer 'Privacy Requests' link contains encoded PII (employee email GPhillips@foodbuy.com) in the URL parameters. While SafeLinks is a Microsoft email security feature, its presence in a footer link on a non-Microsoft domain suggests the link was copied from a private email context and leaks internal contact information. (location: page.html line 537: href='https://nam11.safelinks.protection.outlook.com/?url=...data=05%7C02%7CGPhillips%40foodbuy.com...')
curl https://api.brin.sh/domain/clientrewardsgpo.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
clientrewardsgpo.com currently scores 61/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.