context safety score
A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The scanned domain is tailtarget.com, but the page fully renders as 'Tail Digital' / 'TOTVS' brand content. The canonical URL, og:url, og:site_name, all images, scripts, and links point to tail.digital and totvs.com — not tailtarget.com. The page is serving the legitimate brand's content from a domain that is not the brand's own domain (tail.digital), which constitutes impersonation of the Tail/TOTVS brand via a lookalike or hijacked domain. (location: metadata.json:domain=tailtarget.com vs page.html:18 canonical href=https://tail.digital, og:url=https://tail.digital)
malicious redirect
The page hosted on tailtarget.com presents a LOGIN button that links directly to https://dashboard.tailtarget.com/login — a subdomain of the impersonating domain rather than the legitimate platform. Users believing they are on or linked from the real Tail/TOTVS site may submit credentials to this attacker-controlled login endpoint. (location: page.html:340 — href=https://dashboard.tailtarget.com/login)
credential harvesting
A login button on the impersonating domain tailtarget.com points to https://dashboard.tailtarget.com/login. This mirrors the legitimate Tail platform login flow but routes credentials to an attacker-controlled subdomain (tailtarget.com), enabling credential harvesting from users who believe they are accessing the real Tail/TOTVS dashboard. (location: page.html:340 — <a href='https://dashboard.tailtarget.com/login' class='btn btn__outline-white'>LOGIN</a>)
phishing
The entire page is a high-fidelity clone of the legitimate tail.digital / TOTVS brand site, served from the lookalike domain tailtarget.com. It reproduces logos, branding, content, HubSpot lead-capture forms (portalId 2287241), phone numbers, footer navigation, and social links — creating a convincing phishing site targeting Tail/TOTVS customers and prospects. (location: page.html — full page; domain tailtarget.com vs legitimate tail.digital)
credential harvesting
The page embeds a HubSpot lead capture form (portalId: 2287241, formId: 971ce355-5482-43d9-97e1-8bfb72b1b2d7) that collects email, job title, department, industry segment, and revenue range from visitors. On a lookalike/impersonating domain, this constitutes credential and PII harvesting under false pretenses. (location: page.html:134-231 — HubSpot form modal #contato)
social engineering
The page uses TOTVS/Tail branding, legitimate-looking contact numbers (0800 70 98 100, 4003-0015), and a call-to-action 'LIGAMOS PARA VOCÊ' (We'll call you) to build trust and solicit personal and business data from visitors on the impersonating domain tailtarget.com. (location: page.html:332-334, page.html:324-326 — CTA buttons and phone numbers in nav)
curl https://api.brin.sh/domain/tailtarget.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
tailtarget.com 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.