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 blogspot.pt renders a Google CAPTCHA/security-check page with the <title> set to 'https://www.google.com/' and content mimicking Google's 'unusual traffic' interstitial. The domain blogspot.pt is not owned by Google, yet the page fully impersonates Google's security checkpoint UI, including Google reCAPTCHA enterprise widget, Google Terms of Service links, and Google-branded messaging. (location: page.html:3-34, title tag and body content)
malicious redirect
The hidden form field 'continue' is set to 'https://www.google.com/' and the form action is 'index' (a relative path on blogspot.pt). Upon CAPTCHA completion, the submitCallback auto-submits the form to blogspot.pt/index — a non-Google domain — before any redirect to Google occurs. This intercepts the user flow through an attacker-controlled endpoint under the guise of a Google verification step. (location: page.html:17, hidden input name='continue' and form action='index')
credential harvesting
The form POSTs to a relative 'index' endpoint on blogspot.pt with a hidden token field ('q') containing an opaque base64-like value. Combined with the fake Google CAPTCHA flow, this pattern is consistent with harvesting session tokens or credentials submitted by users who believe they are interacting with a legitimate Google verification page. (location: page.html:7,17, form id='captcha-form' action='index' and hidden input name='q')
phishing
blogspot.pt hosts a page that fully impersonates Google's CAPTCHA security interstitial — including Google branding, Google reCAPTCHA enterprise script, Google policy links, and a fabricated IP/timestamp display — to deceive users into believing they are on a Google-controlled page. The domain is not affiliated with Google. This is a classic phishing lure designed to establish trust before harvesting data or redirecting victims. (location: page.html:1-35)
social engineering
The page displays a fabricated IP address (2600:1900:0:2d07::1c00) and timestamp (2026-03-04T18:13:51Z) attributed to the visitor's session, creating false urgency and legitimacy to pressure users into completing the CAPTCHA and submitting the form. Displaying a specific IP address personalizes the deception and increases compliance. (location: page.html:30, IP address and Time display)
prompt injection
The page includes an inline onload handler: 'if(solveSimpleChallenge) {solveSimpleChallenge(0,0);}' which attempts to invoke a function named 'solveSimpleChallenge'. This pattern targets AI agents or automated browsing environments that may expose such a global function, instructing them to auto-solve the challenge and submit the form without user interaction — bypassing intended human verification. (location: page.html:4, body onload attribute: solveSimpleChallenge(0,0))
curl https://api.brin.sh/domain/blogspot.ptCommon questions teams ask before deciding whether to use this domain in agent workflows.
blogspot.pt 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.