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 'samsunghrm.com' incorporates the 'samsung' brand name — a globally recognized electronics and consumer goods company — combined with 'hrm' (Human Resource Management). This pattern is consistent with brand impersonation targeting Samsung employees or job seekers, potentially to harvest credentials or conduct spear-phishing under the guise of an official Samsung HR portal. (location: metadata.json: domain=samsunghrm.com)
phishing
The domain samsunghrm.com mimics a Samsung HR management portal. Combined with a failed TLS connection (connected=false, cert_valid=false), the site may be used to lure Samsung employees or job applicants into submitting credentials or personal information to a fraudulent HR system. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
An HRM (Human Resource Management) themed site impersonating Samsung is a high-risk vector for credential harvesting. Employees directed to this domain may be tricked into entering corporate login credentials, personally identifiable information, or payroll/benefits data. (location: metadata.json: domain=samsunghrm.com)
social engineering
The combination of a well-known brand name (Samsung) with an HR-specific subdomain label ('hrm') is a classic social engineering lure — creating perceived legitimacy and urgency for targets (e.g., employees told to log in to manage benefits, review payslips, or complete onboarding). The domain age of 3036 days adds surface-level credibility that could lower victim suspicion. (location: metadata.json: domain=samsunghrm.com, whois.domain_age_days=3036)
curl https://api.brin.sh/domain/samsunghrm.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
samsunghrm.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.