context safety score
A score of 46/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 shemzaapp.com is only 96 days old. Newly registered domains are frequently used for phishing campaigns before they are flagged by blocklists. The domain is not yet blocklisted, consistent with an early-stage or newly activated phishing infrastructure. (location: metadata.json: whois.domain_age_days=96, blocklist.listed=false)
phishing
TLS connection to shemzaapp.com failed entirely (connected=false, cert_valid=false). A site that cannot establish a valid TLS session is either misconfigured, serving no real content, or acting as a redirect/cloaking layer. Legitimate sites at this age would have valid TLS. This is consistent with a parked or pre-activation phishing domain. (location: metadata.json: tls.connected=false, tls.cert_valid=false, tls.san_match=false)
brand impersonation
The domain name 'shemzaapp.com' follows the pattern of appending 'app' to a brand-like name ('shemza'), a common technique used to impersonate a mobile application or brand. The hosting reputation is unknown, further suggesting a newly stood-up infrastructure not associated with any legitimate established service. (location: metadata.json: domain=shemzaapp.com, hosting.reputation=Unknown)
hidden content
The context file references a page-hidden.txt file for extracted hidden content, but both page.html and page-hidden.txt are empty. This may indicate cloaking behavior: the server returned no content to the scanning crawler while serving malicious content to real browser user-agents or targeted victims. (location: page.html (empty), page-hidden.txt (empty), page-text.txt (empty))
curl https://api.brin.sh/domain/shemzaapp.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
shemzaapp.com currently scores 46/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.