context safety score
A score of 28/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
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
Two obfuscated scripts load external JavaScript from suspicious domains 'g9904216750.co' and 'g10696554090.co' using the 'Geo Targetly' geo-blocking service. These scripts pass the visitor's referrer URL and current window URL as parameters to unknown third-party endpoints, enabling covert tracking or conditional redirects based on visitor geography. The domains use numeric-prefix .co TLDs inconsistent with legitimate ad platforms and have no transparency about payload behavior. (location: page.html lines 10-24, <head> section)
hidden content
The page's Webflow data-wf-domain attribute is set to 'www.tanda.com.au' while the scanned URL is 'tanda.co'. This mismatch between the canonical Webflow project domain and the serving domain could indicate the site is a clone or proxy of the legitimate tanda.com.au site, potentially used to intercept traffic intended for the real domain. (location: page.html line 1, <html> tag data-wf-domain attribute)
obfuscated code
Two inline scripts use an obfuscated IIFE pattern with single-character variable names (g,e,o,t,a,r,ge,tl,y and g,e,o,t,a,r,ge,tl,y,s) to dynamically inject script tags pointing to external numeric-subdomain .co domains. The variable naming and structure is designed to obscure the script's purpose and destination, which is a common obfuscation technique used to hide malicious or tracking payloads from static analysis. (location: page.html lines 10-24)
curl https://api.brin.sh/domain/tanda.coCommon questions teams ask before deciding whether to use this domain in agent workflows.
tanda.co currently scores 28/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.