context safety score
A score of 39/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden instruction
high hidden content ratio detected in DOM
encoded payload
suspicious base64-like blobs detected in page content
malicious redirect
A geo-redirect script loads an external resource from g10102301085.co — a suspicious, non-standard TLD domain — at page load. It sets body opacity to 0 (hiding the page), calls out to this third-party with the referrer URL and current window URL, and conditionally delays restoring visibility by 5 seconds if a redirect is triggered. This is a classic cloaking/redirect injection pattern where users may be silently redirected based on geo or referrer conditions. (location: page.html:8-17 (inline <script> in <head>, src='https://g10102301085.co/gr?id=-O5HiBcdMtWi56ecnmu4'))
hidden content
The page initially sets body opacity to 0.0 via an injected style tag ('georedirect-O5HiBcdMtWi56ecnmu4style'), hiding all content from users until the geo-redirect script completes or times out after 8 seconds. This opacity cloaking technique is used to mask page content during redirect evaluation and can hide malicious content from scanners. (location: page.html:9-16 (body{opacity:0.0 !important} injected style, restored conditionally after redirect check))
hidden content
Multiple geo-targeted content spans use style='display:none' and are revealed only by the GeoTargetly script based on visitor location (content IDs for CA, NY, DE, ND, NE, RI, TN, SC, NM, SD). While used for legitimate geo-personalization on this site, the pattern of large hidden content blocks controlled by external geo-targeting scripts represents a hidden content vector that could be abused. (location: page.html:5771-5860 (geotargetlygeocontent spans with display:none))
obfuscated code
The geo-redirect script uses obfuscated single-letter variable names (g, e, o, id, t, a, r, ge, tl, y, s) in an IIFE, sends the visitor's referrer and current URL to an external domain (g10102301085.co), and conditionally triggers a redirect. The domain name itself (g10102301085.co) is a numeric-label .co domain with no clear legitimate owner, consistent with malicious redirect infrastructure. (location: page.html:8-17 (IIFE geo-redirect script in <head>))
curl https://api.brin.sh/domain/therapservices.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
therapservices.net currently scores 39/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.