context safety score
A score of 46/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
social engineering
The site explicitly encourages users to bypass workplace and government content filters ('Don't let your boss or government block you from your favorite sites'), normalizing circumvention of security controls and organizational policies. (location: page.html:278, page-text.txt:206)
malicious redirect
All social network links (YouTube, Facebook, Twitter, Reddit, Imgur, Google) route through an internal relay path '/go/<domain>' rather than linking directly to the destination. This intermediary redirect layer allows the proxy operator to intercept, log, or manipulate traffic to these third-party sites without user awareness. (location: page.html:173-194, page.html:331-352)
credential harvesting
The site operates as a web proxy that routes all user web traffic — including authenticated sessions — through its own servers. The URL submission form posts to '/includes/process.php' and the 'allowCookies' checkbox is enabled by default, meaning session cookies for any proxied site (including banking, email, social media) are transmitted through and potentially logged by the proxy operator. (location: page.html:203, page.html:260-263)
brand impersonation
The site prominently features and links to Facebook, YouTube, Twitter, Reddit, Google, and Imgur using their official brand icons and names to attract users, while actually routing that traffic through a third-party proxy infrastructure. This leverages brand trust of major platforms to encourage users to submit credentials and browse sensitive content through the proxy. (location: page.html:173-194, page.html:300-323)
hidden content
Several server option elements are hidden via 'display:none' style (id='additionalServers'), containing a large list of proxy server endpoints (us1-us20, eu1-eu20) that are not visible to users in the default UI but are injected into the DOM and activated via JavaScript on user interaction. (location: page.html:205, page.html:205-256)
curl https://api.brin.sh/domain/proxysite.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
proxysite.com currently scores 46/100 with a suspicious verdict and medium 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.