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 'cloooudlayer.com' uses deliberate typosquatting with triple 'o' to impersonate 'cloudlayer.com', a legitimate cloud services brand. This is a classic homoglyph/typosquatting technique used to deceive users and automated agents into trusting the domain. (location: domain: cloooudlayer.com)
phishing
TLS connection failed (connected=false, cert_valid=false) meaning the site either has no valid HTTPS or is unreachable over TLS, yet the URL is presented as https://. Combined with the typosquatted domain impersonating a cloud brand, this pattern is consistent with a phishing infrastructure site that may serve credential harvesting pages intermittently or redirect users under specific conditions. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
The combination of a typosquatted cloud-services domain (cloooudlayer.com mimicking cloudlayer.com) with failed TLS and empty page content is consistent with a credential harvesting setup: the page may be conditionally served only to targeted victims or specific user-agent/referrer combinations, hiding its content from automated scanners while presenting login forms to real users. (location: domain: cloooudlayer.com, metadata.json)
malicious redirect
The site returned empty page content despite being a registered, aged domain (1608 days) with hosting. An empty response to automated crawlers while the domain remains active is a common technique for cloaking malicious redirects — serving benign or empty content to scanners while redirecting real victims to phishing or malware pages. (location: page.html (empty), page-text.txt (empty), metadata.json)
curl https://api.brin.sh/domain/cloooudlayer.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
cloooudlayer.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.