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
brand impersonation
Domain 'samsungmdec.com' incorporates the 'samsung' trademark combined with 'mdec', impersonating the Samsung brand. This typosquat/compound domain pattern is commonly used to deceive users into believing they are interacting with an official Samsung property. (location: domain: samsungmdec.com)
phishing
The site failed TLS connection (connected=false, cert_valid=false), meaning no valid HTTPS is served despite using a domain that impersonates the Samsung brand. Legitimate brand sites maintain valid TLS; the absence suggests a deceptive or misconfigured site that may harvest credentials or redirect users insecurely. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
Combination of brand impersonation (samsung in domain) and failed TLS/no valid certificate increases risk that the site is used to collect credentials from users who believe they are on a legitimate Samsung portal. No page content was retrievable to confirm or deny a login form, but the domain pattern is consistent with credential harvesting infrastructure. (location: domain: samsungmdec.com; metadata.json: tls)
malicious redirect
The page returned empty HTML and no visible text content despite the domain being live (domain age 2822 days). An empty or blank page is a common indicator of a redirect gateway, cloaking, or a page that only renders content to targeted victims or specific user-agents, consistent with malicious redirect infrastructure. (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 is registered and aged. This absence of content combined with an active domain suggests cloaking: content may be served selectively to targeted users while appearing blank to scanners, a technique used to evade automated threat detection. (location: page.html (0 lines), page-text.txt (0 lines), page-hidden.txt (0 lines))
curl https://api.brin.sh/domain/samsungmdec.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
samsungmdec.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.