context safety score
A score of 40/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
cloaking
Page conditionally redirects based on referrer or user-agent
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The page is served from domain polyspeak.ai but presents itself entirely as 'Polybuzz' (polybuzz.ai), including og:url pointing to https://www.polybuzz.ai/, canonical link to https://www.polybuzz.ai/, and all alternate hreflang links pointing to polybuzz.ai. The scanned domain (polyspeak.ai) is not the canonical brand domain, indicating the site is operating under a different domain than the brand it impersonates or is a mirror/clone of polybuzz.ai served from polyspeak.ai. (location: page.html lines 9, 72, 73-88, 89; metadata.json domain=polyspeak.ai)
malicious redirect
The page title and meta tags declare the site as Polybuzz at polybuzz.ai, while the actual serving domain is polyspeak.ai. All canonical and hreflang SEO signals point to polybuzz.ai, meaning traffic arriving at polyspeak.ai is being directed through a domain mismatch that could intercept users intending to reach polybuzz.ai. (location: page.html line 89 (canonical), lines 73-88 (hreflang alternates), metadata domain polyspeak.ai)
obfuscated code
The page's first inline script (line 1) contains a heavily minified and obfuscated MD5-like hash function (getGlobalI) with no clear declared purpose in the visible page logic. The code uses bitwise operations and array manipulation typical of fingerprinting or token generation routines that are intentionally obscured from inspection. (location: page.html line 1 (getGlobalI function, first <script> block))
hidden content
A <section class='page-title'> block containing h1/h2/h3 headings is styled with 'display:none' (CSS rule '.page-title{display:none}'). This SEO-stuffed hidden section contains keyword-rich headings such as 'Talk to AI', 'AI Girlfriend or Boyfriend', etc., invisible to users but readable by crawlers and AI agents. (location: page.html line 29 (CSS .page-title{display:none}), line 91 (<section class='page-title'>))
hidden content
Console logging is globally suppressed via 'window.console.log = () => {}' injected on page load, which prevents developers and security analysts from inspecting runtime behavior through browser console output. (location: page.html line 64 (!function(){window.console.log = () => {}}()))
curl https://api.brin.sh/domain/polyspeak.aiCommon questions teams ask before deciding whether to use this domain in agent workflows.
polyspeak.ai currently scores 40/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.