context safety score
A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
brand impersonation
The domain 'hsforms.net' closely mimics 'hsforms.com', which is HubSpot's official form hosting domain. The .net TLD substitution is a classic typosquatting/brand impersonation technique designed to deceive users and AI agents into believing they are interacting with legitimate HubSpot infrastructure. (location: domain: hsforms.net)
phishing
The domain impersonates HubSpot's form service (hsforms.com) via TLD substitution (.net instead of .com). Combined with a failed TLS connection (connected=false, cert_valid=false), this pattern is consistent with a phishing or credential-harvesting site that may not yet be fully operational or has been taken down after use. (location: domain: hsforms.net, metadata.json tls block)
credential harvesting
Impersonation of HubSpot's form hosting infrastructure (hsforms.com → hsforms.net) is a known vector for credential harvesting. Fake HubSpot forms are routinely used to collect login credentials, marketing data, or personal information under the guise of a trusted brand. (location: domain: hsforms.net)
malicious redirect
The site returned no content (page.html and page-text.txt are empty) despite the domain being active (age: 15037 days). This blank-page pattern is commonly used in redirect chains where the domain serves as an intermediary hop, forwarding victims to a payload page without leaving visible content for scanners. (location: page.html (empty), page-text.txt (empty))
hidden content
All content files (page.html, page-text.txt, page-hidden.txt) are empty, yet the domain has been registered for over 41 years (15037 days). The absence of any content on an aged domain may indicate cloaking — serving content only to real browsers or targeted victims while returning blank pages to automated scanners and bots. (location: page.html, page-text.txt, page-hidden.txt (all empty))
curl https://api.brin.sh/domain/hsforms.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
hsforms.net 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.