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 loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The site splashtop.eu is serving content that canonically belongs to www.splashtop.com. The HTML canonical tag, og:url, og:site_name, schema.org Organization, and all alternate hreflang links point exclusively to www.splashtop.com, while the actual serving domain is splashtop.eu — a different TLD not listed among the official alternate domains (which cover .com, .cn, and .com/tw). This pattern is consistent with a domain squatting or brand impersonation setup that mirrors the legitimate Splashtop site. (location: page.html: <link rel='canonical' href='https://www.splashtop.com'>, og:url, schema.org Organization @id)
malicious redirect
JavaScript on the page intercepts all anchor click events and appends cross-domain tracking parameters (ajs_aid, ajs_uid, optid) before navigation occurs. The function isCrossDomainNeeded always appends these params when linking to my.splashtop or redirect.splashtop. On an impersonating domain, this mechanism could be used to pass harvested user/session identifiers to attacker-controlled endpoints by substituting those target domains. (location: page.html lines 51-99 / page-text.txt lines 21-83: addCrossDomainParams, isCrossDomainNeeded functions)
social engineering
The splashtop.eu domain presents a pixel-perfect clone of the legitimate Splashtop homepage, including real brand logos, product descriptions, trust signals (Harvard logo, customer testimonials implied), and pricing CTAs. Users arriving at this .eu domain would have no visual indication they are not on the official site, making it highly effective for social engineering toward account creation or purchase. (location: page.html: full page content, metadata og:title, og:description, schema.org Organization)
curl https://api.brin.sh/domain/splashtop.euCommon questions teams ask before deciding whether to use this domain in agent workflows.
splashtop.eu 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.