context safety score
A score of 36/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
cloaking
Page loads content in transparent or zero-size iframe overlay
brand impersonation
The scanned URL is privacymanager.io, but the page fully renders as the LiveRamp corporate homepage (liveramp.com). The HTML declares data-wf-domain="liveramp.com", the title is "LiveRamp: The Data Collaboration Platform of Choice", all branding, logos, and content belong to LiveRamp, and hreflang alternate links point to liveramp.com, liveramp.uk, liveramp.fr, and liveramp.co.jp. A separate domain (privacymanager.io) is serving a complete clone or proxy of the official LiveRamp website, constituting brand impersonation. (location: page.html line 1: data-wf-domain="liveramp.com"; <title>LiveRamp: The Data Collaboration Platform of Choice</title>)
malicious redirect
The domain privacymanager.io silently delivers the full LiveRamp homepage content without any visible redirect or canonical disclosure to the visitor. Users and AI agents browsing privacymanager.io are presented with LiveRamp content hosted on a third-party domain, which can be used to intercept traffic, harvest consent signals, or proxy sessions intended for the legitimate liveramp.com domain. (location: metadata.json: url=https://privacymanager.io; page.html line 1: canonical brand content served from non-liveramp.com domain)
hidden content
A third-party JavaScript file is loaded from middleware.rampedup.us (https://middleware.rampedup.us/ru2026-middleware/privacy-manager/ketch-main-logic.js), a domain unrelated to LiveRamp's official CDN or known vendor list. This script is injected under the comment 'ketch app' and executes before page rendering. Its actual contents are not included in the scanned files and cannot be verified. The domain name 'rampedup.us' is associated with the RampUp conference mentioned on the page, but running middleware JS from a .us subdomain separate from liveramp.com introduces an unauditable code execution surface. (location: page.html line 4: <script src="https://middleware.rampedup.us/ru2026-middleware/privacy-manager/ketch-main-logic.js" async>)
prompt injection
The page explicitly markets 'Agentic AI Orchestration' capabilities and includes promotional copy stating 'Power more intelligent AI with robust first, second, and third-party signals' and 'Connect your most valuable data and signals across identifiers, platforms, clouds, and agents'. While this is marketing language, the page is designed to be discovered and acted upon by AI agents conducting research or procurement tasks. Serving this content from privacymanager.io (rather than liveramp.com) means an AI agent browsing this URL would attribute LiveRamp's authoritative claims to the privacymanager.io domain, potentially poisoning agent knowledge or causing agents to trust and interact with the wrong domain. (location: page-text.txt line 54: 'Help AI agents act smarter'; line 46: 'Agentic AI Orchestration')
social engineering
The page hosted on privacymanager.io presents itself as a privacy management resource (implied by the domain name) but actually delivers commercial marketing content for LiveRamp's data monetization and advertising targeting platform. Users expecting a neutral privacy management tool are instead exposed to persuasive content encouraging them to share data, 'talk to an expert', and engage with a data collaboration network. The domain name creates a false expectation of a privacy-protective service. (location: metadata.json: domain=privacymanager.io; page-text.txt line 48: 'Talk to an expert', line 591: 'Unlock exponential value with data collaboration')
curl https://api.brin.sh/domain/privacymanager.ioCommon questions teams ask before deciding whether to use this domain in agent workflows.
privacymanager.io currently scores 36/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.