context safety score
A score of 41/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
JavaScript immediately redirects all visitors via window.location.replace() to a tracking URL containing a unique UUID (tr_uuid=20260306-1149-42b8-a2df-02816b5adbfa) and a browser fingerprint. The redirect fires after 300ms or upon fingerprint collection, ensuring no visitor remains on the landing page. This is a classic cloaking/traffic distribution system (TDS) used to route victims to phishing or malware payloads while evading crawlers. (location: page.html:6-26)
malicious redirect
A <noscript> meta-refresh redirect is present targeting the same tracking URL with fp=-5, ensuring users without JavaScript are also silently redirected. This provides a fallback redirect mechanism for all browser environments. (location: page.html:33)
hidden content
A hidden anchor link (display:none) pointing to the same tracking URL with fp=-3 is embedded in the page body. This link is invisible to users but crawlable by bots and AI agents, and may be used to lure automated scanners into following the redirect chain. (location: page.html:32)
phishing
The domain 'portalfinan-faturas.digital' uses Portuguese-language financial terminology ('portal financeiro faturas' = financial invoice portal) to impersonate a legitimate financial or invoicing service. The combination of a deceptive domain name, immediate fingerprint-based redirection, and a non-blocklisted .digital TLD is consistent with a phishing TDS landing page designed to route victims to credential harvesting pages. (location: metadata.json:1, page.html:1-35)
brand impersonation
The domain name 'portalfinan-faturas.digital' mimics the naming conventions of legitimate Brazilian/Portuguese financial portals and invoice management systems (e.g., government or bank billing portals). The use of 'portal', 'finan' (financial), and 'faturas' (invoices) is designed to establish false legitimacy and trick users into trusting the site. (location: metadata.json (domain field))
social engineering
The only visible user-facing text is 'Click here to enter', a classic social engineering prompt designed to encourage user interaction and proceed through the redirect chain. Combined with the financial domain branding, this creates urgency and legitimacy cues targeting users expecting invoice or billing portals. (location: page-hidden.txt:1, page.html:32)
obfuscated code
A FingerprintJS library is loaded from a local path (/js/fingerprint/iife.min.js) and used to silently collect a unique browser fingerprint (visitorId) before redirecting. This fingerprint is appended to the tracking URL, enabling the operator to track individual users, differentiate real victims from security crawlers (fp=-7 for failures, fp=-3 for hidden link clicks, fp=-5 for noscript), and serve targeted payloads. This is covert user profiling infrastructure. (location: page.html:4, page.html:18-23)
curl https://api.brin.sh/domain/portalfinan-faturas.digitalCommon questions teams ask before deciding whether to use this domain in agent workflows.
portalfinan-faturas.digital currently scores 41/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.