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
credential harvesting
credential form posts to an off-domain endpoint (may be legitimate SSO/OAuth)
phishing
1 deceptive links where visible host does not match destination host
js obfuscation
Obfuscated document.write with encoded content
obfuscated code
Post Affiliate Pro tracker script is injected via document.write with URL-encoded (unescape) obfuscation: unescape("%3Cscript id='pap_x2s6df8d' src='...tripod.postaffiliatepro.com/scripts/trackjs.js'..."). Using unescape() with percent-encoded HTML to dynamically inject a third-party script is a classic obfuscation pattern that evades static analysis. (location: page.html:435-436)
malicious redirect
ICANN Registrant Rights footer link points to 'promo-manager.server-secure.com' — a domain unrelated to ICANN or Lycos. The domain name 'server-secure.com' is a generic hosting domain used to disguise the true destination of this link, which appears to be a third-party promotional redirect rather than an official ICANN resource. (location: page.html:343)
hidden content
Login box is rendered with class 'hide' (display:none), making a credential-capture form (username + password fields POSTing to /bin/membership/login) invisible in the default page view. While this is a common UX pattern (revealed on click), it constitutes a hidden form that automated scanners and users may not notice. (location: page.html:45-74)
social engineering
The freeBox iframe loads content dynamically via a data-src attribute pointing to '/bin/membership/pref_link?to=buy&m_DL_USA_Tripod_Free=1&view=iframe'. The iframe starts with src='about:blank' and content is injected via JavaScript, obscuring what is loaded. This pattern can be used to present deceptive upsell or data-collection content without it being visible in static analysis. (location: page.html:121)
curl https://api.brin.sh/domain/tripod.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
tripod.com 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.