context safety score
A score of 43/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 page is served from connatix.com (per metadata.json and .brin-context.md) but presents entirely as 'JWX' (jwx.com), with the canonical URL, all links, logos, og:url, and schema.org identity set to jwx.com. The favicon references jwx.com, the title and meta description are for JWX, and the page declares itself as jwx.com in structured data. A visitor or AI agent reaching this page via connatix.com would be presented with the full JWX brand identity without any indication the serving domain is connatix.com. This is consistent with a domain used as a redirect/serving layer for a rebranded entity, but presents a domain-identity mismatch that could be leveraged for brand impersonation. (location: page.html:3-5, metadata.json, .brin-context.md (url: https://connatix.com vs canonical: https://jwx.com))
hidden content
Multiple page sections are marked with CSS classes and inline styles forcing display:none, including 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-15-hidden, dnd_area-row-16-hidden, dnd_area-row-17-hidden, and several module-level hidden classes. Some of these hidden rows contain content (e.g., a CTA section with 'PROMOTE YOUR PRODUCTS AND SERVICES', a blog post section with an external link to maka-agency-4740449.hs-sites.com, and a testimonials section with generic placeholder quotes from Gene Cernan and David Attenborough). While these appear to be CMS template artifacts or A/B test variants, the volume of hidden sections warrants flagging. (location: page.html:327-470, rows dnd_area-row-2, dnd_area-row-5, dnd_area-row-7, dnd_area-row-10, dnd_area-row-12, dnd_area-row-15-17)
malicious redirect
The page is canonically hosted at jwx.com but is being scanned from connatix.com. The Login menu contains a link to 'Portal' at https://portal.connatix.com/login, directing users to a login page on a different domain (connatix.com). Additionally, a hidden section contains a CTA button linking to an external third-party HubSpot marketplace site: https://maka-agency-4740449.hs-sites.com/en/power-theme-blog-3-col. While the connatix.com portal link is likely legitimate (historical brand), the combination of serving from connatix.com while directing to jwx.com resources and back creates cross-domain trust confusion. (location: page.html:644 (portal.connatix.com/login), page.html:1572 (maka-agency link in hidden section))
social engineering
The testimonials section (hidden, dnd_area-row-15) displays quotes attributed to Gene Cernan (Astronaut) and David Attenborough (Natural Historian) — notable public figures with no apparent connection to JWX or the video technology industry. Using unrelated celebrity authority figures as testimonials is a social engineering technique to build false credibility. The quotes are generic and do not reference the company or its products. (location: page.html:1521-1535, page-text.txt:950-963)
curl https://api.brin.sh/domain/connatix.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
connatix.com currently scores 43/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.