context safety score
A score of 45/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The page at startribune.com is serving a Vercel Security Checkpoint interstitial page instead of the legitimate Star Tribune news website. The page title, footer, and visible content all reference 'Vercel Security Checkpoint' — a third-party infrastructure brand — while the URL belongs to startribune.com. This misrepresents the identity of the serving entity to the end user and to any AI agent browsing the site. (location: page.html:<title>, page-text.txt:footer)
obfuscated code
The page contains heavily obfuscated JavaScript using numeric array indexing, shuffled string lookup tables, self-invoking decode loops (parseInt arithmetic integrity checks), and anti-debugging patterns (C() call with toString/search regex fingerprinting). The obfuscation pattern is consistent with bot-detection evasion or malicious payload delivery disguised as a browser challenge script. (location: page.html:line 2 (<script type="module">))
prompt injection
The page-text.txt file contains raw HTML markup injected directly into the visible text output, including full SVG spinner markup and noscript fallback elements. An AI agent parsing page-text.txt as plain text would ingest HTML tags and structured markup that could confuse its text understanding pipeline or be leveraged to inject instructions if crafted maliciously. (location: page-text.txt:line 1)
malicious redirect
The legitimate target domain startribune.com (domain age 11738 days, well-established) is serving a Vercel interstitial checkpoint page rather than its actual content. This indicates the real site content is gated or intercepted, and users/agents are being redirected through a third-party security layer (Vercel) that controls what content is ultimately delivered. The fix link points to https://vercel.link/security-checkpoint, an external domain. (location: page.html:line 3, <a href="https://vercel.link/security-checkpoint">)
social engineering
The interstitial uses urgency and authority cues ('We're verifying your browser', 'Vercel Security Checkpoint') to condition users into trusting the checkpoint and potentially enabling JavaScript or completing challenges, which is a standard social engineering pattern used in fake CAPTCHA and browser-locker attacks to coerce user action. (location: page-text.txt:line 1, page.html:line 3 #header-text)
curl https://api.brin.sh/domain/startribune.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
startribune.com currently scores 45/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.