context safety score
A score of 68/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
brand impersonation
The domain 'cartersonpublicsafety.com' presents itself as a public safety organization in its domain name, but operates as a Thai-language online gaming/casino content site. The meta description is entirely in Thai and promotes online games, while the domain name implies a legitimate public safety authority. This mismatch is a classic brand/identity deception pattern used to exploit trust in official-sounding domains. (location: page.html:13 - meta description; domain name cartersonpublicsafety.com)
social engineering
The site hosts a 'Guides' article explicitly titled 'คู่มือเลือกคาสิโนออนไลน์ในสหรัฐ 2026 แบบปลอดภัย' (Guide to Choosing Online Casinos in the USA 2026 Safely), linking to '/online-casinos-usa-2026-guide/'. Hosting gambling referral/affiliate content on a domain named 'public safety' is a deliberate social engineering tactic to lend false legitimacy to gambling promotions, potentially targeting users who trust the domain's authoritative name. (location: page.html:518-519; page-text.txt:342)
obfuscated code
The page contains minified/obfuscated JavaScript implementing custom base64 encode/decode functions (b2a, a2b, b64e, b64d) and uses them throughout ad insertion logic (ai_check_and_insert_block, ai_process_rotation) to encode/decode block data and tracking attributes at runtime. While these are from the 'Ad Inserter' WordPress plugin, the pattern of encoding ad content and decoding it at runtime constitutes obfuscated code execution that conceals the actual ad/content being injected. (location: page-text.txt:964-966; page.html (script blocks with b64d/b64e calls))
hidden content
The page uses JavaScript-driven lazy content injection via the Ad Inserter plugin's ai_check_and_insert_block and ai_process_rotation functions, which decode and insert content from base64-encoded data-attributes at runtime. This means the actual injected content is not visible in the static HTML and would only appear after JS execution, potentially hiding ad content or redirects from static scanners. The pre-scan context flagged 12 suspicious base64 blobs consistent with this. (location: page-text.txt:989-991; .brin-context.md: suspicious base64 blobs: 12)
curl https://api.brin.sh/domain/cartersonpublicsafety.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
cartersonpublicsafety.com currently scores 68/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.