context safety score
A score of 24/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 hosted on vsb55.com (a 225-day-old unrelated domain) renders a near-perfect replica of Google's CAPTCHA/unusual-traffic interstitial page, including Google branding, Google policy links, and Google support links. The page title is set to 'https://google.com/' and all visible text mimics official Google infrastructure pages to deceive users into believing they are interacting with Google systems. (location: page.html:3, page.html:22-28)
phishing
The site impersonates a Google CAPTCHA verification page on a non-Google domain (vsb55.com). The form posts to 'index' with hidden fields including a 'continue' parameter set to 'https://google.com/', creating a convincing phishing flow that captures CAPTCHA completions and form submissions from users who believe they are on a Google property. (location: page.html:7, page.html:17)
malicious redirect
A hidden form field 'continue' is set to 'https://google.com/', which will redirect the user to Google after form submission. This is a classic post-phishing redirect to mask the malicious interception — the user is sent to a legitimate site after credentials or CAPTCHA tokens are harvested, reducing suspicion. (location: page.html:17)
credential harvesting
The form contains a hidden input field 'q' with a long opaque base64/encoded token value and a hidden 'continue' field. The form POSTs to 'index' on vsb55.com, meaning any CAPTCHA token, session data, or user interaction data is submitted to the attacker-controlled server before any redirect occurs. This is consistent with harvesting Google reCAPTCHA enterprise tokens or session identifiers. (location: page.html:17)
social engineering
The page uses authoritative, fear-inducing language ('Our systems have detected unusual traffic from your computer network') copied verbatim from Google's own error pages. This social engineering technique pressures users into completing the CAPTCHA form on the attacker's domain, lending false legitimacy to the interaction and lowering user suspicion. (location: page.html:24, page-text.txt:21-24)
hidden content
An 'infoDiv' element is present with style 'display:none' and is only revealed on user click. It contains additional Google-impersonating text and links to google.com policy and support pages. This hidden content reinforces the brand impersonation and is not visible on initial page load. (location: page.html:26-28)
curl https://api.brin.sh/domain/vsb55.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
vsb55.com currently scores 24/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.