context safety score
A score of 32/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 kettledroopingcontinuation.com mimics Google's CAPTCHA/reCAPTCHA interstitial page verbatim, including Google branding, Google's Terms of Service language, and a fake 'About this page' explanation identical to Google's genuine bot-detection page. The page title is set to 'https://google.com/' to reinforce the impersonation. (location: page.html:3 — <title>https://google.com/</title>; page.html:22-28 — 'About this page' block with copied Google language)
phishing
A non-Google domain (kettledroopingcontinuation.com) serves a page that impersonates Google's CAPTCHA challenge. The CAPTCHA form POSTs to 'index' on the same malicious domain, allowing the operator to harvest the reCAPTCHA token response and any other submitted data from victims who believe they are interacting with Google infrastructure. (location: page.html:7 — <form id='captcha-form' action='index' method='post'>)
malicious redirect
A hidden form field named 'continue' is set to 'https://google.com/', creating a fake post-CAPTCHA redirect to Google. This classic redirect pattern is used in phishing flows to reassure victims after credential or token harvesting, making the attack less detectable. (location: page.html:17 — <input type='hidden' name='continue' value='https://google.com/'>)
social engineering
The page replicates Google's authority language ('Our systems have detected unusual traffic', 'violation of the Terms of Service', 'solving the above CAPTCHA will let you continue') to pressure users into submitting the CAPTCHA form on a third-party malicious domain, exploiting trust in Google to bypass user skepticism. (location: page.html:24-27; page-text.txt:21-24)
hidden content
A hidden form field 'q' contains a long opaque base64-like token value. This encoded blob is submitted silently with the form POST and likely serves as a session tracking or victim fingerprinting token for the attacker's backend, concealed from the user. (location: page.html:17 — <input type='hidden' name='q' value='EhAmABkAAAAtBwAAAAAAABwAGNaBoc0GIimY36KIUzByt1fSSlATko2L1JquULyDR-PCaW9e9gFDphvIjVhvLkcDfzICclJaAUM'>)
prompt injection
The page body uses an onload handler that calls 'solveSimpleChallenge(0,0)' if the function exists. This is a known technique to auto-solve or bypass CAPTCHA challenges programmatically, and also functions as a prompt/instruction injected into the page execution context targeting automated agents or headless browsers that may process or relay the page content. (location: page.html:4 — onload='...if(solveSimpleChallenge) {solveSimpleChallenge(0,0);}')
curl https://api.brin.sh/domain/kettledroopingcontinuation.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
kettledroopingcontinuation.com currently scores 32/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.