context safety score
A score of 34/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
The domain wbinsights.com is serving a full replica of the Atlassian login page ('Log in with Atlassian account'), including Atlassian branding, logo, favicon, and meta description ('Log in to Jira, Confluence, and all other Atlassian Cloud products here'). This is not an Atlassian-owned domain, making this a clear brand impersonation of Atlassian. (location: page.html <title>, <meta name='description'>, <h1 class='logo'>Atlassian</h1>)
phishing
The site wbinsights.com presents a spoofed Atlassian authentication page designed to collect Atlassian account credentials from victims who believe they are logging into a legitimate Atlassian service. The page replicates the Atlassian login UI and loads assets from id-frontend.prod-east.frontend.public.atl-paas.net to appear authentic. (location: page.html — full page structure, <title>Log in with Atlassian account</title>)
credential harvesting
The page is a replica of the Atlassian identity login portal (id.atlassian.com). Any credentials entered by users will be submitted to or intercepted by the operators of wbinsights.com rather than Atlassian. The login form assets are loaded from the legitimate Atlassian CDN to increase believability while the hosting domain is unaffiliated with Atlassian. (location: page.html — login form served at wbinsights.com impersonating id.atlassian.com)
malicious redirect
All functional JavaScript and CSS assets are loaded from id-frontend.prod-east.frontend.public.atl-paas.net (legitimate Atlassian CDN), which means the actual login form logic, including form submission targets, is dynamically injected. This allows the operator to proxy or redirect credential submissions without static evidence in the HTML shell. (location: page.html — <script src='https://id-frontend.prod-east.frontend.public.atl-paas.net/assets/index.6a475d87.js'>, <script src='...index.b093a1c3.js'>)
hidden content
The CSP nonce placeholder '{{csp_nonce}}' and app-state placeholder '{{data_app_state}}' are unrendered template variables present in the served HTML, indicating this is a server-side template that may conditionally inject or modify content at runtime. The grecaptcha badge is explicitly hidden via CSS ('visibility:hidden'), concealing reCAPTCHA activity from users. (location: page.html — style nonce='{{csp_nonce}}', body data-app-state='{{data_app_state}}', .grecaptcha-badge{visibility:hidden})
curl https://api.brin.sh/domain/wbinsights.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
wbinsights.com currently scores 34/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.