context safety score
A score of 43/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
malicious redirect
TLS connection failed (connected=false, cert_valid=false) for a site named 'cpanelhosting.rs' which impersonates a well-known hosting control panel brand (cPanel). Users or agents navigating to this site over HTTPS will encounter an invalid/missing certificate, which is a strong indicator of a misconfigured phishing or credential-harvesting infrastructure. Legitimate cPanel hosting providers maintain valid TLS certificates. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
brand impersonation
The domain 'cpanelhosting.rs' directly incorporates the 'cPanel' brand name — a widely recognized web hosting control panel software. This constitutes brand impersonation that could deceive users or automated agents into believing they are interacting with an official cPanel-affiliated service. (location: metadata.json: domain=cpanelhosting.rs)
phishing
Combination of brand impersonation (cPanel name in domain), failed TLS (no valid HTTPS), and completely empty page content is consistent with a phishing site that may serve dynamic or targeted content, or is in a staging/deployment phase awaiting activation. The .rs TLD (Serbia) combined with a cPanel-branded domain increases suspicion of a credential-harvesting phishing setup targeting hosting customers. (location: metadata.json, page.html (empty), page-text.txt (empty))
credential harvesting
Sites mimicking hosting control panel brands (cPanel) are a well-documented vector for credential harvesting, targeting webmasters and hosting account holders. The invalid TLS certificate and empty page body suggest the site may serve login-form content conditionally or has recently been taken down after active harvesting. The domain pattern matches known cPanel credential phishing campaigns. (location: metadata.json: domain=cpanelhosting.rs, tls.cert_valid=false)
curl https://api.brin.sh/domain/cpanelhosting.rsCommon questions teams ask before deciding whether to use this domain in agent workflows.
cpanelhosting.rs currently scores 43/100 with a suspicious verdict and low 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.