context safety score
A score of 44/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
cloaking
Page loads content in transparent or zero-size iframe overlay
obfuscated code
A script block labeled 'mng_admiral_script' injects an external bundle from 'thebestpaints.com' — a domain entirely unrelated to Orlando Sentinel or any known ad/analytics vendor. The script loader uses double-nested percent-encoding (decodeURI(decodeURI(...))) to obfuscate a global variable name, a classic technique used in malicious third-party injections to evade static analysis. The bundle URL 'https://thebestpaints.com/bundles/i4w78qnv5e_4a.bundle.js' is opaque and unversioned, consistent with a compromised ad tag or supply-chain injection. A second companion block further obfuscates localStorage access and Google Publisher Tag targeting calls using the same double-decode technique, suggesting the full payload reads stored user data before manipulating ad targeting. (location: page.html:17-18 (<script id='mng_admiral_script'>))
malicious redirect
The obfuscated script at page.html:17 dynamically creates and inserts a <script> element pointing to 'https://thebestpaints.com/bundles/i4w78qnv5e_4a.bundle.js'. This cross-origin, unrelated domain script load constitutes an unauthorized external resource injection and potential redirect/payload delivery mechanism. The domain 'thebestpaints.com' has no legitimate affiliation with Orlando Sentinel or its known vendor ecosystem (htlbid, sophi, osano, parsely, etc.). (location: page.html:17 (A.src='https://thebestpaints.com/bundles/i4w78qnv5e_4a.bundle.js'))
hidden content
The second obfuscated block (line 18) uses double-percent-encoded strings to conceal localStorage method names and a Google Ad Manager key string ('_a'+decodeURI(...)). The encoded localStorage key resolves to a non-obvious identifier used to silently read stored session or targeting data. This pattern is consistent with hidden data exfiltration or session harvesting embedded within an ad tag, invisible to casual page inspection. (location: page.html:18 (<script id='mng_admiral_script'>, second IIFE block))
curl https://api.brin.sh/domain/orlandosentinel.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
orlandosentinel.com currently scores 44/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.