context safety score
A score of 66/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
brand impersonation
The page was fetched from allamericansportsbar.com but the Cloudflare challenge page references cZone 'animaldermatologypdx.com' as the protected zone. The Cloudflare challenge infrastructure is serving content scoped to a completely different domain (animaldermatologypdx.com), indicating the scanner may have been redirected to — or the domain is serving — a Cloudflare challenge belonging to an unrelated domain. This domain mismatch is a strong indicator of misconfiguration at minimum, and potential domain squatting or traffic hijacking at worst. (location: page.html: window._cf_chl_opt.cZone = 'animaldermatologypdx.com')
malicious redirect
The Cloudflare challenge JS rewrites browser history to '/yeast-skin-infection/?__cf_chl_rt_tk=...' using history.replaceState, redirecting the user's visible URL away from the originally requested page. While this can be legitimate Cloudflare behavior, combined with the domain mismatch (cZone: animaldermatologypdx.com vs scanned domain: allamericansportsbar.com), this redirect manipulates the user's URL bar to point to content on a different domain's path. The JS redirect pattern flag in pre-scan context corroborates this finding. (location: page.html: history.replaceState call pointing to /yeast-skin-infection/ path)
brand impersonation
The page title is 'Just a moment...' with meta robots set to 'noindex,nofollow', which is the standard Cloudflare interstitial challenge page. However, because the cZone in the challenge config belongs to animaldermatologypdx.com (an animal dermatology clinic) while the URL is allamericansportsbar.com (a sports bar), users visiting the sports bar domain are being served infrastructure fingerprinted to an entirely different brand and business, which could be used to confuse or mislead users about which site they are visiting. (location: page.html: <title>Just a moment...</title> and cZone mismatch)
curl https://api.brin.sh/domain/allamericansportsbar.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
allamericansportsbar.com currently scores 66/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.