context safety score
A score of 45/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
brand impersonation
The page is served from formstack.com but the footer copyright reads '© 2026 Intellistack, LLC. All rights reserved.' while also showing 'Copyright © 2020 Formstack'. The notification banner links to 'https://www.intellistack.com/platform/clm' — a different domain (intellistack.com) — suggesting the site may be rebranding under or operated by a different entity without clear disclosure, creating potential for user confusion and brand impersonation between Formstack and Intellistack. (location: page-text.txt line 111, page.html line 361 (notification banner href))
malicious redirect
The notification banner at the top of the formstack.com homepage contains a link pointing to 'https://www.intellistack.com/platform/clm', an entirely different domain (intellistack.com). Users clicking 'Learn about CLM' are silently redirected off the scanned domain to a third-party site without explicit disclosure. (location: page.html line 361: href="https://www.intellistack.com/platform/clm")
hidden content
The Intellimize A/B testing script applies an 'anti-flicker' CSS class that sets document opacity to 0 for up to 4000ms, temporarily hiding all page content while remote personalization scripts load from cdn.intellimize.co. Additionally, the localStorage opt-out logic for Intellimize is immediately overridden by code that sets tracking type back to 'optOut' in a confusing pattern. While likely a legitimate CRO tool, the content-hiding mechanism can be abused and reduces transparency. (location: page.html lines 2-3: anti-flicker class + intellimize localStorage manipulation)
hidden content
A dataLayer push fires a 'formSubmission' event with formType 'Contact us' on every page load, not just on actual form submissions. This sends false form submission telemetry to Google Tag Manager unconditionally, misrepresenting user behavior in analytics pipelines. (location: page.html lines 39-47: dataLayer.push formSubmission on page load)
curl https://api.brin.sh/domain/formstack.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
formstack.com currently scores 45/100 with a suspicious verdict and medium 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.