context safety score
A score of 31/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
phishing
Domain 'securpass16-mobile.com' uses password-related terminology ('pass') combined with 'mobile' and a numeric suffix, a pattern consistent with phishing infrastructure mimicking a legitimate password or mobile banking service. (location: metadata.json: domain)
brand impersonation
The domain name 'securpass16-mobile.com' appears designed to impersonate a secure password or mobile authentication service. The combination of 'secur', 'pass', and 'mobile' is a common brand-spoofing pattern targeting users of password managers or mobile banking platforms. (location: metadata.json: domain)
credential harvesting
Domain construction ('securpass16-mobile.com') strongly suggests a credential harvesting site targeting users who may believe they are accessing a legitimate secure password or mobile login portal. TLS is not connected and certificate is invalid, which is inconsistent with a legitimate authentication service. (location: metadata.json: tls, domain)
hidden content
TLS connection failed (connected=false, cert_valid=false) on a domain named to suggest secure authentication. The page HTML and visible text are empty, which may indicate the site serves content conditionally (e.g., only to targeted victims, specific user agents, or after a redirect), concealing its true payload from automated scanners. (location: metadata.json: tls; page.html; page-text.txt)
malicious redirect
The combination of an empty page body, failed TLS, and a 16-day-old domain with a deceptive name is consistent with a redirect staging domain — used to funnel victims to a downstream credential harvesting or phishing page while evading automated detection. (location: metadata.json: domain, tls; page.html (empty))
curl https://api.brin.sh/domain/securpass16-mobile.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
securpass16-mobile.com currently scores 31/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.