context safety score
A score of 31/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The scanned domain is jwplayer.com, but the entire page presents itself as 'JWX' (jwx.com). The HTML title, canonical URL, schema.org Organization, all navigation links, logo, and meta tags reference jwx.com — not jwplayer.com. An AI agent or user browsing jwplayer.com would be shown content belonging to a different brand identity (JWX/jwx.com), which constitutes cross-domain brand confusion and potential impersonation of the legacy JW Player brand. (location: page.html:3 (title tag), page.html:492 (canonical href=https://jwx.com), page.html:82-102 (schema.org Organization name='JWX', url='https://jwx.com'))
malicious redirect
The scanned URL is jwplayer.com but all internal navigation, CTAs, logo links, and canonical references redirect to jwx.com. The favicon is also loaded from jwx.com. A visitor to jwplayer.com is silently redirected into an entirely different domain's content ecosystem without clear disclosure. (location: page.html:4 (favicon from jwx.com), page.html:492 (canonical jwx.com), page.html:672 (logo href //www.jwx.com), page.html:107 (stylesheet from jwx.com))
malicious redirect
A 'See all news' call-to-action button links to https://jwpconnatix.com/news-room — a third domain distinct from both the scanned domain (jwplayer.com) and the displayed brand domain (jwx.com). Users clicking this link are sent to an unannounced third-party domain. (location: page.html:1323 (href=https://jwpconnatix.com/news-room))
hidden content
Multiple page sections are present in the DOM but hidden via CSS 'display:none' rules applied through '-hidden' class overrides (dnd_area-row-2-hidden, dnd_area-row-5-hidden, dnd_area-row-7-hidden, dnd_area-row-10-hidden, dnd_area-row-12-hidden, dnd_area-row-13-hidden, dnd_area-row-15-hidden, dnd_area-row-16-hidden, dnd_area-row-17-hidden). These sections contain full content blocks, CTAs, and one links to an external third-party HubSpot theme site (maka-agency-4740449.hs-sites.com). (location: page.html:327-470 (CSS hidden row definitions), page.html:1716 (hidden CTA linking to maka-agency-4740449.hs-sites.com))
social engineering
The testimonials section displays placeholder quotes from Gene Cernan (Apollo astronaut) and David Attenborough (naturalist) — neither has any affiliation with video technology. These appear to be unpopulated HubSpot theme template placeholders used as fake social proof, which could mislead users into believing notable public figures endorse the product. (location: page.html:1521-1535 (Gene Cernan and David Attenborough testimonial slides))
hidden content
A hidden CTA section (dnd_area-row-17-hidden, display:none) contains a button labeled 'Lift off now!' linking to https://ecosystem.hubspot.com/marketplace/website/power-theme-by-maka-agency — an external HubSpot marketplace page for a third-party theme. This is invisible to users but present in DOM and could be activated or scraped by automated agents. (location: page.html:1699-1725 (dnd_area-row-17-hidden section, href=https://ecosystem.hubspot.com/marketplace/website/power-theme-by-maka-agency))
curl https://api.brin.sh/domain/jwplayer.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
jwplayer.com currently scores 31/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.