context safety score
A score of 74/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
brand impersonation
The page is served from cdn.minnesotamonthly.com but all content, scripts, stylesheets, AJAX endpoints, and internal links resolve to hourwp-p.innoscale.net and hourwp-s.innoscale.net. The page title is 'primary – Just another WordPress site' with no Minnesota Monthly branding. This CDN subdomain is hosting a completely unrelated WordPress installation under the Minnesota Monthly domain, which could be used to exploit trust in the minnesotamonthly.com domain. (location: page.html:1, page.html:479 — title, heateorFfcpWebsiteUrl, all resource URLs)
malicious redirect
The search form and all navigation links redirect users from cdn.minnesotamonthly.com to hourwp-p.innoscale.net. The off-domain form action (flagged in Tier 2 scan) is confirmed: the search widget submits to the innoscale.net backend rather than the serving domain. Users believing they are on Minnesota Monthly's CDN are silently sent to a third-party domain. (location: page.html:480-484 — search form action, page.html:485 — navigation links to hourwp-p.innoscale.net)
hidden content
The page sets 'noindex, nofollow' robots meta directives, intentionally preventing search engine indexing and crawling. Combined with the domain mismatch, this suggests the page is deliberately concealed from discovery while remaining accessible via direct URL. (location: page.html:1 — <meta name='robots' content='noindex, nofollow'>)
obfuscated code
The setREVStartSize JavaScript function uses heavily minified single-letter variable names and compressed logic (standard for RevSlider 6.0.7). The Tier 2 scan flagged JS obfuscation; this is consistent with minified third-party plugin code rather than purpose-built obfuscation, but warrants noting given the domain mismatch context. (location: page.html:478 — setREVStartSize inline script block)
curl https://api.brin.sh/domain/cdn.minnesotamonthly.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
cdn.minnesotamonthly.com currently scores 74/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.