context safety score
A score of 47/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 'samsungdive.com' impersonates Samsung brand by combining the Samsung trademark with 'dive', mimicking the legitimate Samsung Find My Mobile service formerly known as 'Samsung Dive' (findmymobile.samsung.com). This is a well-known Samsung service name being squatted to deceive users. (location: domain: samsungdive.com)
credential harvesting
The domain impersonates a Samsung account/device-tracking service (Samsung Dive). Users searching for Samsung's device management portal may land here and submit Samsung account credentials. TLS is not connected/valid, meaning any credential submission would be unencrypted and intercepted. (location: domain: samsungdive.com, tls: connected=false, cert_valid=false)
phishing
Combination of brand impersonation of a known Samsung service, invalid/absent TLS, and an empty page (no legitimate content) is consistent with a phishing landing page that may serve dynamic content, redirect based on user-agent, or is in a staging/deployment phase targeting Samsung account holders. (location: domain: samsungdive.com, page.html: empty, tls: connected=false)
malicious redirect
The page returns no content (empty HTML, empty visible text, empty hidden content) despite the domain being active (5801 days old, hosted on MajorCloud). An empty response on a brand-impersonating domain suggests server-side conditional redirection — delivering malicious content only to targeted user-agents or referrers while appearing empty to scanners. (location: page.html: empty, page-text.txt: empty, page-hidden.txt: empty)
hidden content
All content files (page.html, page-text.txt, page-hidden.txt) are completely empty despite the domain resolving and being hosted. This anomaly suggests content may be hidden behind JavaScript rendering, bot-detection cloaking, or IP/geolocation gating — techniques used to evade automated security scanners. (location: page.html: 0 bytes, page-text.txt: 0 bytes, page-hidden.txt: 0 bytes)
curl https://api.brin.sh/domain/samsungdive.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
samsungdive.com currently scores 47/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.