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
brand impersonation
The page at dataliberation.org renders a full replica of Google's CAPTCHA/bot-detection interstitial, including Google branding, Google reCAPTCHA enterprise widget, Google Terms of Service links, and Google support URLs. The page title is set to 'https://support.google.com/accounts/answer/3024190' and the hidden 'continue' field points to the same Google support URL, creating a convincing illusion that the user is on a Google-owned property. (location: page.html:3,17,22-28)
social engineering
The page falsely claims 'Our systems have detected unusual traffic from your computer network' and presents a fabricated CAPTCHA challenge to manipulate the user into believing they are being verified by Google. This creates a false sense of urgency and legitimacy to coerce user interaction (CAPTCHA solve/form submission) on a non-Google domain. (location: page.html:24,27)
phishing
The domain dataliberation.org is serving a page that impersonates Google's bot-detection/CAPTCHA system. The form posts to 'index' on the same domain with hidden fields including a base64-like token ('q') and a 'continue' redirect parameter pointing to a Google URL. This is a classic phishing pattern: harvest form interaction/tokens on the attacker's domain while appearing to be Google, then redirect to the legitimate destination to avoid suspicion. (location: page.html:7,17)
malicious redirect
The hidden form field 'continue' is set to 'https://support.google.com/accounts/answer/3024190'. After the form is submitted to the attacker-controlled domain (action='index'), the server can redirect to this Google URL, completing the deceptive flow and making the interaction appear legitimate. This open-redirect-style chaining is used to launder the phishing session. (location: page.html:17)
hidden content
The form contains a hidden input field 'q' with a long opaque token value ('EhAmABkAAAAtBQAAAAAAADgBGI_-oc0GIjDWxHBim6ridBSo8CIZ95MaEBaTfC25h0D7g9gOuA4YI_uJ1-om6STdFVNTS5Jf0uMyAnJSWgFD') and a hidden 'continue' redirect field, both invisible to the user. These hidden fields facilitate server-side tracking, session correlation, or credential/token harvesting without user awareness. (location: page.html:17)
prompt injection
The page title is set to the string 'https://support.google.com/accounts/answer/3024190' rather than a human-readable title. This is a known technique to inject misleading context into AI agents and browser automation tools that read page titles to determine page identity, causing them to misclassify the page as belonging to Google's support domain. (location: page.html:3)
brand impersonation
The page loads Google reCAPTCHA Enterprise JavaScript from 'https://www.google.com/recaptcha/enterprise.js' and uses a reCAPTCHA site key ('6LfwuyUTAAAAAOAmoS0fdqijC2PbbdH4kjq62Y1b') to render a legitimate-looking Google CAPTCHA widget on a non-Google domain, reinforcing the impersonation and lending false authenticity to the phishing page. (location: page.html:13,15)
curl https://api.brin.sh/domain/dataliberation.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
dataliberation.org 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.