context safety score
A score of 48/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
brand impersonation
The page displays Criteo branding (criteo_logo.svg, criteo_favicon.png, custom-criteo.css) on a login form served from iponweb.net. Criteo acquired IPONWEB, but the combination of an external domain serving a login page with Criteo brand assets is a strong indicator of brand impersonation or at minimum a deceptive credential collection surface that could mislead users into believing they are authenticating with Criteo directly. (location: page.html:13,28,46 — favicon, CSS, and logo references to criteo assets)
credential harvesting
A login form with a username/email field posts credentials via HTTP POST to https://iam.iponweb.net/auth/realms/iponweb/login-actions/authenticate with a hardcoded session_code and client_id (jira.iponweb.net). The form collects usernames/emails and submits them to an identity endpoint. The session_code embedded in the action URL is static in this snapshot, which is consistent with a credential-harvesting page capturing submissions under a fixed session context. (location: page.html:63-71 — <form> action URL with embedded session_code)
phishing
The page is a login portal (title: 'Sign in to IPONWEB IAM') served at https://iponweb.net (the root domain) rather than a dedicated auth subdomain, combines Criteo branding with IPONWEB IAM labeling, includes meta robots noindex/nofollow to suppress search engine visibility, and presents a credential collection form. The noindex directive is a common tactic to avoid crawling/detection of phishing pages. The overall pattern — external branding, suppressed indexing, credential form — is consistent with a phishing page. (location: page.html:8 — meta robots noindex/nofollow; page.html:11 — title; page.html:63 — form action)
social engineering
The page header reads 'IPONWEB IAM' while displaying the Criteo logo, creating a dual-brand confusion that may cause users to lower their guard and enter credentials, believing the portal is a legitimate unified identity system. This mixed-brand presentation is a social engineering technique to exploit trust in the Criteo brand. (location: page.html:37,46 — kc-header-wrapper text 'IPONWEB IAM' alongside criteo_logo.svg)
curl https://api.brin.sh/domain/iponweb.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
iponweb.net currently scores 48/100 with a suspicious 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.