context safety score
A score of 44/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
Login page at imssms.org collects username and password credentials via a form posting to 'signin' endpoint. The domain 'imssms.org' is not an established brand and the page presents a generic login interface claiming 'Accounts are free and always will be.' — a social engineering lure to attract users. No clear legitimate organizational identity is established. (location: page.html:505-526, form action='signin' with username and password fields)
credential harvesting
The login form submits username and password via HTTP POST to a relative 'signin' endpoint. A hidden field 'etkk' with base64-encoded value 'aI9sYFk=' is included in the form submission. This hidden token alongside credential collection on an unverified third-party domain is a strong indicator of credential harvesting infrastructure. (location: page.html:505-526, input name='etkk' value='aI9sYFk=' (hidden field))
hidden content
A hidden form field named 'etkk' with base64-encoded value 'aI9sYFk=' is embedded in the login form. This field is not visible to users and is silently submitted with credentials. Its purpose is opaque and consistent with session tracking tokens used in phishing kits to correlate harvested credentials with campaigns. (location: page.html:506, <input type='hidden' name='etkk' value='aI9sYFk=')
social engineering
The page displays the message 'Accounts are free and always will be.' prominently in red text to entice users to register or log in. This persuasive framing, combined with an unverified domain and no visible organizational branding, is a social engineering tactic to lower user suspicion and encourage credential submission. (location: page.html:492, <h2 style='color:#ef4848; font-size:26px;'>Accounts are free and always will be.</h2>)
brand impersonation
The page uses the name 'IMS SMS' in the title and displays logo images (logo.png, logo-white.png) without any clearly identifiable legitimate brand affiliation. The domain imssms.org has no established public identity, and the professional UI template (Bootstrap-based admin dashboard theme) is used to lend false legitimacy, potentially impersonating an enterprise SMS or messaging platform. (location: page.html:10 (<title>IMS SMS | Login</title>), page.html:494-498 (logo images))
curl https://api.brin.sh/domain/imssms.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
imssms.org currently scores 44/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.